Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Left to my own devices, I'd probably spend 100 hours one week programming, then not touch a computer for two or three weeks, reading or building something or doing stuff outdoors instead.

Such a level of autonomy would be fantastic for a bunch of people (myself included!). The opposite extreme -- a continuous drudge of exactly 40 hours/week -- is pretty scary, because the work itself would have to be pretty mundane to be so predictably reliable. At some level, really creative and difficult problem-solving does have such burstiness built in.

But... one thing I've found in the process of matching "natural burstiness" with "externally-imposed stable output rate" is that sometimes, the drudgery is useful too. When I'm stuck in an unproductive state, continuing to do something helps to unstick me. Creative inspiration is sort of a positive feedback loop, where just taking a step (any step!) and trying something helps to fill me with ideas for next steps and alternatives. So I'm not exactly pleased about deadlines, or external pressure, but some pressure or goal (internally-imposed is best) is really helpful for me. There are still bursts and lulls but the lulls become more disciplined and useful somehow.

Of course, all of that is assuming that there's some interesting creative kernel to the work. If someone's complaining that 40 hours/week of CRUD apps is just not floating their boat... well... they've got deeper problems. :-)



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: