4 ms·

> 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

> 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 produce negative results. [0] Working smarter generally means planning before writing code, thinking about how one's work will integrate into the larger system and how to make that code reliable, maintainable, and extensible. It also means picking your battles and directing effort where it will count. With experience coders learn that endlessly coding generates errors and shortsightedness. Sure, there is a small percentage of coders who can code error-free for much longer than most, but most coders will be most productive when keeping to a regular 40-hour work week. And even super coders are susceptible to burnout. [1] [0] http://www.igda.org/?page=crunchsixlessons http://www.igda.org/?page=crunchsixlessons [1] http://www.alistapart.com/articles/burnout/ http://www.alistapart.com/articles/burnout/ EDIT: format link list.

mtkd 10y ago
a great old coder I've worked with for many years often says - I might not know the solution - but I know what it isn't - that knowledge/perspective mixed with younger coders who will do some heavy lifting is a very powerful configuration if you don't understand the benefits having some 40 or 50+ year old devs on a team brings - watch some Jim Weirich videos
mbell 10y ago
> Working smarter generally means planning before writing code, thinking about how one's work will integrate into the larger system and how to make that code reliable, maintainable, and extensible. 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.
- mirchiseth 10y ago
  The journey of right someone told me - do the thing - do the right thing - do the right thing the right way

mtkd 10y ago

a great old coder I've worked with for many years often says - I might not know the solution - but I know what it isn't - that knowledge/perspective mixed with younger coders who will do some heavy lifting is a very powerful configuration if you don't understand the benefits having some 40 or 50+ year old devs on a team brings - watch some Jim Weirich videos

mbell 10y ago

> Working smarter generally means planning before writing code, thinking about how one's work will integrate into the larger system and how to make that code reliable, maintainable, and extensible. 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.

mirchiseth 10y ago
The journey of right someone told me - do the thing - do the right thing - do the right thing the right way