Is there a difference in their work output? Absolutely there is, in my experience here. Contrary to my prior assumptions, it is actually the _die hard_ tech guys that
- Produce excellent work
- Produce a consistent amount of work over long periods
- Keep up to date with tech
- Don't really seem to suffer "burnout"
- Consistently improve their skills and progress their careers
- Have a high probability of being enthusiastic about a new project, technology or their work
Where as the ones who are "work-only" programmers (not always) tend to
- Produce excellent work in short bursts, and then average work the rest of the time
- Do not produce consistent amounts of work over long periods
- Not only struggle to keep up with tech, but actively _fight_ the idea of having to learn something new
- Have a high probability of going to management to discuss their "burnout" and take extra time off
- Seem to have one specialized skill set that neither improves nor gets worse - they just float around the same level
- Rarely show enthusiasm for a new project, technology of their work
People often refer to "burnout" in the context as a short term solution - but I honestly think that "burnout" as we know it is a result of someone who has already "checked out" or "lost the passion" for what they do (or perhaps, they never had it, and just went into this career for other reasons)
This seems really grim for the non _die hard_ people, so here's some positive traits I've seen in them that are usually lacking in the _die hard_ people.
- Typically have much better communication skills
- Usually better at reasoning for which technology to use in a project (ignore "language or framework of the week")
- Are better with customers and maintaining relations
- Provide more support to their colleagues
- Willingness to take on different kinds of tasks (no attitude of "that's not my job")
I think it's fair to say that balance is key between these very dynamic cultural traits we observe as programmers.
EDIT: formatting