Where Do All of the Old Programmers Go?

full-of-beans asks: "I work as a software developer for a large UK based international organization. Most of my colleagues that program are under 40 years old. Those that are over 40 tend to be in either Management or IT Support! I was wondering were do all the old programmers go? They can't all end up in management. I know we don't get paid enough to take early retirement. Is there some other career that tends to attract 40+ year old programmers, if so I'd like to know, because I'm not that far of 40 myself!"

Loony Bins

[Anonymous Coward]

They're all in sanitariums, driven insane by debugging assembler for countless hours.

Re:Loony Bins

[Hal_Porter (817932)]

Notation Polish proper in write!

Kids Damn!

Bankruptcy or Public Service

[Marxist Hacker 42 (638312)]

Seems to be the only other choices. Private industry, since globalization and commodity coding offshore, has no place for old programmers anymore. They cost too much in salary and benefits in comparison to a young person just out of college, preferably India Institute of Technology, where they train the next generation of yes men.

Re:Bankruptcy or Public Service

[rkanodia (211354)]

My father is an IIT graduate who worked on (among other things) Project MAC at MIT in the 70's. He ended up becoming an executive by the 80's but quit so he could go back to being a developer. And, like you said, it's hard for people his age to find work in the private sector. He eventually settled in as a systems architect for Apple, of all places. I guess they realize (unlike most companies, which, as you said, dump their old hands in favor of cheap noobs) that it doesn't matter that he costs twice as much, because he's ten times the programmer they'll get by recruiting straight out of schools.

Re:Bankruptcy or Public Service

[vectorian798 (792613)]

preferably India Institute of Technology, where they train the next generation of yes men.

Agreed with everything except that last clause there. Do you really know what you are talking about or are you just randomly talkin' out your ass? Whether you are a 'yes man' or not, is completely based on your own personality and not where you go to college. I think what you meant to say is that 'preferably IIT, which has typically churned out excellent graduates' (note: I am at UCB not IIT, so this is by no means a biased statement).

Re:Bankruptcy or Public Service

[Marxist Hacker 42 (638312)]

Agreed with everything except that last clause there. Do you really know what you are talking about or are you just randomly talkin' out your ass? Whether you are a 'yes man' or not, is completely based on your own personality and not where you go to college. I think what you meant to say is that 'preferably IIT, which has typically churned out excellent graduates' (note: I am at UCB not IIT, so this is by no means a biased statement).

As a 30-something programmer who went to a good American school, it's something I've noticed in the newest generation of H-1bs hired from India. Most of them are from IIT, and most of them know the language that they were hired to work in- but NONE know when to tell managment off when they need telling off. Managment likes this, and this is the reason I got laid off, moved to contracting for a state agency, and am in the process of interviewing for a permanent position with the same agency. It's more a function of age than where you graduate from I think- though there does seem to be something in the Eastern cultures that lends itself to working on teams and not rocking the boat.

At any rate, it seems obvious that private industry has no place for an old curmudgeon like me- which is why I'm headed for the public sector.

Re:Bankruptcy or Public Service

[middlemen (765373)]

I am sorry to hear this. I am from IIT and I am working in USA (not on H1B but with a Green Card). What you dont get is that the US Dollar is 45 Indian Rupees. If an Indian with an H1B visa works here, it is not for the life in USA, it is for the money which he gets in USA which gets converted to 45 times that of Indian money. Agreed some inflation, and standard of living has to be accounted for, but even then it is a large amount of money for that Indian on an H1B visa. And if this guy starts "telling off" his managers, he will be sent back to India, and another "yes man" will be brought in. This guy might have family that he needs to support etc. , so you cannot say that all IIT graduates are "yes men". In fact most of them are far from it. It is the circumstances that make a man a "yes man".
I on the other hand do speak my mind with my boss, because I have no fear of getting fired and being sent back to India, because I live here and since I have a green card I can apply for another job in the worst case scenario.

Re:Bankruptcy or Public Service

[Marxist Hacker 42 (638312)]

I didn't really think it was a function of where one graduated. But thanks for correcting me that it's more a problem of the indentured servitude (employer purchased) visas as opposed to culture.

Re:Bankruptcy or Public Service

[kypper (446750)]

