Hacker News new | past | comments | ask | show | jobs | submit login

A whole career of very short jobs isn't great though. One particularly valuable kind of experience is seeing a project through and understanding how early decisions went awry later on.

Some older coders I work with might not have obsessively learned the latest framework, but they can identify issues like "that's the kind of subsystem that one person ends up maintaining, and then they leave and it's awful", or "We did something similar in the 1990s, and it didn't go so well because it is overly complex. Is there a simpler way to do this?".




> One particularly valuable kind of experience is seeing a project through and understanding how early decisions went awry later on.

That's a good take on it, and the application of it vary with companies and industries.

A waterfall EE project at a old school company could hardly deliver any stage in 6 months.

A software project at a fast executing startup could have gone through 2 major delivered projects in that time.


Ha ha, I guess I'm screwed as I work in a job shop where no project lasts longer than 6 months. I love it though. Better that than the same project for several years.




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

Search: