Earlier quoted context omitted.
I had a bit of a burnout around 2006 -- I had worked my ass off on a fantastically complex framework, the pinacle of years of experience, and it was a joy. It was SO cool. There was an application on top, which was also pretty cool. And the marketing bods/management and so on more or less dragged the project off track, up to the point I didn't want to work on it at all, I quit, I left my 'baby' and had a hard 6 month…
Heh, respectfully, I think we're talking about two different kinds of burnout. The form I am referring to, builds steadily over time. It's not the result of some bad interaction with management, rather, it's the result of doing the "same" thing for 30 years. I recognize that the problem is in seeing it as the "same" thing. Yet, given our job as programmers is often to see the forest through the trees, to identify pat…
There's LOADS of fields that you haven't done. I remember my first time trying to get my head around some VHDL code and I felt I was 12 years all over again looking at 6502 assembly code.
Make your horizon wider!