And if this guy starts "telling off" his managers, he will be sent back to India, and another "yes man" will be brought in.

Can you tell me how that doesn't validate his point?
You're saying that because you don't fear being deported (like a natural born citizen would), that you have no problem telling your boss off, but that those from India need to be "Yes Men" to stay in the country. Regardless of whether they are all 'Yes Men' by nature, what you're saying is: they have to be to have the jobs here. Thus they ARE willing to bend over for the company and thus ARE more attractive to the company as employees.

Re:Bankruptcy or Public Service

[pkphilip (6861)]

I am an Indian and I don't agree with the GP's broad assertion that Indians are "Yes" men when they land in the US. I worked and lived in San Jose. I decided to come back to India after my contract ended even though my employer granted me full-time employment. One of the reasons I was offerred this employment is because I am not a "Yes" man.

The assumption that people will throw you out on the street if you don't keep sucking up to the management is false in most places; any management worth its salt expects to hear the truth from the floor and once the management gets around to the understanding that the people on the floor are lying to them and basically kissing butt, they will rapidly lose any respect for the opinions of these minions. Even the management expects to hear the truth - believe it or not.

Re:Bankruptcy or Public Service

[crucini (98210)]

I'm also in the Valley and I think the Valley is quite different from most of the US. Companies here tend to value truth, openness and competence. In other places, especially the East Coast, yes-men thrive.

Re:Bankruptcy or Public Service

[deaddrunk (443038)]

