>> At my current place... well, they pay me to write code all day long. If
>> I hadn't written that code, somebody else would have written it, which
>> means it would have taken the company slightly longer to get where it is
>> now.
>
> That sort of implies that you have no skills that are unique. I find
> that hard to believe.

Well, we all know how to write code, so...

> There are probably specific tasks that people turn
> to you to. Either because you do them faster or better. Better either
> because more readable or more thorough.

Mostly people turn to me because I happen to be the guy who wrote 
function X, and how does that work again? I could look it up, but it's 
quicker to ask you...

> Some of these things might even be related to Haskell as a spill over.
> Not that you use the language, but you may use techniques borrowed from
> there.

Heh, I still remember the day I wrote some code that parses a particular 
file, and I wrote it as a nice isolated function that takes the file 
contents (which is data) and returns the parsed result (which is data), 
and then a tiny wrapper that actually does file I/O. This makes it 
trivial to test the parsing without having to *physically* create files 
on disk...

...and then my boss ordered me to munge the two together and write tests 
that actually create (and then delete) files on disk. Sometimes I feel 
my talents are totally wasted...

Post a reply to this message