✳flâneur — a map of the web's best reading

the interruptible programmer · SteveStreeting.com

stevestreeting.com · 2,018 words · saved by 1 readers

I’m 37, and I’ve been a (professional) developer for 16 years. You would have thought that in that time, I’d have figured out an effective work style which delivered the desired outcomes (code cut, products shipped etc) without causing detrimental knock-on effects - but, sadly, you’d be wrong. I think the style in which I practiced my craft for the first 15 years of my career was much the same as every other enthusiastic developer: you put a ton of hours in. 12-16+ hour days, evening and weekend coding marathons, pizza in the keyboard, crunch times, 3am debugging sessions where you just can’t go to bed because you can feel the source of that bug just beyond your fingertips, dammit, desperate last-minute sprints to deadlines where you manage to slot that last piece in, Jack Bauer-like, just before the world goes to hell. If you’re in the demographic I’m talking about, you’re nodding sagely, and probably grinning a little too, reminiscing on past trials and glories. This sort of crazy dedication is respected in our circles, and is pretty much expected of any developer who has claimed to earn their stripes.

Work 2.0 - the interruptible programmer · SteveStreeting.com Work 2.0 - the interruptible programmer 4 Sep, 2010 · by Steve · Read in about 10 min · (1981 Words) coding Development GTD Health Productivity programming I'm 37, and I've been a (professional) developer for 16 years. You would have thought that in that time, I'd have figured out an effective work style which delivered the desired outcomes (code cut, products shipped etc) without causing detrimental knock-on effects - but, sadly, you'd be wrong. I think the style in which I practiced my craft for the firs

Explore this link on the map →

related reading