You're very wrong about demand for COBOL programmers. I was one and there are very few COBOL jobs about now, most have been moved to India because there are no young, cheap people coming into that field (not surprisingly). I now find myself outside of IT and the only way I can get into the newer fields is to get a degree just so I can get back into something that I already have 15 years experience doing.
No-one wants to train me despite the fact that I did a C++ course at college and passed it with full marks (showing that it wouldn't take long for me to pick stuff up). It's in the nature of the wastefulness of corporate culture, they'd rather pay top dollar to poach someone or take on someone inexperienced in years than someone who only needs the language/platform skills, not all the analysis/design/corporate politics skills that takes years to learn rather than a few months.

Re:Bankruptcy or Public Service

[nikster (462799)]

It's true that trying to not get fired is a pretty good motivation to say yes to everything thrown at you. I even know westerners who do it.

But it may also be a cultural thing.

I now live in Asia and the culture is that you DO NOT under any circumstances tell your boss off. Or anybody else of "more respected" status like your dad or even any older, presumably wiser person.

People here say no but they say it in a way that an American or other westerner would hear as a clear and loud yes. It's subtle. I can now tell a yes-that-means-no from a yes-that-means-yes but it took me a while. And some westerners who live here simply never get it.

Oh... signs of getting old, I am repeating my own argument. [slashdot.org]

Re:Bankruptcy or Public Service

[ShyGuy91284 (701108)]

Sounds like what my Japanese Culture teacher said in a lecture once. She had a slide to see what we knew about Japanese culture, and we learned that "We will carefully inspect your resume for further consideration" is a flat out "no" for if you are going to get a job somewhere..... I hope to go to asia someday, idk if I would be able to stand the formality between me and a boss though. There's a certain relaxed atmosphere many US bosses have that you can joke around with them. My supervisor in a previous job was actually a pretty good friend of mine in the end.

Re:Bankruptcy or Public Service

[aeoo (568706)]

"Yes men" are precisely the people who are bound by conditions -- they fear for their lives and those of their families, and that's exactly why they are "yes men". The man who can say NO when needed is precisely the kind of man who is not affraid to lose life and comfort. Because such man doesn't produce yes'es and no's out of fear, he is less likely to be biased and is more trustworthy, but at the same time, timid people are often affraid of such a man.

It is ironic, but it is people who love their families the most who end up hurting their families by creating a world where the power is so unevenly distributed. If people were less skittish, and yes, this means, not so worried about their families, then it would be difficult to bully people and boss them around, and there would be fewer scams and inequities, and the families would benefit. In the long run cowardice hurts us all.

Re:Bankruptcy or Public Service

[crystall (123636)]

I've worked for both public service and private companies. If you love to code and don't want to be a manager, public service is a great way to go. It's fairly secure compared to the private sector (except when the legislature starts messing with pension plans). I'm 53 and have been coding since the days of punch cards. And yes, you can teach old dogs new tricks - last year I made the switch from Cold Fusion/Sybase to OracleForms/Oracle/PLI.

And I'm not alone. Half my state gov't shop is over 40. What we oldsters can offer the young-uns is experience. It may not have been the same language or the same platform, but we've learned a few tricks over the years. And we're not just fogies sitting on our butts wasting taxpayer dollars - our agency leads our state in e-govt offerings.

Re:Bankruptcy or Public Service

[CastrTroy (595695)]

The problem is that everyone, not just programmers, expects to be getting paid a lot of money, just because they've been doing their job a long time. Take a look a bus drivers. They get a raise every year, and by the end of their career are making twice as much as the newer guys. Are they really bringing any more to the organization just because they've been doing it longer? Obviously in programming it helps you to provide more for a company once you've been around a while, but eventually you top out in what you provide to the company, and therefore so should your salary. Similarly, if you start at a new company, you may be less useful than those who although they have only been programming 5 years, all of it has been with that company, and they are able to provide a lot to the company. If you're doing the exact same thing you were doing 5 years ago, what makes you think you should be getting more than cost of living increases every year?

Re:Bankruptcy or Public Service

[Marxist Hacker 42 (638312)]

Then make one. Find someone who has a problem and propose a solution. Update your skills. Go make something happen. When I moved to Seattle in 1992, I had no job and things weren't good for VAX programmers. While I was looking for work, I learned new skills on my own and turned those skills into something very successful. I think that one problem with today's programmers is that they believe that opportunities will just jump in their lap. I hate to tell you this, but those days are long gone. But if you row into lake in your boat and fish don't jump in, do you stop fishing? If you fish and don't catch anything, don't you buy better tackle?

Oh I did that too- but a side job doesn't pay the bills, though it is a great way to keep the skills sharp. The fact of the matter is, the skills of a coder are very much oversupplied these days- most of the paying jobs are in Microsoft land or Java land, so those are the skills you need- but those are ALSO the skills that 50,000 new IIT graduates get EVERY SINGLE YEAR- and they don't have a family to feed or a mortgage to pay, and they will give their right arm to work in America, instead of giving managment a fight over deadlines and things that can't be accomplished.

It's more like coders are the fish- and for every line of employment, every opportunity in the private sector, there are several hundred fish going for the line, and twenty or thirty eating the bait (getting an interview). Contrast that with public service, where they must hire a citizen, and there are usually only 30-40 applicants for a job, and the permanent position I just interviewed for yesterday had only 4 people interviewed.

Do not be afraid.

[douglips (513461)]

40 year old programmers are recycled into yummy treats called "cheetos" and fed to proto-programmers. It's the circle of life.

Re:Do not be afraid.

[cratermoon (765155)]

Well at least now I'll finally be able to say to the young turks who love to produce bad code [thedailywtf.com] and come up the endless excuses to justify it: EAT ME!

Re:Do not be afraid.

[LifesABeach (234436)]

Legend has it that there is a hidden valley. This is where the "old" programmers go. There the lan's flow at 100gb, there's total 3D emersion games, and software licenses cannot survive. PHB's can't see it, and Users read the GD Manual. I hear it calling me now.

Rats, its my boss asking how to reboot his "Etch-A-Sketch" Lap Top.

They get a life?

[TERdON (862570)]

... or possibly, there just aren't that many programmers over 40. Most educations aimed at programming started approximately 15-20 years ago or less. If you were programming before that, it wasn't very likely that you had been educated for programming, but for something else...

Re:They get a life?

[vsprintf (579676)]

Hell, if you got started so long ago that you're 60+ and programming now, then you started off with punchcards and manual switches.

What would your point be, since 2GLs and 3GLs are far easier and require less understanding of computing than machine language and manual switches?

That's a hell of a big change, a lot more than simple syntax and such. I mean, if you started with C (1972), then you're still in good shape with Perl (1987) and Python (1991). But if you started with Fortran (1957), Cobol (1959), and Lisp (1959), you're stuck with some seriously dead-end knowledge

If you think that, you don't understand programming at all - or were you trying for a funny mod?

Not that there aren't jobs around for those specialities, but what was hip in 1960 is fossilized today. You could be using Fortran 95, or Scheme, I suppose, but what would be the point?

Take your Ritalin and sit down. Just because someone knows Fortran or C doesn't mean they don't also know Java and C++. You're like the class clown demonstrating his knowledge of two languanges while everyone else knows four.

Government Work

[dch24 (904899)]

I am a contractor at a government installation. Without going into too much detail about what it is I do I can say this: civil service jobs in the US are where a lot of over-40 programmers go because the benefits of working for the US government are pretty good:

1. Your employer is the largest (fill in the blank) anywhere.
2. Your employer can't fire you. Civil servants basically can't be fired unless they do something completely crazy like "go postal."
3. The pay's not great, but the people are pretty laid back. And most of them are over 40.

Well....

[Anonymous Coward]

You ever hear of Mountain Dew? It's old programmers, I tell you! Mountain Dew is old programmers!

Silicon Heaven, of course!

[Tackhead (54550)]

> Where Do All of the Old Programmers Go?

Silicon heaven [nildram.co.uk], of course.

(No such thing as Silicon Heaven? Preposterous! Just ask the collection of HP calculators nobly enshrined atop the PDP-11 in my basement!)

If we told you, we'd have to...

[ddent (166525)]

Fortunately you are almost 40 and won't have to be wondering in suspense for too long, but you can start saying your goodbyes to your friends and neighbours. Just tell them your going on a trip and you don't know exactly when you'll be back. We don't want to attract too much attention to our operations. At the stroke of midnight, we'll be dropping by. You can bring a couple boxes with you if you like, though you'll be well provided for even if you don't.

Back to School

[CrazyTalk (662055)]

I'm 41, a former programmer, and thats where I am - getting my MBA (and currently managing development outsourced to India). A good friend of mine has left the development world and gone back to Law School. Not an uncommon story.

Law School

[stlhawkeye (868951)]

I realized a few years ago that your typical lawyer doesn't know jack about technology, and you're typical IT person doesn't know jack about the law, judging by the number of Slashdot posters who run their mouths about IP rights without understanding them, or asserting the right to do things that they clearly have no right to do (note: saying you should have a right that you don't have is fine, saying you do have a right that you don't have is ignorant; this is the practice I'm referring to).

