Re: Re: How do you avoid "Code Burnout"?

[Anonymous Monk]

I probably would just work on the code continuously until it's done

Doesn't work. I've tried it. You usually pass out and forget everything around 72 hours.

A flap side of the "maintenance" type is someone who prefers creating new things from the start.

These ""maintenance"" types are a myth. Nobody could be so twisted that they'd prefer to maintain existing code than create something new.

[svsingh]

They're not myths! They're new hires! Seriously, a lot of companies/groups use this philosophy. Cut your teeth on bug fixes and general maintenance, and then once you're familiar with things, you can create new code.

[Anonymous Monk]

That's the difference. I'm sure these new hires would rather create new projects then maintain old ones, it's just that the people hiring them won't let them.

[xdg]

On the other hand, I wonder if starting out on the nasty job of maintaining code before getting to write new code leads one to learn programming practices that make one's code easier to maintain... ;-)

-xdg