Microsoft & .NET.NETOld Programmers Never Die, They Just Become Managers. Not!

Old Programmers Never Die, They Just Become Managers. Not! content and product recommendations are editorially independent. We may make money when you click on links to our partners. Learn More.

For the better part of the past dozen years, I have worked as an itinerant software developer, sort of a “have computer, will travel” consultant. For a long time, everywhere I went I was one of the young guns. Now, it all of a sudden seems like I am an old timer. When did that happen? Now, I routinely work with people who are closer to my oldest son’s age.

After many turns of the calendar and years of whacking on a keyboard—in addition to a bad back, carpal tunnel, poor eye sight, and more flab than I like to see in the mirror—I am old enough to know a thing or two about my line of work. In this article, I share the pearls of professional wisdom I’ve accumulated over the years, starting with my favorite: Old programmers don’t simply disappear.

Continuing Education and Working Smarter

Continuing education is going to really pay off over the long haul. At 40+, one will not be able to put in 80- or 100-hour work weeks like the kids will. To compete against young programmers with raw horsepower, you will need a lot of wisdom.

If you are too tired to continually train yourself, your skills eventually will become outdated and you will find yourself at an increased risk of job loss. It’s okay to slow down, but never stop learning—not in this business.

What if you feel too old or too tired to work as many hours as your younger co-workers? Well, the truth is that there is no correlation between hours worked per week and good software. There isn’t even any proof that excessive work even really helps improve a project’s timeline. Good (or great) software is a function of team work, good planning, sound management, and a level head. More than likely, if one or more people are working 50+ hours a week, people are trying to compensate for poor planning by heroic effort and there is a very good chance the outcome will be poor too.

If you’re working 50+ hours a week at a fixed rate, and/or your peers or management don’t respect you enough to provide adequate planning and resources to do the job well without killing yourself, find a new job. An unwillingness to work your life away means you are smart enough to live a balanced life. It does not mean you are undedicated.

Up or Out: Is It Myth or Reality?

I worked at an East coast investment firm recently and very few people seemed to be above the age of 35. Such work environments might make one wonder, “Will I be either forced into management or forced out of programming after I turn 30 or 40?” The answer is no, not if you make yourself valuable through continuing education and eschewing long hours in favor of proper planning and wisdom.

Why do people assume that an older programmer eventually has to become a manager? Do we make older doctors stop practicing medicine? How about lawyers? Do all lawyers have to become judges or politicians? Generally, no. The good news is that the industry is growing older and the median programmer/developer age has increased too. It’s not just kids any more. Remember, what young programmers have in energy you have in experience by now. Brain beats brawn almost every time.

About the Author

Paul Kimmel is the VB Today columnist for and has written several books on object-oriented programming and .NET. Check out his new book UML DeMystified from McGraw-Hill/Osborne. Paul is an architect for Tri-State Hospital Supply Corporation. You may contact him for technology questions at

If you are interested in joining or sponsoring a .NET Users Group, check out

Copyright © 2006 by Paul T. Kimmel. All Rights Reserved.

Get the Free Newsletter!

Subscribe to Developer Insider for top news, trends & analysis

Latest Posts

Related Stories