So I decided that, since I'm an argumentative armchair law nerd, I may as well get paid for it.

But mostly, I want out of IT because it's generally unstable and I don't find the work to be satisfying. The contributions I wish to make to the world do not lie in software development, and so I'm getting out.

Re:Law School

[vertinox (846076)]

or asserting the right to do things that they clearly have no right to do (note: saying you should have a right that you don't have is fine, saying you do have a right that you don't have is ignorant; this is the practice I'm referring to).

"We hold these truths to be self-evident, that all men are created equal; that they are endowed by their Creator with inherent and inalienable rights; that among these, are life, liberty, and the pursuit of happiness; that to secure these rights, governments are instituted among men, deriving their just powers from the consent of the governed; that whenever any form of government becomes destructive of these ends, it is the right of the people to alter or abolish it, and to institute new government, laying its foundation on such principles, and organizing its powers in such form, as to them shall seem most likely to effect their safety and happiness."

-Thomas Jefferson [wikiquote.org]

To paraphrase what I think he is saying is that I, nor you, nor the government actually can give or take away any type of rights at all. These are things that exist but cannot simply be handed out like physical things since they are given by either god or the natural order of the universe.

Rights are simply there.

Old C programmers don't die

[bsartist (550317)]

... they're just cast into void*

They WORK

[maiden_taiwan (516943)]

They go to companies who appreciate them.

My company is aggressively hiring software engineers right now. When we interview a senior developer who really knows what he/she is talking about it, it's like a breath of fresh air.

It's true you can get more raw work done by two junior bodies vs. one senior engineer at twice the price, but when your production database server is dying under load, you want the engineer with experience to be there.

At least Old Programmers Never Die

[Aging_Newbie (16932)]

From Google:

Old programmers never die, they just lose their memory
OLD PROGRAMMERS never die, they just byte it
OLD PROGRAMMERS never die, they just decompile
OLD PROGRAMMERS never die, they just get bugged with life
OLD PROGRAMMERS never die, they just go to bits ...
Old programmers never die, they just branch to a new address. -
Old programming wizards never die, they just recurse.
Old PROGRAMMERS never die, they just can'tC as well.

Most 40+ programmers don't work....

[kawika (87069)]

...for large companies. By that point in your life you've learned enough to know that big companies move slowly and make dumb decisions. By age 40, you've either moved into management to participate in the stupidity, or you've left for a small company or consultancy. At least that's the way it's been for me and my friends.

I love programming and will write code until I die. It's fun (in a perverse way) to come in to various companies, fix their WTF code [thedailywtf.com] and look like a hero.

Re:Most 40+ programmers don't work....

[Maxo-Texas (864189)]

I agree with both of you.

Large companies are slow and stupid. You can spend months doing nothing and then they act like something is an emergency and then before it is finished, it's dropped and something new is chosen. Assuming all does go well, you suffer a huge productivity hit.

I was at small companies christmas party tonight and I asked about how long it would take them to make a 100 line change to production that involved adding a new column to the database.

They replied, as I remembered from my small company days, oh about 2 hours-- another said half a day. I told them (and it obviously shocked them) that it took 4 months at a large corporation. There are too many steps to go into, but it is a stutter step of forms to fill, required estimation of the size of the project, impact analysis (even if you know there is none), approval of the pmo office, more required forms, required kickoff meetings, (actual coding & testing), required weekly status meetings, required regression testing, approval of the database team, coordination with our outside hardware partners. Sarbanes Oxley can be responsible for about 1 month of that - the pmo office can be another month of that.

It is truly horrible. But yes, you still have career programmers because they are tired of spending their personal time to self train a few nights a week and really just want a pension and a stable job. It can be stable until this offshoring crap started- until inflation makes offshoring a bad deal (in 3-4 years) it piles on top of all the other horrible stuff.

But hey, it's a job- it pays okay as long as you leap to each new tech, and it can take months before the large company lays folks off if it decides it wants to do so today. They just don't want the risk. So they have you document everything and train your offshore replacement before they let you go. So you keep racing to take on new responsibilities so they can't let you go. And so on.

Mentoring

[fishdan (569872)]

I had the priviledge to work with an older programmer -- and he was amazing. We had an incredibly productive office, and it was because even though we knew the science of computer programming, this guy knew the art.

He also taught us incredible lessons. In 8 hours a day, 40 a week, he was able to get all his work done. And he did finally hit it big, and 2 years ago bought his dream house on the beach. As a spot of bad luck that beach was in Gulfport MS, so he'll have to rebuild, but that's not really the point.

The best lesson he taught us was "embrace new technology -- because that's what your job really is." As a result he embraced Windows when it came out, Java, Open Source, XP, and was incredibly relevant, even at the the ripe age of 55. Of course he embraced some things that did not become important. He became a Notes developer. He spent a month becoming an expert on XML, and I know it never really became useful for him. What he knew, and taught us -- there is no point in this profession where you can stop learning. For some people, when they realize that, they decide they want to move to management, where learning actualy hinders your career.

The reason you don't see many old developers is because they can't/won't learn new tricks. All you guys out there who won't learn Ruby? You're days are numbered -- not because Ruby IS the next great thing -- but because it MIGHT be. As a technologist, if you want to keep working with technology, you have to embrace the fact that technology changes.

My last comment is thanks Leo! I know you'll see this, and I just wanted to let you know about the debt that we all owe you, and hope that some day I can pass on the lessons you taught to me to other young developers.

Re:Mentoring

[jcr (53032)]

I had the priviledge to work with an older programmer -- and he was amazing.

I had the good fortune to run into several people like that in my career. One of them went to work for IBM the year I was born, and he knew not only the current state of the art, but how we got here, and what was tried and discarded along the way.

My old boss at the first graphics hardware company I worked for, got into the electronics industry when the field was still known as "radio". For fifty years, he kept up. I learned more from him and people like him in my first year at work, than I'd picked up in all my formal schooling.

-jcr

Well billy, you see ... about your programmer

[RembrandtX (240864)]

the first thing that popped into my head :

"Well billy, you see ... about your programmer, he wasn't feeling so good anymore, and city life would be just mean. So Daddy put him in the car and drove him out to this WONDERFUL farm, where he could play in the sun, and see cows, run around having fun all day long. He seemed really sad at first, but Daddy said he REALLY enjoyed it there, we might be able to visit him eventually, once he is back to his old self."

To employers who know how to hire good coders

[McMuffin Man (21896)]

I work in a coding shop where the average age is over 40. We work in an industry where bugs have more significant repercussions than in most. Management responds to this by making sure to hire people who have had a chance to learn how to write quality code, and how to compensate for their own weaknesses, whatever those are.

When faced with a choice between a bright recent grad from a top engineering school with great interships and a can-do attitude vs. a forty-something engineer who's been around the block, worked on various architectures, at various levels of the system, held various roles in a team, and had to pick herself up and dust herself off after a failure or two (and who wants more money than the new grad), my VP will take the experienced programmer almost every time.

I'm under 40, and I love having all of this wisdom around to learn from. Our best, most productive coder is over 60, and he thinks so clearly and with such accumulated wisdom at an architectural level than he can see problems during the first design sketch that a clever new grad would figure out only while thinking over why he was unemployed after his product failed in the market. The young men and women on our team are very, very sharp, but brains is no substitute for brains and experience.

Programming is a skill, not a career

[syukton (256348)]

Programming is a skill, not a career. Programming is like mathematics. There are few "programming" jobs out there just as there are few "math" jobs out there, but there are a lot of jobs which heavily involve programming just as there are jobs which heavily involve mathematics.

Another way to think of programming, is as a proficiency with a certain set of tools, like hammers and wrenches and pliers for example. It doesn't matter how well you know how to use these tools, because there's no jobs out there which simply need you for your knowledge of these tools. Most jobs out there require you to know how to apply these tools in a given scenario in order to accomplish a goal or solve a problem.

So to answer the question, "programmers" stop being "programmers" as soon as they realise this, that programming is only a skill and not a career. Once this has been realised, they take their knowledge of programming (which is essentially telling a machine to solve complex logical problems for them) into another arena. Law, Science, Administration, Teaching, etc. They don't stop programming, they just stop being simply "programmers" and instead become IP Lawyers, Data Modeling Scientists, Systems Administrators and Professors of Computer Programming.

Do the math.

[ocbwilg (259828)]

A programmer in their 40's or 50's would have probably gotten their start in the late 1970's and early 1980's. PCs were barely in their infant stages at that point, and they weren't a whole lot of them around (relative to today). Most computers that were in use in the 1970's were mainframes and minicomputers. That's not to say that there weren't programmers, but there were far fewer of them in those days. The number of people that would have been programmers in that era is relatively small.

Some of them have no doubt died off. Others may have changed professions. Some will have worked thier way into management. Others may have started their own companies.

Still others have retired. Take a look at Microsoft. They've probably had more programmers come through their doors than almost any other company in the world. They've also made more millionaires out of employees (especially from the early days, and those people would be in their 40's and 50's today) than just about any other tech company. Many of those people (not just from MS, but other companies in similar situations) may have taken early retirement.

I wouldn't be suprised to discover that a fair number of them went on to teach. If you were there in the beginning of the tech revolution, you probably have something useful to pass on to the next generation.

Then I suspect that some are still working, but because there are relatively few of them compared to the younger people (those who got their start in the past 10 years) you probably don't encounter them as often.

My father started programming back in the 70's, working on UNIX tools at Bell Labs. He stayed with them through several different companies until he was finally forced into early retirement from Lucent last autmun at the ripe old age of 57. He's by no means rich, but by being careful with his savings, and the retirement package (usually only the old-timers have these anymore), and the severance package, he had enough money to retire to Florida.

Redundancy

[Bazzalisk (869812)]

My father is a 50 year old programmer - and I doubt anyone will employ him again when his current job downsizes (as I'm sure it eventually will) - this is because there is a (stupid) perception amongst people doing the hiring that all programmers should be 20-something recent graduates ... the idea that computers are only understood by teh young has become a cliche in our society.

Re:First Post!

[grumpyman (849537)]

Ah that's what you do after 40 eh?

Re:Simple.

[toddbu (748790)]

This is total bullshit if I've ever read it. At 42, I can still out-think and out-code many of those 1/2 my age. Of course I code a lot smarter than before, so while I may generate fewer lines of code, they're much, much better than what I used to code. And I definitely still care about the details.

I can't speak for all old coders, but I got kind of tired of coding just for the sake of coding. You can only do an implementation of a queue so many times before you ask yourself why you're writing it. I started a company with another guy, and we are a solution provider. Part of my time is spent with customers, and part of it coding. I much prefer this way of doing things because I can produce better results and my customers get a better product. Maybe all the old coders move on to smaller companies where they can be closer to the end user.

Re:Simple.

[AHumbleOpinion (546848)]

As you get older, your brain changes configuration. You don't want/can't learn as fast, or don't care about the details anymore.

Actually, as you get older you realize that school habits are not applicable to the real world. Jobs are not like a quiz, you shouldn't be pulling details from memory, that's why we have reference manuals. Do I need to memorize the the run-time complexity of 10 sorting algorithms? No, what a waste, I merely need to have Knuth Vol 3 Sorting and Searching with a post-it note on the page with side-by-side comparisons of various sorting alogorithms, their run-tme complexity giving various types of data, info on optimal and degenerate data, etc.

Learning is not about memorizing lots of trivia. It is about filtering important info from the huge volume of crap and trivia. Learning was once described to me as the *selective* loss of information. You have to think about that for a second. We're bombarded with info, overwhelmed with it, we have to discard some of it. The better strategy is to discard info on a selective basis, the trivia, rather than discard info randomly. What some consider "not caring" is what others would consider "being selective".

Re:The Barrier

[kibbey (96367)]

Relax, all the old coders (like me) are still here fixing the crap the youngsters keep trying to pass off as working code.

Re:look forward to your exciting new career ...

[Fulcrum of Evil (560260)]

Younger IT workers are cheaper, and more familiar with newer technologies at the same time!

As a bonus, they can make the same old mistakes all over again!

Re:look forward to your exciting new career ...

[koreth (409849)]

and more familiar with newer technologies at the same time!

If that's true of you, you have only yourself to blame. Age has nothing to do with it. I'm pushing 40 myself and I still make it a habit to regularly devote time to playing with new technologies that might end up turning into something useful down the road. And once familiar with those technologies, I look for places to apply them. Yesterday I spent most of my day working on a real-time streaming AJAX UI for a multi-user financial application, hardly a technology that went out of fashion with disco and bellbottoms.

There are a lot of capable young IT workers out there. I have the pleasure of working with a bunch of them at one of my jobs right now. But there are also a lot of boneheaded young IT workers who are only in the business because it looked like a lucrative thing to major in, and who will be sick of the whole thing and looking to switch careers by the time they're 30. I've worked with some of them too. Trouble is, employers can't always tell the difference between the two. Meanwhile, as a going-on-veteran-status programmer, I have a resume with lots of references from past employers who can confirm that I'm worth what I charge. There are lots of companies out there who value a proven track record, and I doubt that'll change any time soon. Only time can give you a track record of any kind.

In my observation, it's far more about your attitude than your age. If you can maintain an attitude of, "Wow, that's neat, I need to learn more about that and try it out," you'll probably do quite well no matter how old you are. If your attitude is, "I've learned how to do X, and that's what I do, so don't ask me to do Y," then yeah, familiarize yourself with the employees-only section of your local fast food joint, because the demand for X will dry up at some point.

Re:Mid-life Career Change?

[Phaid (938)]

Maybe it's conducive for one who programs computers to have a yearning for a different job and once they have enough financial backing, they take the plunge?

It's true. I've been a software engineer for 11 years and I frequently dream of a glamorous career as a truck driver. Once I get my house paid off, I'll buy some driving lessons, and then -- it's owner/operator time.

Re:They get executed when they turn 40 (nt)

[TheWanderingHermit (513872)]

It's more like when you reach 40, your life clock (that crystal on your palm) turns from red to black and you're on Lastday. At the end of the day, you go to Carousel, where you float into the air and explode. If you're lucky, you come back and get to do it again.

Since you're near 40, I'm sure you're thinking of running. Don't bother. There are Sandmen who will stop you, and then you don't get to go on Carousel for a chance to come back.