News for hackers. Stuff that matters.
Re:How to Burn Out Programming by acron0 on Wednesday February 12, 2014 @03:30AM (#7223199)
Number 4 worries me. What's considered to be "too short" a time period between jobs? I was at my previous job 18 months - I'd say a bit 'too short'. I've been at my current job 3 years. Is that 'too short' to think about moving on because I'm bored?
Re:How to Burn Out Programming by mcv on Wednesday February 12, 2014 @04:55AM (#7223444)
To me, 4 years is too long. 2 years is probably perfect for a salaried job. 6-12 months for a freelance contract.

But this can be totally different for other people.

Re:How to Burn Out Programming by collyw on Wednesday February 12, 2014 @08:18AM (#7224052)
The think is, for any type of maintenance programming on a large system, it takes 6 months to get up to speed and be properly productive in my experience.
Re:How to Burn Out Programming by GuiA on Wednesday February 12, 2014 @03:36AM (#7223212)
Depends on where you are and how old you are. In your 20s in Silicon Valley, 3 years is a bit long. But in your 30s somewhere else it's fine.
Re:How to Burn Out Programming by dagw on Wednesday February 12, 2014 @05:22AM (#7223523)
The goal shouldn't be to change jobs, as in the company you work for, but to change jobs, as in what you are working on. There is nothing wrong with being 10 years at the same company as long you're constantly getting a chance to do different things, moving around and generally feel like you're developing and learning.