Apr 292013
 

One of the things people always ask you as a teen­ager, or in job inter­views, or when you’re con­tem­plat­ing doing some­thing new, is: what do you want to do? And the ques­tion­er is often dis­ap­poin­ted when you don’t have a barn-burn­ing deeply-held spe­cif­ic desire just wait­ing there. Answers that are more gen­er­ic (albeit equally import­ant), such as ‘some­thing inter­est­ing’, or ‘some­thing use­ful’ are some­how unsat­is­fact­ory, even when coupled with a gen­er­al idea of the area in which you want to do some­thing use­ful and interesting. 

This morn­ing I read From “sit still” to “scratch your own itch” and it’s full of descrip­tions of expect­a­tions for pro­gram­mers that res­on­ate with me, such as the expect­a­tion that “a REAL pro­gram­mer or a REAL open source con­trib­ut­or is sup­posed to be a self-starter who comes up with their own pro­ject ideas from the start”. The art­icle has some tech­niques to stop these expect­a­tions from being over­power­ing or intim­id­at­ing. The author sug­gests, for example, that writ­ing Yet Anoth­er {Some­thing Simple} is fine, just like sew­ing an item from a pat­tern (or in my case, knit­ting it). You learn from that, and expand your knowledge.

In my case, mov­ing from pro­ject man­age­ment back into more tech­nic­al work, what helped was work­ing through online tutori­als until I was far enough along to be able to start writ­ing my own use­ful stand-alone pro­jects. Some­times I’ve sur­prised myself by how much tech­nic­al know­ledge from 10 or more years ago comes back, like wak­ing the tech­nic­al brain up again that was dormant for a while. I guess, for me, that was the itch that needed to be scratched.

/* ]]> */