Earlier quoted context omitted.
I'm in your same age bucket, and when I hear comments like "work smarter rather than just putting in more hours", I wonder if that's not just rationalization for simply not wanting to work longer hours because people in that age group generally have other life obligations, and eventually become overpaid and uncompetitive status. You can't always work smarter day in day out, and expect to beat someone who is both smar…
> when I hear comments like "work smarter rather than just > putting in more hours", I wonder if that's not just > rationalization for simply not wanting to work longer hours > because people in that age group generally have other life > obligations, and eventually become overpaid and > uncompetitive status. When people advise to work smarter than harder, it's often a nod to the fact that longer hours generally produ…
I have a largely different opinion on this, working smarter just means doing the right thing instead of the wrong thing. I realize that is vague and I think the reality is vague here. Investing the time to write 'reliable, maintainable, and extensible' code is the right thing to do when it's the right thing to do, it's the wrong thing to do when the it's the wrong thing to do. Being older shouldn't mean that you always write 'reliable, maintainable, and extensible' code, it should mean that you realize when it's warranted and when it is not. My experience is that this isn't the case, 'older' coders (and I safety quote older because I'm not convinced that age is the true differentiator) tend toward 'reliable, maintainable, and extensible' at all costs. That just isn't the right answer all the time. I'd venture a guess that some of the stigma that exists about 'old coders' is related to this.