Slashdot Mirror
Ask Slashdot: Am I Too Old To Learn New Programming Languages?
ProgramadorPerdido writes "I have been a developer for 25 years. I learned Basic, VB, C, FoxPro, Cobol, and Assembler, but the languages I used the most were Pascal and Delphi. I then concentrated on a now-non-mainstream language for 11 years, as it was used at work. One day I had the chance to move into Project Management and so I did for the last 2 years. Now, at almost 40 years old, I'm at a crossroad. On one side I realized developing is the thing I like best, while on the other side, the languages I'm most proficient with are not that hot on the market. So I came here looking for any advice on how to advance my career. Should I try to learn web development (html, xhtml, css, php, python, ruby)? Should I learn Java and/or C#? Or am I too old to learn and work a new language? Should I go back to PM work even if I do not like it that much? Any similar experiences?"
I'm 55, a programmer, and I've been out of work for two years. I've had plenty of interviews, but no job offers. Here's my take on all of this: I'm too old to be a programmer. I'll put my "management hat" on and tell you why:
1. I'm old. One 5 hour energy drink revvs up your basic 20 year old code monkey all day. I need a saline drip with caffeine in it all day to keep going.
2. I'm expensive. I have 30 years of experience in the 'biz and a masters degree in CS. I'm not cheap. You could hire two 25 year olds for what I'm asking.
3. (and what I consider to be my greatest failing in the corporate world) I've seen all the tricks. I've been exposed to every nasty little mindgame management has at it's disposal. And sometimes I have the bad manners to call people on it. This is called "having a bad attitude".
So when I compete against 20-somethings in the worst economy since 1929 (I hesitate to say the worst economy ever), I lose. I should have made the leap to management when I had the chance, not because I would have loved management (I would have had to manage assholes like me, after all ;), but because at 40 you have TWENTY YEARS LEFT. The years go by really, really fast. You should really start thinking about a soft place to land when you're 60 now, because if you aren't in line to be a VP or a Director you ain't gonna make it at this point.
The suggestion to "Follow Your Bliss" only works in an economy that's not run by sociopaths. Hell, it only works in a country that's not run by sociopaths. Strike one strike two. Tighten your belt, put as much money away as you can, and make sure you keep your health up. Because the era of "company loyalty" is over, COBRA for a family costs as much as your mortgage, and finding a new job is going to be a real challenge.
Other than that, have a nice day! :D
"If god did not exist, it would be necessary to invent him" --Voltaire
Maybe go into something that is part leadership, part technical. Like design or software architecture or system engineering. Use your experience working with software to do high/mid level design work. As you probably know, there are things that never change regardless of what tool stack you are using. Your knowledge in these areas is probably much more valuable than your knowledge of a specific language.
You’ve probably seen a lot of things work and a lot of things fail... and probably know what areas of a system need to be more flexible or more reliable and what approaches will lead to pain. Don’t take for granted that feeling of your hair standing on end when you look at a design... knowing it will be a nightmare to maintain. It takes years to develop that, and it’s valuable.
Be the guy at the end of the chain who reviews the lower level designs and provides the “overall picture”. The guy who reviews the code and makes decisions on what third party tools to use. Let the children play with the actual code/nuts and bolts.
You probably can learn a new language and go back into programming but I would suspect your experience will actually work against you. You know too much to become a newbie again.
I work with a guy who's over 60 and is just now learning Java. He's being paid to do it, to support a scientific instrument.
The determined Real Programmer can write Fortran programs in any language.
Yeah sorry, at 40 your brain basically fossilizes, and becomes a FIFO stack.
If you learn a new programming language, you WILL forget the old ones.
If you're still proficient with COBOL you can give ABAP a try since it's similar. There's a lot of SAP work around and, at least in my experience, the big corporate environment is willing to hire experienced developers.
English is not my first language. Corrections and suggestions are welcome.
https://secure.wikimedia.org/wikipedia/en/wiki/Assembler_%28computer_programming%29#Related_terminology
PocketPermissions Android Permission Guide
I firmly believe you're too old to learn the day you stop learning.
Never ever quite learning the latest and greatest in programming, to do any less is condemning ones own career path.
Having recently joined the ranks of older programmers I still find that I can completely crush the new kids by leveraging that vast experience I already have.
Dust off the learning hat and get back into the fight man, 40 isn't a time to lay down and die... last I heard 30 was the new 20 and 40 was the new 30... and we're all going to be broke in this economy so who cares in the end?
I'm about your age. My impression is that new learning is still possible, but it requires more time and effort. So I'd say it partially depends on how motivated you are.
The concepts are what are hard to learn, the syntax is the easy part. So many similar languages may trip you up at time, but if you can work through the syntax differences and keep hacking at it it's not too difficult to learn.
I owned a mortgage company during the last decade and had to shut things down when it all went south. Given that a mortgage broker has such a 'wide range of skills', I found myself with 0 prospects and a hungry family. I had always been interested in programming but never took a single course or had any idea about any language.
During the last 3 years I started learning html/css, then javascript, and now C# and PHP. It's been a battle but now I have found myself a new set of skills and have started getting regular work in my small town. I don't think I'll be programming the next social media platform but my local customers like my work and sleep much better at night.
I turn 42 next month.
Sorry but the question is too inane to take seriously. Best of luck.
Can you remember your name and not constantly pissing yourself? then your not too old to learn anything
If you think you might be too old, then you are.
Ask Slashdot: Am I Too Old To Learn New Programming Languages?
Barring extreme physical exertion and danger, you're never too old for anything. If you're too old to learn something new, you might as well lay down in your grave and wait for death on the grounds that adopting a fatalistic attitude toward new experiences basically ensures you're done with life. That's my opinion anyway. Seriously, if you can't do something new, what exactly are you looking forward to?
I do have an important question though: how did you come to begin programming? I am unfamiliar with what would have been available paths back in those days. Did you get a degree via courses in logic and mathematics? Trade school? Taught yourself? Mentored?
I believe Pascal is closest to a procedural language and Delphi is the object oriented equivalent? So that's a somewhat diverse start. Are you familiar with concepts like (but not limited to): closures, sets, Big O Notation and understand the difference between a framework and a library? These are things that I might not use daily coding Ruby and Java but I remember from school and I feel better prepare me for learning any new (or old) language. If you aren't familiar with these things, it might pay to consider taking refresher courses at a nearby college to brush up on them. I don't know how viable this suggestion is but on the grounds of learning new languages, it has proved invaluable to me in understanding why language creators made the choices they did.
Should I try to learn web development (html, xhtml, css, php, python, ruby)? Should I learn Java and/or C#?
Personally I would suggest Ruby on Rails with CSS for a solid UI. You're going to need to know concepts like RESTful interfaces and it might take some getting used to letting the Rails automagic do things for you but the resources are plentiful and free. It sounds like it will be totally out of your comfort zone and that's probably a good thing if you're up to the challenge.
Should I go back to PM work even if I do not like it that much?
In today's economy? Why not make two resumes: PM and Programmer. If PM skills pay the bills, hop on it and work on programming as a side hobby. If the right Programmer position comes up and the pay is good, consider it but don't set yourself up for failure or take too large a risk if your home/dependents/nestegg are at stake.
My work here is dung.
learning a new programming language is awesome.
however, if swelling persists for more than 4 hours...
Come up with a product idea, find the best language to write it in that you are interested in learning.. then hire one or more cheap programmers on odesk.com to write the software. You follow along, adding code when able, or just work on the user experience and PM.... Ideally you'll have customers in mind before you even start that can help test and refine the product. Roll it out as soon as possible and start charging money for it. (Yes, I've done this.. it works.. and your budget can be very small.)
You're never too old to learn. I'm in a similar situation to you: I learned a number of computer language and now, being almost 40, I don't do any programming at work anymore, I just do fancy diagrams. That doesn't prevent me from maintaining my programming skills in my spare time and learning new stuff. In the past couple of years, I've dabbled in Vala http://live.gnome.org/Vala, Python (to create scripts and desktop apps rather than web apps), re-acquainted myself with ANTLR and played with a number of other languages. If you want to have a go at an interesting variety, get yourself a copy of "Seven Languages in Seven Weeks" by Bruce Tate: http://pragprog.com/book/btlang/seven-languages-in-seven-weeks.
In WW-II Japanese air force promoted their combat aces to ranks so high they out ranked their base commanders. They kept assigning themselves most dangerous and glorious combat missions, eventually all of them died. But Japanese did have a few aces notching up dozens of kills. US, on the other hand, does not have any reaching even 10 kills. The moment a combat pilot notches up 5 and qualifies to be an ace, he is transferred to the training command and is made to teach those skills to a new crop of young pilots. Some of them eventually transferred to NASA test missions and flew research aircraft.
So though you love coding, switch to project management. I am speaking from experience. I loved coding, and stayed in programming for far too long. I am doing project management now. You can always code in your spare time, doing what you like.
sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
Properly, it could be "assembly language" or you could also say, "I got my start on 8086 Assembler," which in my case would be true. But there's nothing wrong or incorrect with calling it "assembler." Frankly, I've never heard it called "Assembly" without the qualifier "Assembly Language." Harrumph.
"Here's what's happening. You're starting to drive like your Dad..." - Red Green
I'm 47 and I split my time between management and software development. Though I strive to always improve, the management aspect of my work is not something I particularly enjoy. My personal view is that my skills as a manager are easy to find in other people. My technical skills not so much. Given that, I feel that letting my technical skills atrophy would be a huge mistake.
Yes, become proficient with web technologies. Learn HTML 5 and how to create rich applications for mobile devices. Create an app for the App Store or Android Marketplace. Get involved with an open source project.
Oh, and grow your hair out. Once you hit 40 you need long hair to be taken seriously as a developer.
nope, even IBM still calls it "assembler" at times
for example http://publibfp.boulder.ibm.com/cgi-bin/bookmgr/download/asmr1020.pdf or http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=/com.ibm.mq.csqzal.doc/fg19060_.htm
you diaper wearing puppies can go off and make up your own rules if you want, but don't be surprised if we older and wiser suddenly beat you with our ear horn
Trying to bridge the gap between developer and manager for the last years didn't work, you get pulled in too many conflicting directions
Reality of coding versus the imaginary world of management, snr management.
I have a new position (switched companies) where I can leverage my technical knowledge but manage an application, employ other skills too.
Every Java book I have started..I stall at around page 51 - partly just because you need a tutor who can answer all those dumb questions.
Is your space key completely broken? Or do you just hate doing as everyone does.
If you dont mind maintaining legacy code or systems then those skills will always be needed. If you insist on new project development then yeah it's time to either learn what is current or get off the pot.
Either way, good luck
I don't think it is a matter of being able learning a new programming language. An good example would by father-in-law has recently taken up writing programs to generate art. He is 71 and had some programming experience, but was an EE by trade. He learned java, c, and c++ as well as post script. Now as others have mentioned the real problem come with management, the body count, and corporate culture. Why would they want to have you as a programmer when they could have 2 college grads for the same price since according to management people are interchangeable and experience doesn't matter. When I tell management what I think at my job it is usually welcomed as I won't BS them and blow smoke up their ass like a lot of people do. At another company I got fired for "not being a team player" for doing the same thing.
Time to offend someone
Being Russian, and knowing all those "converts", I can tell you - they are good !!!!!!!!!
It depends on what sort of mental model you built to learn your first languages. If you started with one or two and stuck with them up 'till now, you might be stuck thinking in terms of those syntax/vocabulary models. On the other hand, if you managed to develop a lower (higher?) level mental model with which to contain your acquisitions up to now, learning more languages will be simpler.
I'd say: Give a new language a try. You might be surprised at how easy it is.
And remember: Writing software is like having sex. Make just one mistake and you've got to provide support for a lifetime.
Have gnu, will travel.
I started learning XQuery (for native XML databases) before turning 40, but it was after turning 40 that the whole beauty of the language overtook me.
There still aren't that many XQuery programmers out there, and their demand is on the rise. So learning a new language with a lot of potential and very little current competition may be what you need. Your functional programming skills will be very helpful with XQuery.
For starters, the Open Source eXist DB project is great for getting up and running with a native XML database and using XQuery. There are a lot of tutorials, deep documentation, and a very responsive mailing list.
Being "too old to learn" is mostly an excuse. Unless you have a brain injury of some description, or a brain disease, you're never too old to learn anything. It might take slightly longer, then again - it might not.
Nearing 40, I'm learning Verilog which is not merely another language, it's a hardware description language and although the syntax looks familiar to a language you write software with, how you use it is radically different. This has certain challenges, but there is no problem with actually *learning* it, nor some of the very big differences that "writing hardware" so to speak has compared with writing software. Also, while we had a slack period at work I made a start at learning Erlang, which looked like it had some useful applications for what we do, and had no particular problems learning it despite it being a functional language whereas everything I've done to date has been an imperative language.
In fact to learn a new language within the same family (for instance, if I were to learn Python) today I find it much easier and much faster than I did 20 years ago because depth of experience can help avoid the dead-ends, and we have much better tools which can also help us to learn faster.
This, by the way, applies to human languages. "I'm too old to learn a foreign language" is an excuse. "English speakers are bad at learning foreign languages" is an excuse. I started learning Spanish 3 years ago. Today, I'm at an advanced level and have even stood up in public and given talks in Spanish. I can think in Spanish and conduct my entire daily life in that language. I can even laugh at humorous programmes on Spanish TV, which proves that I'm getting to grip with it pretty well. Until 3 years ago I was monolingual so it's not that I'm getting a handy lift-up by knowing some other foreign language.
If you believe you're too old to learn it'll become a self-fulfilling prophecy and your brain will wither away.
Oolite: Elite-like game. For Mac, Linux and Windows
Hogwash. I didn't start working as a software developer until I was 50. I learned Java, Perl and PHP in a year or so. I already knew C and FORTRAN at that time. Since then I've taught myself Python, Javascript, Scala and Ruby. I've recently started Erlang.
A year later I taught my father C; he was in his mid 70's and wanted to right some software to do some statistical analysis of stock data.
Don't let these whippersnappers tell you you can't do it. The fact is that is they know it, it's easy. The stuff that is actually hard is the math, and since you went to school more 20-30 years ago you have a far better education in the fundamentals that count than they do.
NOW GET OFF MY LAWN.
What mythical force prevents you from reading and spending time on a new subject? It's like an obese person asking if they're too fat to lose weight. Having said that, C# and Java can be similar to C but they can also be different in large ways. C# has delegates. They're anonymous functions that can be passed around. Java has anonymous classes. They're classes that are defined at runtime that can be passed around. They both make use of generics. You'll need to know about polymorphism to understand that you can pass subclasses as arguments to functions and that you can return the subclass when the function had the return type of the parent class. They both borrow from the functional style and it may be alien from your perspective. But Ruby, Javascript, Python, and Scala are all functional and Python is becoming a fan favourite. The functional style makes for less lines of code to accomplish the same task as the procedural style.
I've been in the biz a long time. My observation is that you probably have to choose between doing what you like and money. If you like money more than personal work satisfaction, pick the management route. It's the better choice for us geezers finance-wise. But if you truly prefer coding, and money is secondary, then go for it. You may have to dumb-down your coding resume a bit, for "experience" works against you, and keep your asking price mellow. Only briefly mention your distant experience on your resume, they don't know or care what a DEC is.
Table-ized A.I.
You could always start your own company. Use that opportunity to learn hot skills. Like mobile platform programming such as iOS and Android. Start as a consultant so you can keep your day job.
Advantages
1. you keep an income as you develop your career
2. you create your own management position
3. you develop advanced, in-demand skill sets that are only getter hotter
4. if your day job disappears, you can build your moonlighting career
5. if your moonlighting career fails, you have the skills to seek another job
Disadvantages:
1. You gotta be brave and disciplined.
Getting proficient in anything is hard work, but age is only one factor. If you need to make a choice look at all the factors. Research areas you have domain knowledge, what open source applications are used in that area and what languages are those apps written? Leverage everything. What's the dominate languages in your geographic area, python, c#?
I'm nigh on 58 and still a developer. I am content to keep writing code.
I tried being a PM and it amlost drove me into an early grave. It is not for me.
So I went back to developing.
The company where I worked went belly up two years ago. Sure it took me a while to get another job. Not for the reasons stated but many companies couldn't hack the 'I don't want to be a Manager' answer to the where do you see yourself in 5 years question.
Finally I got a job where they were happy with that answer.. sure I could earn a load more if I were willing to commute for 3hrs a day but those days are behind me.
In three or so years I'll call it a day and retire. I will be able to afford to do that because I saved loads in my 20's, 30's & 40's.
to the OP,
Stay with it. There will be a job somewhere for you. Somewhere that will appreciate your experience and honesty.
Good luck
I see this a lot with developers who have worked in one language for a long time (while others are invented/evolved around them).
My Father-in-law was a UNIX C developer for 24 years before being laid off and facing a very soft marketplace. He asked me (a java programmer of about 8 years at the time) if I could give him some pointers on getting started on a more marketable skill.
I said "I can't give you any pointers, but I can pass on a good reference or two" *rimshot*
In all seriousness after about a week he was like "I don't know what I was so afraid of."
Just remember a language does not make you write bad code or good code, the language is just a way to express the concepts that you have down, the conceptualizition of the process is the actual hard part.
I'm 66. In the last few years I've learned enough Python and PHP to do useful work, and learned Linux enough to get an LPI cert. Considering all these things are free to download, there's no barrier preventing you learning, except your own false belief that you are too old.
"Cock Up Your Beaver" does not mean what you think. This sig is intended to clog filters and annoy do-gooders
I'm an over 40 software engineer. I've found that a diversity of skills makes you more flexible in the marketplace. I learn at least one new language a year to stay current. Sometimes I learn more than one. When I change jobs, I try to go to new industries to broaden my exposure. When the economy is good, you can really take advantage of diverse skills to work your way into the up-and-coming industries. In a down economy, your diversity of skills means you've got more options than the one trick pony.
Personally, I never want to move above team leadership. My only alternative is to stay relevant on the technical side. The only way I do that is by constantly learning and being able to show that I constantly learn. I've worked hard at remaining employable and relevant as I age and it's paid off. After getting laid off from a company hemorrhaging money a couple of years ago I have been able to pick my new place of employment from a number of offers.
The only person who can make sure you stay employable is you. The only way you can do that is by staying relevant in the constantly changing marketplace. The only way to make that happen is to keep learning every day.
irregardless, I could care less.
feast on that for a while.
While experience counts for a lot, managers and employers rarely see it that way. They will see your out-of-date skills and hire that 25-year-old who has all the modern languages on his/her resume.
Want to keep your hand in? A couple of suggestions:
- Even as a PM, you may be able to find an excuse for the odd proof-of-concept or prototype.
- Program in your spare time. If you don't have a family, you have the spare time. If you have a family, take the excuse to learn Scratch, or Python, or some other kid-friendly language - teach your kids to program!
- Teach an evening course in programming.
There is nothing mysterious about the newer languages, but you have to *use* them. Work your way up from simple stuff, Google for answers to the inevitable "stupid questions". Learning a new language, and sometimes a new way of thinking takes time. If it makes you happy, you'll find the time - but likely no longer as part of your career choice.
Enjoy life! This is not a dress rehearsal.
In fact you would probably be better at learning a new language.
The Kruger Dunning explains most post on
As a 37 year old that has programmed 100s of k lines of code in several languages for the last 15 years, I've found that understanding fundamentals is more important. With a language reference handy I can write functional code in a new language immediately, and optimized code that accounts for language peculiarities in a couple months. Mind you I've really only been working with imperative languages mostly, so a different class of language may take more time. Anyway the point is that if you really understand the basic control and data constructs that most languages share, you'll get by fine with a new language. But as others older than I have pointed out, you may want to look at the bigger picture and longer timeframe re: your career. So far I've been getting away with ignoring my age as a numeral and just forging forward to the best of my ability, but life is limited and that strategy probably won't last until the end. In any case, age is just a number, and it has a strong placebo effect, so go with what youve got instead of what you are supposed to have at your age.
LS
There is a fine line between being a cultivated citizen and being someone else's crop. - A. J. Patrick Liszkie
If you have a base its better than starting from 0. Now for my sales pitch:
Check out my site WiBit.net. We offer video computer programming tutorials in a linear and fun way. We break apart everything into 5 minute videos that are focused and comedy infused. You can skip right to things you want to learn, and skip over things you already know. We made it so you can learn if you have no experience, or skip right to what you're trying to figure out if you're experienced.
We have C,C++, and Obj-C for now. Java and C# are coming soon! Out content is free! We only ask that you sign up to download labs material!
End of sales pitch. Thank you for your time and for tolerating my excessive use of exclamation points.
for my employer, on any job I might be project manager, systems architect, developer, sometimes even racker of hardware and cable puller. I still learn a new language now and then, and now and again actually use them at a client.
Have you had much object oriented exposure? if not, get that way of thinking into your skill set with a widely versatile language that is used for command line, web, daemon and applications. I'd suggest Python, learn the basics, then do some web development, then go into a web framework (take your pick) and also learn to call C libraries with python.
http://docs.python.org/index.html
Pfft. I learned in the 70's on BASIC, Pascal and other procedural languages that ruined me for years. Fortran on punch cards? Did it.
Now I have to learn new languages for nearly every new project. It's not so hard. If you have good basic logic skills all languages are pretty easy to learn.
Tip: Become a consultant/contractor when you are old and wise.
Normally, I'd say do what you like the best, but in this case, do what the market wants. At 41, I'm expensive and falling behind in technical skills. I've gone from being a Systems Engineer back to a Systems Administrator with more server room and virtualization experience, and my salary has not changed for the past 4 years. I'm now also a small business owner and a consultant. I'm boning up on my corporate and management skills a lot more than my old technical skills. I'm learning how to attract and land contracts, manage employees and so forth. If I stay strictly technical, my salary and skills will plateau (they already have). No one wants to employ an expensive SysAdmin. They do want to employ cheaper employees on a contract that I manage. So, my strategy is to learn how to get those contracts and then hire the employees myself, earning my company revenue (and thus me, a higher salary).
My advice: learn what the market wants at the price you want to get paid. Go to salary.com or some other service and find out what the average and range of salary are for the job you want to do. If your salary expectations are higher than that job, consider switching to another set of skills that will pay your salary.
...no, you are not too old. Unless your brain is malfunctioning due to age, you should be as able as when you were a kid. It just requires more patience, from what I noticed.
I recommend you pick C# over Java. (I am a Linux user, and yes, I find annoying I can't use WINE to run those, but that's not the point). C# is less portable but is faster. Java is slower, but portable. (And both have a lot of code references).
Also seems there are concerns about Java's future (which I happen to see more realistic than the C# FUD about it being replaced with HTML5+JS, fat chance), which makes me, personally, wary of it.
Basically, if you don't care about annoying Linux users, go with C#. If you are using less common OSs and speed is not a concern, go with Java.
Also just for fun I'd learn Lua or Python. Lua is extremely easy to learn, and a seasoned programmer would master it in seconds. Python is just useful to know IMO.
Although since you list C skills, I'd personally stick to C until the very end. Super fast, super portable, time-proven and still in use (can be a pain to code but I find it way worth it).
At 40 I would have expected the OP to realize that once you learn how to program, everything else in syntax. It sounds like the OP has a robust background in coding, I can't help but wonder why s|he is expressing trepidation on this topic.
Mod me down with all of your hatred and your journey towards the dark side will be complete!
That word... it doesn't work that way.
Can you learn a new language - sure. As another poster pointed out - is it worth it? Unless you want to compete in price with a bunch of newbies; probably not.
A development team or shop is like a baseball team
There is the rare superstar that gets top dollar because they can do things nobody else can' which is why they are rare and expensive.
There are a few solid players who have decent careers because they have a good skill set and can be depended on to deliver. they make a decent wage but no where near the superstars. They stick around.
The biggest group is the journeymen players - they hang around a few years but there is always a crop of younger, cheaper players coming up to replace them. they never get serious money. They get churned to control costs.
Then there are the managers and coaches. They are valued for their experience; they know the game, seen all the tricks and can guide a team to victory. The may not make superstar money but they are paid well and they have longevity (as long as they perform) and options to move if they do well. They stay up on the game but don't try to play. Plus they decide who gets to play, where they play and who stays and who leaves.
As others have pointed out, there's always someone whose cheaper or wiling to work for less when it's a pretty generic skill set. I'd use your experiences to move to a place where your knowledge and experience is what is valued; rather than try to build a new skill set. Learn new languages to be able to identify good vs. bad programming; but base your value on being able to identify problems before they hurt you or solve them as they come up.
I can't code a line (unless it is Fortran) but I can manage a team and clients to get the job done on schedule and budget. It can even be fun -I've never believed you need to be a jerk to be a manager.
I'm a consultant - I convert gibberish into cash-flow.
I can't pretend to know enough about this to have any valuable input, but I do have a suggestion. A few years back I worked on a project, and one of the guys on the team with me was in his 40s as well. He knew the language we were using (C#), but he didn't know modern programming theory. Unfortunely, the team lead didn't get a chance to look at his code before he left (he was a contractor), so we ended up having to throw out almost all of his code because none of it was object oriented. All that being said, if you go back to learn a new language, pick up some new programming theory as well. On a closing note, good luck with your decision. Career path decisions are almost never easy (I'm in the process of that right now myself). Best of luck!
I'm 34 and learning more and faster than ever before. I pick up new languages and ideas like a fish in water. The more I learn, the easier it is to learn other new things.
I can't believe that 6 more years would see me turn into a turnip.
No, 40 is most definitely NOT too old to learn new tricks. My father think he's too old at almost twice my age, and I don't even agree with that.
"If you make people think they're thinking, they'll love you; But if you really make them think, they'll hate you." - DM
I'm 40 myself. I love coding. I had to learn a couple of new languages last year. But I'm finding now that it's a better use of my time to train the new guys to do the job I was doing last year. More work is getting done. The painful lessons I learned last year, I'm teaching to the new guys this year. So instead of one guy doing that job, there are now four guys doing it, and it's getting done faster, and possibly better, because at least a couple of them are smarter than I am (really, that's a low threshold).
Easy Online Role Playing Campaign Management
If you're familiar with Delphi, then C# should take about five minutes to pick up. It was designed by the same architect as Delphi, and you do almost everything in the same way. It just uses C syntax instead of pascal. But ha at being too old, my dad picked up Delphi in his 40s and it's his favorite for RAD. He still uses Delphi 7 (the last good one) for everything, and grumbles about there being no Mac version. "Use Lazarus, it's exactly the same" "No, too hard to use" "It's identical!" "No it's not". Then again, he's probably trolling, he was mocking my use of a smart phone "My phone makes calls and that's all a phone is for!" and then he bought a droid ;)
ASCII stupid question, get a stupid ANSI
You aren't too old, but unfortunately you've used VB.
Confucius say, "Find worm in apple - bad. Find half a worm - worse."
get offa my astroturf!
If you could program one language, you can program in any language. It's inherent on the Turing-completeness of programming languages. It's all just a matter of syntax. Sure, mastering a language takes time, but you've probably see already much things and that means you can easily apply what you know to the knew languages.
See, I agree with you 100%, more if I could. In my years developing, most of the languages I now use to program are not the ones I was employed to do, but ones where I've been dropped into a project, had to hit the ground running and learn on the fly. It's not difficult, once you know the concepts of *how* to program.
But. Try going in to a job interview and saying "No, I don't have 5 years of this language, but give me a week, some small changes to work on and access to google and I'll be able to program it as well as most of your other developers". It may be true, but it doesn't wash with HR people or project managers. They have a ticksheet of skills and levels and they don't care a damn how easily transferrable any of them are - if you don't have it exact, tough.
-Never argue with an idiot. They drag you down to their level, then beat you with experience-
If you understand the concepts of programming, then the knowledge is transferable. I will grant to anyone that it is difficult to go from procedural to object oriented languages, but in the end, it is all "yet another way of telling the computer what you want it to do."
What's great is that with few exceptions, it has all been done before a thousand times by many people who document themselves on the public internet. So if you are armed with a good, strong, general understanding of programming and a strong understanding of what you want to accomplish using another programming language, there is much you can learn "on the fly" without making too many mistakes along the way.
Good programming practices are fairly universal, after all. Knowing the intricacies of a language is also important but can be learned as you go as well. (you know, details like limits on the size of memory elements such as integers, floats, arrays and the like, the effects of dynamics such as what happens to an integer, signed or unsigned when you decrement past zero and so on...)
But without a purpose of a goal, even a fake one, it is pretty difficult to learn anything. Most books which teach programming, do so by use of examples so that you can have a feel for the practical application of some aspect of the language.
But really, the question of "am I too old?" Age is not the issue. I am convinced it has everything to do with the health of the person in question. As you get older, it is easier to loose parts of your mind from time to time, but I have found that if you watch your diet, you can keep your mind more clear and ordered and prepared to accept and process new information and knowledge. I have also found that when I eat badly, my mind works BADLY. For example, low-carb with lots of vegetables and roughage style eating gives me optimal mental performance. But when, on occasion, I eat those burgers and fries... or worse? (I love'm okay?) Well, the impact on my mind and even on my vision is quite profound... and I regret having done so almost every time.
So as you get older, take more time to prepare yourself and your environment for absorbing new things. Eat things that you know are good for you instead of things you want (unless they are one and the same). Clean your environment! Clear away interruptions. Put on some classical music (that really helps). Plan your path. Imagine starting, working and completing. Then do it.
Hell I did some of my best programming/system design when I was 40! But I do find it odd that you would be asking about learning a new language... that's something you should have been doing all along. Part of the challenge of being a good developer is staying on top of the latest trends and development environments. In fact, some days, the only thing that keeps going/motivated is knowing that there is always an opportunity to learn new things.
Wanted: witty unique signature. Must be willing to relocate.
I'm in a similar age category. And some things are harder for me to pick up these days. But other things aren't.
I'm not really trying to learn new languages at this point, over the last 15 years I've surveyed at least 150, and trying out small projects with at least 10 of the best ones.
Right now I'm going "back to school". Studying AI http://www.ai-class.com/, and Algorithms http://mitpress.mit.edu/algorithms/. I briefly toyed with the idea of studying Knuth, but it didn't seem practical for what I want to accomplish.
Why not work on some FOSS projects? Even fixing bugs can help keep the old gears turning. Better yet, start your own fun project.
Age has little to do with it, save young programmers may have more energy and no social life. Too many hours is sign of a poorly designed project and management inexperience.
I'm a 40 year old history professor, but I've lurked at Slashdot for years on account of my hidden/closeted geek side.
I've just now started to learn Arabic and Mandarin Chinese. Back in college I studied Russian, and mastered it quite quickly. I am progressing nicely in Mandarin and Arabic, but by no means am I mastering them at the same pace I mastered Russian 20 years ago.
Though some here are denying it, yes, as you get older it does become more difficult to learn. Not impossible, just more difficult. We now have wives, kids, job, mortgages, and home repairs to occupy our time, so of course making time to learn new languages is difficult. But it's more than that. Our brains simply aren't the same as they were 20 years ago. I'm no MD, but this is simply a function of the evil which is "aging."
If you only noticed "irregardless", you missed half.
I too come from a (mostly) Delphi/Pascal background and switched to C#.NET about a year ago. It's amazing what you can do in C# and the learning curve for Delphi veterans is not too steep. Trust me, choose C#, you will not regret it.
Ditto. The #1 advantage to age is domain knowledge. You need to play this up.
Code monkeys are cheap, but a guy who knows his algorithms and has good domain knowledge is cheaper. Code monkeys will cut and paste, do naive things or write unmaintainable code. According to Alan Kay, on average, 80% of the cost of software development is after the software has been released. This means that in order to beat those odds, good code needs to be written from the start. You should make this case in your job interviews.
For anyone out there doing hiring, here's a tip for spotting good programmers: they tend to work on paper first. Give them a practice problem and see if they can decompose it without a computer. No code needs to be written, just watch the process unfold. Any competent programmer, or one who dares to call himself an 'engineer' should be able to do this in front of you.
I'm 50 and have been in this career for 30 years. Throughout my work life I've had to adapt to the changes in the industry, from Mainframes to minis, to PC, and now the mobile device. It can be done and I think you give to much power to inexperienced developers, not enough credit to managers.
I can agree that cost, in this market, can be a factor, but then how much are you willing to cut. I dropped 15% to get my current job, but it was still within my budget and I get to work in a growing company. Are you willing to move? I did to keep working.
Learning a new language at this point is not an issue of a fossilized mind (like another poster quipped), but that you have more distractions in life in general. In my 20's, the level of responsibility around me was limited. No wife, kid, house, or major debt. Over time my focus and time got more diffuse, and the work environment restricted my ability to "experiment" with new technologies. If you want to learn something new you'll need to set aside time to work and research. You will also need something that interests you, to drive you along. Right now I'm writing an application to scrape data off a website, integrate the data into google maps API and store it off to a MySql/PostGreSQL database. Its fun, but I don't get to work on it all the time. IT's not for my job, but it is something I can talk about in an interview.
What I feel is this, it is not so much a situation of young or old, it is about attitude. Don't stress the brain thinking you can't compete, you can, but you need to express it. You may cost more, but you save them more, you show them you can adapt, learn, you show them you can mentor, yet be open to instruction. Today's world requires flexibility first and people's perception is that "older" folks are stuck in their ways ('Get off my lawn kid"). Show them you are not and it will go a long way to securing a job.
One thing I'll say to hiring IT managers, get off the "What language do you know" path. You want to hire a quality developer? Then don't quiz them about details of c# or ASP or PHP or Java or what ever the hell is the language of the day. Google negates the need to memorize details, the languages are just too damn complex these days to be an expert in everything. You want to know how they think, how they solve problems, how they design/create. Syntax can be taught/learned, but good critical thinking, that comes from experience. Code monkeys will cost you more in the long run then one or two creative minds. Creativity is ageless. The best shops are those with mixed teams.
Life is a great ride, the vehicle doesn't matter
I started on .net languages when I was 44. Now they are what I do all day long (Admittedly, .net makes things significantly easier than they used to.) I just bought an android with the specific intention of writing some real-estate apps.
Non-programming skill sets enhance your employability as well. These days, in addition to programming in .net, I design automated testing system frameworks and the VMWare virtual machine environments in which the system runs. One day, I'm coding. The next, I'm tearing down and rebuilding a server. After that, I'm developing and testing a virtual machine configuration for cloning and making sure the Oracle database is configured correctly. The day after that, I'm documenting some portion of the system and preparing a powerpoint presentation explaining the changes after doing the diagrams in Visio.
One of these days, I'll take a programming course. I promise.
So yes, you can learn, if you have the skill of self-teaching.
The only thing that might cause you a problem is physical. If you're older AND obese, have frequent insomnia, or chronically use medications with a cognitive hit (prescribed or not), you might as well find something else to do.
Please do not read this sig. Thank you.
I am early 50s, coding for almost 40 years. Still employed but worried about the next job (taking a pay cut and/or competing against clueless but cheap weenies). The fact you went into PM tells me you went to the dark side. I don't generally see people come back from that. At least stay abreast of trends and development environments that have traction. Perhaps start focusing on Android. I feel safer having coding skills than management skills. In a downturn you need to retain the "doers" not the PMs. All our PMs were let go in the last round of layoffs. All us 40+ year old coders are still working. My friend retired from his programming job last year at the age of 79. Still had calls asking him to do some contract work.
I'm 36. I grew up on BASIC. Now I prefer C++. Two days ago someone asked me to write a web-app in PHP. I had never used it before, but I said "no problem". About 500 Google searches later, I'm a PHP expert and I'm just putting the finishing touches on my web-app. If you can't learn any more, you're not a programmer any more.
should help you work your way through college. I suggest you go back to school and learn Naval Architecture, Marine biology, History or something totally different. For two reasons:
When it comes to programming you've seen it and done it, time to move on.
Nullius in verba
I once set out to learn Java after years with a "legacy" stack. What I found is that the Java libraries made no sense to me such that I couldn't figure out how to use them in a timely matter for things that were a sinch in other languages.
It's like you have to connect a Flig to a Snerg, and the Snerg to the FloogManager before even simple things worked, and none if it made logical sense to me. I have to know "why" to think about how to do things; it's just the way I am wired. Until "why" clicks in , I'm a fish out of water.
The libraries seemed like arbitrary, random bureaucracies created purely for job security of Java programmers and builders. Maybe there is a rhyme or reason for the whacky maze, but I'd probably die of a heart attack before discovering it. I abandoned Java like the plague and focused on scripting languages instead, but they pay less. Java 1, me 0.
Table-ized A.I.
I'm 60 years old and... what was the question again? Damn! I'm pretty sure I had a great reply.
I'd say that since you aren't dead yet (no check for zombie) then the very notion of 'too late' goes right the hell out the window. Find a project that interests you; implement it in the 'new' language and see what happens. If you and the language don't 'click', pick another language. Lots of languages, lots of projects---shouldn't be a problem; good luck :)
I was similar to you then at 40 decided to learn genetics (genetics is just programming right? :) . Turns out high-end biology is full of enormous data analysis and management problems, and now I mostly do coding and stuff, with a little project management thrown in, but in a more varied and interesting domain than billing systems I specialised in before. I picked up perl, bits of python, java, javascript along the way, and moved from the propriatory monolith databases to the open ones. You have a wealth of valuable skills already, and are not too old to learn something new. Be prepared to do it for less income, If money is your main motivator, stay where you are but switch to managing something bigger in a different organisation, that seems to be the best way to keep fresh and keep working up the ladder if you don't want to start something completely new.
Korma: Good
To learn one computer language isn't just learning the language, but learning how to learn languages; each additional one you pick up should be that much easier. It's not effortless, but it's doable. FURTHER; while less popular languages don't have as much of a calling, they often do end up being legacy code that some employers becoming increasingly more desperate to have maintained, adjusted, et cetera... so maintaining a working relationship with an 'old' language may make you a rare commodity later (and thus worth more.) It's something to keep in mind, if not bet the bank on.
The words do whatever I tell them to do.
Assembler, motherfucker. That's what we called it in the 80's while you were just a glint in James Gosling's lazy eye.
-Billco, Fnarg.com
feast on that for a while.
Mmmm. Tasty. I liked it alot.
and you've never heard of such men as Richard Bong or David McCampbell. Given that, your assertions about the Japanese are also suspect.
Hail Eris, full of mischief...
E pluribus sanguinem
I love JBOSS with redhat. Using an MVC style development you can utilize JSP, Java, Rich Faces, and CSS. The best part...it's open source with a great community for support
If there is no God then free will is an illusion.
irrelevant if he was "good" by your definition. If someone is willing to employ him, that's the only thing that matters. Even if later *you* find his code is a bitch to maintain, tough shit for you. That just means he's the shit "pitcher" and you are the bitch "shit eater". Real world is a bother that way.
For the sake of learning the languages, given your background, in your position I would pick up C++, Java, and C# in that order. (That path will provide the quickest learning curve given your experience.) After or concurrent to those, you should also learn PHP. The basics are not that much different from C or Basic, and the object oriented extensions are most similar to C++ and Java. The reason I suggest PHP is that it is not just useful as a web programming language, but is also very useful in backend scripting when used in console mode. However, for the sake of career advancement, continuing with Project Management is the best route to take. You might enjoy a position as a development team manager, where you can still take an active role in programming, for the sake of constructing overall architecture, and then delegate building specific modules to the rest of your team.
All these new languages will still understand you, give or take bit of punctuation.
Korma: Good
You're 39? You're just getting started. You have another 30 years of employment to go. Don't quit now.
When planning your future, you should ask yourself two questions: 1) What kind of job do I want? And 2) what kind of work is plausible for me, given the state of the industry, my age, my skills, my location... and most of all,
my attitude. Do I still want to kick ass or not? If not, that's your real problem.
Professionally, learning yet another programming language won't mean much unless you can also show meaningful experience using the language to build something of value.
More importantly, it's not proficiency in a language that will open doors at your age. It's the ability to deliver solutions -- on time, on budget, that work. If you've been a 'principal scientist', or 'software architect', or 'lead programmer', then you can turn your experience into an asset. These roles are out of reach for kids right out of school. But if you can talk a good game, show that you know how to design, coordinate, and integrate the many components needed to deliver a new software service to your employer (or a client company), then you're a rare asset and you possess skills that are far more valuable than being conversant in yet another programming language.
BTW, I'm 53 and since I was your age, I've developed proficiency in several languages (high performance computing, image processing, matlab, R, perl, java, C*). But what I value more (and I think future employers will too) is 1) my ability to take a leadership role in driving a project to a successful conclusion. And 2), I'm willing and able to learn. I've completed several advanced courses part-time (3 grad CS/EE classes in the past 3 years). In doing this, I've shown that I can adapt to changes in the workplace, and reinvent myself as the work changed.
Strategically, I'd suggest that you adopt a 'leader/innovator' attitude in your current workplace and in future interviews. If you look like someone with ability, a 'can do' attitude, and impress others as being engaged, inventive, and innovative, you can break down the negative stereotypes that often beset older techies. At least that's worked for me so far.
A final word of advice. Do NOT express your opinion (*especially* negative ones) on any technology or business philosophy, and don't disparage the quality of your technical skills. DO emphasize that you have learned how to get things done, and have a track record of doing just that, ideally by understanding the business, anticipating needs, inventing and delivering solutions, ideally by leading others.
Good luck.
I would keep learning. I've been in the Industry about 20 years. I started with Cobol, then RPG, then C, then C++, then Java, and now I'm doing some Groovy and Ruby and lots of SQL. Also, Its funny, I still work a lot with C and there is still a lot of C code out there.
In my humble opinion, you would probably get the best results learning Java, Groovy, and Ruby. And of course keep your SQL skills strong.
I would also stay away from PM work. I have done some Project Management and some Business Analysis. I hardly ever get recruiters asking me about PM jobs or Business Analyst jobs.
On the other hand, regardless of what anyone tells me about outsourcing, etc, recruiters still call me and email me about coding jobs all the time. I'm a US Citizen, 40 something years old, and I haven't been out of work more than 2 weeks in 20 years by staying technical and coding.
Good luck...
At this point in your career you know enough about PROGRAMMING to mentor the next generation. No matter what language a team is using, there are best practices that should be followed. Developing software involves a lot more than just writing code. Companies need people who have been through the entire development life cycle to mentor those who haven't. Make the move into management and help the next generation. Extricate yourself from the minutiae of the code itself and focus on everything else that goes into developing software.
I am at a similar point in my career, although I am a sysadmin. I'm getting tired of keeping up with having to learn new interfaces and new tools. The basics are all the same. Keep the systems online, keep them backed up, make sure they are redundant, keep the data safe, etc. I've done the work for the last fifteen years and I understand it well enough to mentor people who are doing the grunt work, hacking at the configs, racking the gear, etc.
Oh wait...
I've been product managing and architecting for a years and now I'm out of work at age 52 with no obvious prospects for re-employment. I decided the developers were always having more fun than the managers. So I took my first course in c++ last month at a local community college (2nd quarter CS.... objects, linked lists, pointers, etc.). It was hard, but not impossible.
I have the same questions. Objectively, the idea of becoming a developer in your 50s is ridiculous, absurd, silly. But here's another thing that's even more ridiculous. - Getting up in the morning and having to do things that you don't give a damn about. So with my unemployment checks and savings I'm back to school to see how far I can go in the art of coding.
Will this enable me to support my family? I have serious doubts about it. On the other hand, it's not like there are other options falling out of the trees. It will take a least a year or two before I can even walk in the door and say "Hey I'm an old guy with some new skills... (and a lot of experience around software development)... what terms are you willing to hire me on?" If I do this thing, I'll do it the honest way, not pretending to be a 20 year old developer, and not asking for the salary of the experienced 50 year old project manager that I am.
Will it work? Will anyone bite? Hell if I know. But I do like playing with code, so I'm taking baby steps down that road and we'll see where it leads.
I'm a hiring manager. Many, many times I have hired people because they are smart, despite the fact that they have no experience in the particular programming language in use at my company. For the right people, learning a new language is easy.
Indeed. Over the last 4 decades I have written lots of assembly code for a host of machines such as Burroughs B3700, CDC Cyber, Honeywell DPSx and Data General MVxx00 systems, and even (somewhat later) for Intel *86 boxes. I don't remember agonising (even once) over what to call the language. Sure, the CPU architectures are different, of course, but the operations are pretty much the same.
Returning to the topic of the OP, my contention is that so long as you have your marbles, there is no reason why you should not be able to learn a new programming language. Assembly coding is comparatively hard to do, and no longer necessarily that useful on the majority of modern machines. There might be a coolness factor implicit with the use of ASM which I missed back in the day when that was what we did, but I guess I missed that.
However, such advanced age as mine might be an incentive to choose quite carefully where to distribute your interests. I can't offer any particularly insightful choices here, since I don't know what the function is; if all you're doing is coding for websites, then take your pick out of the various markups available. If I were still writing apps I would personally pick C and/or Fortran for my (perhaps geriatric) preference, but I would still consider learning Python or Ruby.
There are many things to consider here, OS, Language, Environment, UI, Hardware - all of these things are important to a successful developer, and the choice about which to focus on can be intimidating.
I like Linux as a hosting platform over Windows, while I've architected solutions on both platforms, I've had greater success and stability overall with Linux servers.
For Linux hosting, the main web technologies are Java, PHP and Python. Of those three, PHP is (by far) the most prevalent.
I'll take some time to run down some pros/cons of each language and describe some of the most popular frameworks for each.
Java:
This is the mainstay of enterprise development, for web development the most popular and current platform is called Spring. Struts is also popular, and many folks use a combination of Struts and Spring (though this is becoming less common as people migrate more towards 100% Spring based). Java runs under a servelet container, there are several of these available (both commercial and free) but many people chose to just go with the Tomcat servelet container from the Apache project. These frameworks are MVC (Model-View-Controller) frameworks, which is a technological abstraction which can be a useful paradigm for larger applications.
Pros: Java is great for enterprise development where you have "waterfall" SDLC and strict requirements. It's is great when you need rigid B2B interfaces/services and critical, formally modeled infrastructure. There is also a massive developer pool available for Java development.
Cons: The language is becoming outdated, as both Sun and now Oracle have failed to effectively update it. Spring makes Java web development possible, but it is not nearly as capable as some other frameworks. Time to market is slower, as Java requires much more code and "plumbing" to get up and running. Java/Spring aren't as flexible as some other technologies, and don't lend themselves as well to rapid, agile, iterative development.
PHP:
PHP can be considered the "grandfather" of the internet. It was the first very popular server-side language after the CGI days, and to date, most web sites on the internet are still running PHP. While early versions of PHP suffered from major security concerns, this is no longer the case, and PHP has evolved into a first class language with very moderns features such as OOP and Functional (map/reduce/inline anonymous fuctions/closures/etc...) features. There are several great frameworks available for PHP, two of the most popular are CakePHP and Symfony (yes, the spelling is correct). PHP apps can have great performance, I've developed some very large and demanding high volume sites with PHP, and they've handled the load with no problems.
Pros: Great language, easy to deploy, reasonable developer pool, good framework availability, dynamic language that lends itself well to agile/iterative/flexible development. Great library support, probably better than any other web language due to its maturity.
Cons: If not designed properly PHP applications can become a huge mess. The MVC frameworks available for PHP are good, but they aren't the best of the options I've seen. PHP works great with MySQL (LAMP is very common) but is not as tightly integrated with other backends. Due to the architecture of PHP, the framework overhead can be a significant performance bottleneck. This can be mitigated by effective use of FastCGI or WSGI servers, but then you're moving away from the simplicity of mod_php in apache, and that's really where PHP shines (simplicity of deployment). Overall, I generally recommend PHP for smaller applications that need a quick turnaround, but I generally look elsewhere for larger, more complex applications. While the PHP community is still vibrant, many people are migrating over to Python.
Python:
Python is a very popular general purpose language, but has only really become popular for web development fairly recently (last five years).
Drinking habits can be dangerous. You can choke on the cloth and the nuns will wonder where their clothes are.
I'm 27, and I just started learning Python (via http://learnpythonthehardway.org/book/). It took me 2 days to get the feel of it. So, I'd say you're never too old. If you know the basic concepts of programming (which you obviously do) then you can pick up a new language's syntax & nuances pretty quick.
Effin excellent answer. Isn't it depressing. Go for the dough! ...but turn your garage into a hobby shop with old chipsets and show the grandkiddies how it's done. (Like mine did with ham radio)
Age is not important. The fact that you have to ask this question puts you in the old dog category. Your experience with other languages ought to give you a head start in learning new languages, and your knowledge of programming paradigms should carry over immediately. Somebody with your skill shouldn't be asking such a question, but just doing it.
My brain exploded at the first word, its recovered enough to now feel like an idiot
C++ and Qt4, and used them for the next five years to program in-house client-server applications for the state agency I worked for. Qt4 was used to replace Visual Fox Pro 5 apps, which I had learned to use several years before, at 56. The year before I retired I picked up Oracle's APEX and programmed a web based payroll package for that state agency. Since I began programming professionally 40 years ago, beginning with Fortran IV and COBAL, I have learned over a dozen languages and RAD tools. All of them were fun to learn and to use, except for APEX, which is like programming with a mental straight-jacket on, because it requires that you bend your problem to fit the tool in ways no previous tool I have used ever did.
Of all those languages my favorite is FORTH.
Running with Linux for over 20 years!
The real question isn't if you are too old to learn a new programming language, but are you to "set in your ways" ( programmers of all ages have this problem ) to learn to think in a new way?
Anyone can learn new terms and new APIs, but many refuse -or- miss learning to think in new ways.
I've met plenty of people older than you who got a book or went to a "cram until your drop" corporate training course to pick up Java.
They learned APIs, but they didn't learn how to think in OO or even in terms of modularization.
The results is a lot crappy code where you get JSPs with a solid wall of code or functions that go on for pages.
If you learn an OO language, make sure you learn AND APPLY the OO philosophy.
Good luck, IMHO experience counts in programming and as an older person you have a lot more to offer than some young dude without experience, sloppy habits and is inexperienced enough to think s/he is hot shit on a stick.
For most people anyway.
However, if you have to ask - then yes no matter what your actual age is you are too old.
"You can hire two 25 year old for your rate, but are you twice at productive?"
As an almost-25-year-old, I'm learning to appreciate what people can learn in decades of programming. Some of my professors are terrible, but some have a lot of depth of understanding of things like C and C++ which would be extremely valuable in a real project. You'll be many years beyond making a lot of the classic, simple mistakes, and you'll at least be at the point where you'll see flaws in a design (from experience seeing similar designs fail) that others won't.
You won't be twice as productive in the measurable ways, like SLOC or issues closed per day or whatever, but those were never really measuring anything useful anyway. The more meaningful things are hard to measure -- how often does your code produce obscure bugs which will be discovered months later and take days to fix? How often will you design something in a way which is so rigid you practically need a rewrite to make a needed change -- or so much the other way that you spend more time writing the "flexible" version than it'd take to write several versions of the hardcoded version? Finding that balance is tricky.
On top of all that, you also don't have the additional communication overhead of those two 25 year olds.
The problem is, how do you actually sell that? How many companies actually understand that? It seems like ageism goes the other way -- I'm more likely to get a job than you simply because of my age, even if we were asking the same price. And that sucks -- I've definitely been on teams where we needed experience.
So, if the choice is between "have no income at all" and "do web development at the rates of an inexperienced programmer", I'll take the second one... However, if the choice is between "have a well paid job which I don't really like but allows me to live life comfortably" and "do web development, which I like, but barely be able to pull my family through", I know what I choose. It won't be the web development.
I think the idea here is that web development is supposedly easy enough that anyone can pick it up, whereas, say, mainframe assembly or COBOL is obscure enough that you might be hired for having the skill alone. The idea is that if you have the experience with a particular legacy system, that's worth far more than trying to train a 25-year-old, and they'll all be looking for fun stuff like web development.
Then again, I don't know if those pay better, and I do find the attitude a bit frustrating -- old programmers are only useful for old (legacy) systems? I imagine the demand might be higher there, but we need you in web development, too.
Don't thank God, thank a doctor!
I've been learning computer languages since 1961. I definitely gets harder. The first time I noticed it I was in my late 50's and was learning Web develeopment (SQL Server, ADO, html, Javascript). When I was younger I could read a manual, remember it, and get to work. With the Web stuff I was working with a circle of books on the floor around my chair. Now I don't use books any more, just Google. Part of the problem is getting older and not remembering details so well. Part of the problem is that there is SO much more to remember. Fortran had a dozen or so constructs to learn. Modern Web systems have thousands. My opinion is that modern programming systems would be unworkable without Google. Even the young people couldn't remember it all. Would I hesitate to learn a new language now? Probably not. I just did some work with Camel for the first time; it was slow but I got through it. So, all the advice about career paths is probably good, but if you like to code, I'd say you can still do it.
As long as you take some joy from learning a new coding language and like doing things with it.
Read radical news here
Come on, cut zget some slack. By his number he's probably been programming for about 3 days or so. As to the original question of "Am I too old?", just try & see. If you can learn a new language, then the answer would be "no."
Are you familiar with the phrase Turing Tarpit?
Language X and Y both being Turing Complete doesn't mean shit when it comes to practical use and the level of abstraction you can achieve. For example, I'm about 10-100x more productive in Haskell than I am in Java simply because I'm working at a much higher level of abstraction.
HAND.
Kill yourself. Kill yourself now. If you aren't under 40, golden brown, and work for peanuts, then nobody wants you.
15 years ago I left development, to take an offer to become an (Oracle) DBA. Intelligent employers, while hard to find, recognize that DBA's with dev background bring a wealth of knowledge about what works and what doesn't. And the specialized skills of DBA's can demand a premium in the job market.
Walking away from development and into production-side database work was probably the best career move I've made in 30 years.
And there are still opportunities to get your hands dirty. I'm constantly creating Perl scripts for monitoring...coworker DBA's set up web pages...some DBA's do hardware configuration (servers, SANs)...
I've picked up several new languages in the last 15 years or so. It's amazing what still applies, for example, if you understand IMS databases then XPath is just a simple step away. C++, C#, Java and JavaScript can all trace their roots back to the original C of Unix fame. Why don't you download Microsoft's free Express editions of their development tools and play?
I developed with Delphi and Interbase for about ten years and then moved to C# and SQL Server for new development. The transition was not hard at all, as Object Pascal and C# are very similar.
As to project management vs development, one solution may be to give yourself a TINY non-critical piece of coding work to yourself for your project. I say tiny because I have worked on teams where the PM fancied himself a developer and gave himself critical chunks of the work, but he was so busy interfacing with higher-ups that he blew the same deadlines he complained to us about missing.
I think the above may satisfy the enjoyment of developing while keeping the age issues consistent with reality in the workforce. I don't like those facts either.
I don't know whether they've been jaded by the industry or their own failings, but here's my take:
I'm 46 now. I have pretty much run my own business for most of my career, so I've been able to pick and choose jobs based on my own personal desires and needs, rather than being forced to "take what I can get" from the "industry". I have pretty much "done it all", when it comes to various categories of IT, but I prefer programming the most, since I started out in it. I have a number of specialties that people depend on me for, and they are very happy with what I have done for them. I also am a Delphi/Pascal primary language developer, and I still do a lot of my development in that language. I also have developed in C/C++/C#, BASIC/VB, about 10 different kinds of Assembler, Java, and a number of scripting languages. Of those, I still prefer Delphi/Pascal. I've been learning Python and Ruby on an as-needed basis as well.
Being on my own all this time, the most important thing I have learned is how to learn, and to never stop learning something new. I figure I will be in the middle of learning something new when I keel over dead at the keyboard. I love IT and have done little else but study and work in this field.
In the last few years, I have been changing my career focus a bit from industrial and scientific projects over to entertainment. Even at this stage, I plan to develop some really fun games, leveraging my knowledge and experience from other areas as much as possible. I may never make anything that is a "hit", but that's not why I am doing it. I'm doing it because it is what I want to do, and where I want to be. I want to make something fun that *I* want to play; if someone else also likes it, then bonus!
At my age, I may not be the fastest coder in the world, and I have my share of personal demons (most of them not age-related) that I have to fight in order to get things done, but I would put my work product up against anyone's. I also know and accept that there will be age-related decline from here on out, but I don't care. I will keep doing my best until I can't do anything anymore (because I am dead). It is all I know how to do (well, anyway) and all I love to do, so that's what I will do.
Now, as for your questions:
"Should I try to learn web development (html, xhtml, css, php, python, ruby)? Should I learn Java and/or C#?"
If you want to do something in those languages, or are just curious, sure! Why not?
"Or am I too old to learn and work a new language?"
You're never simply "too old" to learn anything. It may take you longer, and you might not ever get as good at it as someone who cut their teeth on it when they were in their teens, but that won't stop you from being functionally literate enough in it to be useful.
One thing I should point out right now is that, by mastering one of the more complex "mainstream" languages, learning any other programming language is ten times easier, simply because there are few fundamental differences between programming languages besides syntax and API, and both of those are easy to pick up or just keep a "pocket" reference handy. After you have learned to become proficient in several modern/complex languages, you've pretty much been exposed to the gamut of paradigms across pretty much every language out there. Picking up new ones after that point is little more than learning a new paint coating technique; building the rest of the car is still pretty much the same -- engine, drive train, etc.
"Should I go back to PM work even if I do not like it that much?"
Well, my current situation doesn't lend well to this suggestion, since you're likely going to be working for someone else, rather than yourself, but my suggestion is to do the greatest combination of 1) what you like the most, and 2) what you feel you are best at doing for the people writing your paycheck. If those two are in conflict, my suggestion is to change the situation surrounding the latter, because you aren't likely to be able to change the former. In addition, doing something you hate just for a paycheck probably means that you won't do a very good job of it in the long run, and in that case, you aren't serving anyone's best interests, including especially your own.
-SS "Teach the ignorant, care for the dumb, and punish the stupid."
Seriously, if you are asking the question, then you need to take a shovel and dig yourself a nice lil' hole and go for a dirt nap. I'm a practical idealist. Sounds like an oxymoron, I know, but yeah, I'm 45 yrs old and I keep learning new stuff everything. I'm a developer, an instructor and I do believe that the day I stop learning, the day I think I know enough, that's the day I should just kill myself. Do you like programming? do you like a challenge? That's what you should be asking yourself. You claim to have 25 yrs of experience, have you not learned anything yet? what's so freakin' challenging about a new programming language when you got all of the other ones under your belt? I have a basic, c, c++ and assembler background. You seem to have a similar one, with even more including cobol. What's out there that you wouldn't be able to conquer? So, it's not if you are too old, but rather, do you give a crap. If you do, go for it, it's always useful and it won't be a waste of time especially\ if it's a hot commodity to learn. Unless you are kinda mediocre as a programmer to begin with, but hey, that's a story between you and your previous projects/employer. And yeah, there are a lot of young ones out there in the market and they don't charge as much or work twice or three times the amount of hours to get it done. I laugh my ass off when I see that. Because for me, I can get the job done in half the time, and it's done right. Why? it's called experience. Every project I've ever done has been a lesson learned in trial and errors. Even in success, I learned that it could have been done better and basically applied this knowledge to my future projects. By now, having myself 20+ yrs of experience in the field, I've yet seen anything which doesn't relate in some ways to something I've done in the past. How you sell yourself is how you define the relevancy of you as a person, a resource and then skills you have to offer. Keeping with the current trends and lingo of the industry is all about learning, nothing different than learning a new programming language. So, do you give a crap? do this industry still make you excited? Those are the questions you need to ask and you are the only one to provide the answer. Cheers! Claude
He can learn whatever languages he wants in his spare time at work and home, but the bottom line is, you're at an age now where you need to seriously think about putting back for retirement!!!
A job is merely a means to an end...you work to make money, to have the type and style of life you want now...and for your future in older age.
I'd say usually...the management track is the way to do this in this stage of your life. Nothing wrong with honing your skills in the meantime...in case you lose this job, etc.
But for God's sake, don't jump job and go backwards at this point in your life if you have a good livelihood going for you now and if the path looks good for your future.
Especially in these economic times. Think about money first. After all, if you didn't have to worry about money...you'd likely not work again and just enjoy life...
Light travels faster than sound. This is why some people appear bright until you hear them speak.........
I am older and more experienced than you are. The only thing that stops me from learning new languages every year is the fact that I am learning and doing other programming and application related stuff. New languages are not the only thing, it's new methodologies. Extreme Programming is well worth checking out, even if we are too old to say "Xtreme" and not make people laugh. Functional programming has a lot to say for it. Learning a new language because it's fun is the best reason. Look at other application areas, I completely switching application area (from system to scientific programming) at around your age. I mentor younger people, take on problems where I don't have a clue. Sometimes I fail. The great thing about software is that it moves fast, you can always be learning and adapting. Any week I don't both learning something new and discover 10 things I don't know is a bad week. Go for it, if one thing you try doesn't seem to be what you want, you still learned something, try something different. The only way I will not be learning a programming techniques and languages when I hit 85 is if I am dead or have Alzheimer's; in which case it will not matter.
"Basic, VB, C, FoxPro, Cobol, and Assembler, but the languages I used the most were Pascal and Delphi."
It's almost like you've gone out of your way to avoid every popular language (C being the one exception). You're in a more difficult position than most because you don't have much experience in any of the top languages employers are looking for (those being C++, C, Java, PHP, Perl, C#, Python according to most studies). How did you let this happen would be my first question. It seems hard to believe someone who takes their career seriously would manage to avoid experience with all the things employers want.
-Lod
Programming is not the major item on my position description but I do a lot of it, usually in spurts separated by programming inactivity. Last year my boss wanted me to learn Java since our contract engineer knew Java but not C/C++ so I've been sporadically attempting to learn it, and Eclipse, and ...
I've done pretty well at teaching it to my self using a couple of books, Google searches, and attempting small programs related to what I'm going to need to do when I get more proficient. It's harder than it was 20 years ago when I was 50.
I can't advise you that you should attempt the learning for your work, though, that's beyond me, but continual learning appears to keep the mind active longer. I can't remember where I read that.
Nate
If you've got an MBA as well as lots of development experience, why don't you start your own company?
As always, if you think you're too old to learn, you're right. But until then, learn Scala.
There's been a lot of good advice and interesting thoughts in this discussion.
Quick summary:
No, you sure as hell aren't too old to learn a new programming language. If you really want to get back in the coding game, pick something you'll both enjoy and be able to get work doing, and do it. But be aware of career choices you make and the consequences. You pays your money and takes your chances.
But one more thing...
I'm gonna pimp slap you for suggesting that late 30s is decrepit and aged. Logan's Run is fiction, youngster.
WALSTIB!
I think it is impossible to be absolutely unable to learn new things. But it is not so much about a language, it is usually about the experience with a particular platform (and the language(s) it typically uses). Learning Ruby won't immediately put you on par with anyone who did 2 years or Ruby development. And anyone faces this problem - not only older people. However, there is a perception that younger people learn faster and they become useful contributors to the projects. Sometimes this is true, sometimes it is not.
I think you have to decide for yourself which career path do you want to take. Being a manager, an architect, a team lead, a consultant, evangelist, generalist...Generally, I think the age kind of filters the software engineering crowd and separates the real specialists from others (who quickly become managers etc ;) ). And usually there are challenging and rewarding jobs for these real specialists out there - irregardless of their age.
One is never too old to learn a new programming language. One can definitely be too old to be paid for learning and using a new programming language.
continual learning appears to keep the mind active longer. I can't remember where I read that.
Hmm, I don't think your premise worked in your case :)
I'm middle-aged and teaching myself Python. Pyhon rox! Python is hawt! I feel younger already.
"Crude and slow, clansman. Your attack was no better than that of a clumsy child."
http://www.youtube.com/view_play_list?p=EE0530175276C4A0
I hear they're teaching python now in this course. What guile!
Verbum caro factum est
I recently interviewed a programmer who was around 60. The average age of interviewers/candidates was about 36. This guy knew everything, but when we gave him problems he would take the wrong branch and stick to it, in spite of attempts to bring him back towards the solution. We felt he would start wrong and waste too much time before someone could correct his course.
If he had been able to shift gears like the other candidates, we would have hired him -- white hair, wrinkles, liver spots and all.
I'm a 48-year-old dev-turned-manager-turned-dev who started a C# career a year ago at a competitive wage thanks to someone who reported to me 15 years ago and to whom I now report.
I'm older than you. And still learning new languages and new electronics, these days I'm building robots. My neighbor down the street is old enough that when he was a teenager, he had a television *that* *he* *built* *himself* *from* *scratch* because that is the only way you could get a television. There was one station in Philadelphia that he could watch that broadcasted 2 1/2 hours a week. Later, he was one of the designers of the ENIAC. Go to his house today, and you will find a Windows box, a Mac, and a Linux box running Ubuntu. He is still hacking -- this is a guy who was already a working engineer when WW II broke out.
I am shocked that you are asking the question. You have an attitude problem, not an age problem. I hope they pull the plug on my life support before I ever ask if I am too old to learn something new.
The problem for minimum wage jobs is that when they look at your resume all they see is "overqualified, will be unhappy working here and will find a better job in a couple of months". I ran into that problem... fast food places wouldn't even give me interviews.
You can try what I did until you find a job, and be self employed. I'm not sure what you're qualified to do, but I do know the girl who I hire to clean my condo makes at least as much money per hour as I do at my job (even after travel time).
It's hard to decide what you want to do, both have their pro's and con's.
But to answer your question on programming languages, a loop is a loop, a conditional statement is a conditional statement and that's never going to change. All the other stuff is syntactical stuff which you can easy look up on the web. If you know that there is function or syntax in one language, most often, you can find in another language. It may be hard at first but you write a program one line at a time.
If you have been proficient in at least 3 programming languages, you are never too old to learn another one. You already know how languages are the same and how they differ.
I started with Fortran II, Fortran IV, and the original BASIC. At the same time, I learned assembly languages for the IBM 7090/7094 and the IBM 1401. (That was in the early 1960s, before Noah and the Flood.) Later, I learned JOVIAL 4 and then REXX. In my 50s, I taught myself UNIX (both C and Korn). When I finally bought myself a PC (at age 55 after some 33 years as a programmer and software test engineer), I taught myself DOS, how to create Word and Excel macros, and how to create Web pages with hand-coded HTML and CSS. I still do DOS scripts for Windows XP; and I now have well over 300 Web pages on my site, some of which use UNIX scripts as server-side includes.
The only languages in which I had formal classes were COBOL and Pascal. I used COBOL for a few months, but that was a project to convert a legacy main-frame system in COBOL into a client-server system in C++. I never used Pascal.
oh noooo ...Almost 40.. I'm 41 and I pretty much use a completely different technology stack than I did 3 years ago. I switched from down in the bones Embedded real time to the goulash of frameworks that in Java back end coding. :)\
Almost 40 is not even close.
If I hire someone who costs 2x what a 25 year old costs, they should be bringing something to the table that is worth it. If someone is telling you that you're too expensive you are probably applying for the wrong job. They aren't going to pay you senior pay to do a junior job.
IMO, most professional programmers today should be familiar with something like C#, Java, or some of the other modern languages like Ruby or Python. It really depends on the kinds of things you'd think you're going to write. Even if you don't end up using these languages in your day-to-day work; concepts from modern languages are creeping back into older languages. C# and Java arrive with excellent garbage collection; and then "smart pointers" start showing up in C++. Likewise, C# arrives "foreach," then an equivalent shows up in Java and C++.
No, I will not work for your startup
I enjoyed programming too much to take care of my body, so started getting carpal tunnel and neck issues. So I moved to product management. At our company, that includes a significant amount of technical involvement, both the end users' physics/chemistry/engineering technicalities, and our software's algorithmic/data model/hardware technicalities. Tying the two areas together and seeing the plan executed is satisfying. My winning personality (non-bad attitude) was important in getting the position. I miss coding regularly to some extent, but don't miss the real low-level parts. I don't need to ever type another iteration loop, for example.
Ok full disclaimer, I'll turn 33 this weekend and despite all the trappings of adulthood (house, husband, kid, 11-year career), I hardly feel old and am constantly learning new things (including programming languages, even though I'm not a professional developer). But if you're really concerned that late 30's is way worse or something, consider this.
My dad died several years ago and left my mom with no income. His small business supported our household and for the previous few decades she had helped him run that business. Due to various boring details I won't get into, she had to sell the business when he died, and was left with no job and no marketable skills. She was 49.
She spent the next few years trying her hand at various things before settling into her current job. In the years between 49 and 60 (her current age), she learned: how to clean a house professionally (totally different than cleaning your own house), how to provide technical support answers for model-making tools and equipment (meaning she had to learn how they all worked), office management for two completely different industries, and finally library science. She is now head of circulation at her library and poised to potentially become director of the library someday.
So, age has nothing to do with it. Your brain is completely capable of learning new things at any age - in fact, constant learning can help stave off dementia when you actually do get old. But even if age had something to do with it, you are clearly not old. In other posts I've recommended various career moves instead of going back to programming, but if your actual question is "can I learn a new language despite my age", the answer is of course you can.
Don't use your age as an excuse. I'm old enough to be your father and I picked up PL/SQL this decade. Stop making excuses, get off your ass, and hop to it. Decide what type of development you want to do, and then pick the most popular language in that field and LEARN it.
And get off my lawn.
Grumble.
Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
A good programmer can be good in any language.
However the same is not true for someone who just knows a language - that doesn't mean he can be a good programmer in another language.
So, for instance, you might consider yourself to have mastered the English language. Does that mean you are a good poet? However a good poet could probably write good poetry in any language he chooses to learn.
Of course, this is all irrelevant because at 40 (and I'm right there with you) you need to be thinking about some kind of management, or being an entrepreneur or something. Just being a great programmer is probably not going to cut it much longer.
-- Senior Software Engineer, Attorney appearance services, locallawyerapp.com.
I'm 63. Since 1978, my primary language has been C or C++. In the last four years, I've learned (well enough to write at least one application in the language that saw distribution) Python and Java. If you're not totally brain-damaged from being a manager, you should be able to pick up a new language -- especially if you have to.
You know, I first got started programming when I happened upon a left hand basic cartridge with an Atari 400 for $5 at a garage sale. It came with an attachable floppy disk drive that was DOA. Countless hours would be spent with a small black and white TV with me writing procedures. Should the power turn off, all that work was lost.
... and I would not automatically assume that my four year degree at the University of Minnesota would make me a better programmer than yourself or anyone who taught themselves to code. But the important point of this is that when I interview (and I've held interviews for programmers to come onto my team many times) the interviewer is looking for you to prove that you will be a self motivated asset to the team. If you can put MIT or some prestigious school, they often lower their required threshold of proof. If you put U of MN there is still proof required -- after all there are some ~50k students at the U of MN and as such it would be entirely possible for some idiot to be herded through with the other cattle. So they just need to make sure I am not this idiot -- or at least not in the area they need me for. Now, when you have institution to back up your claim of skills, the proof requirement quickly becomes insurmountable.
Despite growing up below the poverty line working on farms, I was able to go to college with enough grants based on need. This is where our paths diverge
So I will issue you a challenge and I will target the Ruby language and Rails framework. This probably isn't the best option for a job seeker (I think some Java with maybe Spring Framework would be better suited for a position) but this could result in proof. If you want reading material for any of these steps, I recommend the Pragmatic Programmer series on Ruby and Ruby on Rails (used it is quite cheap but here is a free alternative).
Step One: Learn Ruby. Ruby is a functional language that is very simple and easy to learn but difficult to completely master. The flexibility of the language seems to continually leave me with more and more options at my disposal. From mixins to domain specific languages, it just keeps on giving. I'm guessing with your background you're going to notice that some things in Ruby are slow. This is okay. As computers have gotten beefier, programmers have sacrificed performance and (to a large degree) memory in order to make code easier to maintain and write.
Step Two: Learn Rails. Rails is a very extensive framework that is again easy to learn. That tutorial should show you how to master concepts like quickly creating a CRUD (Create, Read, Update, Delete) application for a blog or recipes (I forget). From here you have to use your imagination. Make something that is CRUD or some mutation of CRUD to demonstrate that you know how to utilize and extend this concept. You might use census data and experiment with new UI toys like Processing or HTML5's Canvas element. I think if you have access to some mildly interesting data that building a site you'd like to share would be a great idea (even if it is just in CRUD format). But get it to a state where you're proud of it.
Step Three: Github. Put your source on Github.
Step Four: Host your project on Heroku. You might buy a domain name if you're open to $12/year. I don't know how far you want to take this part. But get it so that people can access it.
Now once you've iterated over that a bunch
My work here is dung.
Dude, I out rank you by several years. You mind is flexible. It can be retrained to function in ways you have never dreamed before... at any age. It takes a willingness to attack the inflexibility with novel approaches. Listen to different types of music. Work on making music. If you aren't a math wiz dive into Khan Academy and stretch an analytic approach to thinking (go from basic to advanced math as fast as you can.) Run your life different. Start writing books for fun. Learn a new language. (Chinese is a great brain jump starter!)
The point is, you have to choose the level of flexibility for your brain. Remapping patterns (thinking behaviors and assumptions), on a regular basis, teaches your neural network flexibility. It changes the wiring of the neural pathways from "think as a coder" to "think as a learner/creator". Even within the narrow confines of "being a programmer", moving from OOP/imperative programming to functional programming, requires a great deal of brain flexibility. Once you start opening up your ability to learn in new ways, however, you will find that you are no longer limited to a programming (or development manager) career path.
You may be 40 but you are probably not even half over with your life. Keep you brain (and body) active and changing. It will insure an interesting LIFE instead of a limited CAREER.
Gook luck grasshopper.
No, you're never too old to learn - anything!
I'm 43 myself, and I never considered myself old for anything. I know for a fact that I'm smarter than the average joes out there, (hint...when everything you do, everything you attempt...becomes easier for you than your peers, stakes are...that you really ARE smarter than your peers).
Recently, I decided to revert my os to Linux Slackware 13.37 (gotta love the title), and it went down with me like a sinch, ubuntu 11.04 sucked donkeys balls, why? Unity ...and tablets that is... people wants to be idiots, and treated as such. Now I'm going Linux from scratch, do ya wanna fight about it? No...
In my 12'th of age...I programmed assembly, so what of it...now I'm 43, I'm not anyone famous, not anyone YOU lot know...I'm just a lonely bastard living it out in some swedish forest as a loner...a tech freak for sure, but I never stopped believing in myself, neither should you. I can do anything - can you?
What this world is coming to - is for you and me to decide.
I'm not on the high horse but the low one today. He only needs to be good enough to get a job.
As for language, this is slashdot, the virtual walls drip with entrails and body fluids.
If a job is just a means to an ends to make money, then that is a depressing job.
There are still a lot of things to learn besides programming !
I'm 46 and I earned my life coding since I was 20, so I have more than 25 years of experience (mostly in game programming). Plenty of Asm/C/C++/C#/VB.Net, etc...
Nowadays, I find coding boring, since it's mostly like building with Lego.
I have decided to change career, so I started practicing agility.
I have been a public speaker a few times in agile conventions, because I have a lot of terrible experience (in game companies !), and I naturally know how to motivate a team (that is: not by using money).
I'm currently self-learning NLP and TA and all possible psychological tools, which are very easy to understand for me because when you code, you know how to be methodical.
My goal is to become an agile coach.
So my advices: ...)
1) learn psychology, you'll discover that it's fun ! (read about Agile, Scrum, XP, NLP, TA, GTD,
2) try to practice psychology whenever you can
3) use your experience to help teams as a coach (don't hesitate to accept a lower salary to build your experience)
It's never too late to learn !
If you want links, just ask me.
Does not matter how many languages you might have learned, you can always learn more. The question becomes how hungry are you, how much cash do you have to go back to school, how many opportunities are at your location and for which language. I would do it in a heart beat if it raised my salary by 10k+...remember...you need to stay relevant, so if by doing so, you also get an increase in pay...why not?
No!
You are certainly not too old to learn new languages. I would recommend you towards languages like C# or Java (C# is my personal favorite) since they are more similar to the languages you know and are more useful towards more powerful coding. The other thing you might want to consider if you don't like being away from code completely and like design would be the possibility of going in to software architecture. It's probably more in line with your experience level and is less dependent on knowing a specific language in detail and more based around coming up with overall system designs to have developers implement. It maintains the technical work while letting you leverage your management experience and also mitigates your lack of coding experience in the most modern languages.
As long as you are familiar with the concept of how to organize code in an object oriented manner, not a whole lot has changed in terms of how code is written at it's most basic level. The only real changes are the shortcuts that have been introduced to simplify implementation.
AJ Henderson
You too old, guy, give it up. Go join Mitt Romney's campaign......
I'm a 61-year old software engineer. I learn new technologies every week. A few years ago I taught myself Java in 3 days. I am respected by my colleagues, many of whom are young enough to be my grandchildren. The only thing holding you back is your attitude.
40 years old? Get off my lawn and off your ass and go learn something new.
No sig? Sigh...
I'm 62. Learning languages is fairly easy. They're almost all like C except maybe LISP and a couple others. Someone mentioned PL/SQL which is straightforward and based on Ada. C is currently the most widely used language with Java losing market share and Objective-C skyrocketing (Mac, iPhone, iPad). Bjarne Stroustrup said he's he's sorry he developed C++ ("C lets you shoot yourself in the foot. C++ makes it harder but if you do you blow your whole leg off"). With multi-core processors and stagnant clock speeds, nothing runs any faster unless you code you code for multi-core. This is not easy. I've been using the Intel compilers & Intel Parallel Studio which integrates with Visual Studio on Windows and Eclipse on Linux. Learning this will give you a leg up over guys who continue to churn out sequential code as 4 -processor/10-core servers hit the market. Also, take a look at NVidia's Parallel NSight for CUDA programming (Massively Parallel Programming). The fastest supercomputer in the world uses multicore Intel & NVidia Fermi processors (as do several others in the top ten). Security is fascinating! Read about hacking, kernel exploits, web application obfuscation, cryptovirology, rootkits, social engineering and everything else you can get your hands on. Learn Metasploit. Most companies are incredibly vulnerable and don't know it. Using CUDA (above) you can access any hashed password system in a few days - max. You can become a wizard. But none of this will guarantee you a job if you're 60 and not a sniveling corporate weasel. If you're lucky, some startup will realize your worth. Or go into business for yourself.
No, you're not too old. We have just hired a software engineer in his 70s. He hit the ground running, and is continually kicking ass and taking names. It took him right around two weeks to become productive in Scala (which is not an easy language to learn). Granted, he's an outlier, but it certainly can be done.
You can try therapy and psychotropics, like a large number do and probably need, or you can grab hold of yourself and have a heart to heart. Reinvent yourself. Discover your strengths, work on your weaknesses. Look into why you are asking this question and what is it really masking. Old age and cunning has advantages over youth and vigor -- paraphrased from somewhere.
Courage, perseverance and planning.
Here is my $.02. If you don't stay current with languages, you may be able to find niche employment, but at some point, your fun will most likely end. Some languages are, of course, timeless (C++), but nobody in their right mind would choose to use VB or Delphi over .NET these days. My advice on languages is always the same: learn C++ first, then any C like language is in your reach. Learn C# or Java next, and JavaScript. With the three of these, you can do anything. Programmers who know C/C++ will always have an advantage over the new kids that started with Java/.NET. Any time something cannot be done easily in managed code (C#/Java), you will become indispensable (trust me).
Keeping a broad base of familiar languages can be a serious boon. At a single company, I have written things in C, C++, Java, VB, Delphi, C#, Ruby, JavaScript, Flex, Silverlight, Perl, Python, PHP, and old style ASP. You never know what will be thrown on your desk from new technology, or even (the Taliban ninja) acquisitions of other companies/technology. That is job security.
You sir, deserve all the mod points that I don't have to offer.
I'm 50 and you hit every point and more that I could have stated. There is so much more to building computer technology systems than learning a new programming language.
This nails it "...understanding the business, anticipating needs, inventing and delivering solutions, ideally by leading others."
Well... at 46 yo, I've learned probably about a dozen new programming languages since I was a spry 40 yo. OK, a number of those I've "learned" relatively superficially... I wish I had more opportunities to get my hands dirtier on a daily basis with all the languages I've only played with a little in the last few years, but I get paid quite a bit to do relatively few things.
Actually, over the last few years, I've *written* at least two languages. Not quite programming languages, but one markup language and one, well "annotated grammar description" I guess you'd call it. Yes, I know that NIH syndrome is a bad thing, but there's a reason why I wrote what I did (trust me). On the shelves near me I have books on about a dozen PLs that I either haven't worked with at all, or have touched passingly; it wouldn't be true to say I'm actively reading all of those books, but I certainly glance at them.
Buy Text Processing in Python
I'm 58. Am I'm still learning "new" languages. In college, many years ago, I learned COBOL, Fortran, PL/I, S/370 assembler, APL, and SNOBOL. Over the years, I've added BASH shell scripting, Python, PHP, Java, JavaScript, ICON, Delphi, Turbo Pascal, Modula II, Erlang, Haskell. I'm not even bothering to mention Groovy and Scala as they are just basically Java variants. If I can learn new stuff, you can too. The hard part of programming is figuring out what is really required and attention to detail.
The parent made excellent points. Long story short: follow his advice, stay put.
That said, depending on who you work for now and later, a 40 y.o. doesn't have 20 years left, they've got 25 or 30. You and I are in a bit of a quandary. On the one hand, because of increasing life span and concentration of wealth, having most working people retire at 60 doesn't make economic sense, and odds are that you need to spend the extra 5 to 10 years stashing cash. On the other hand, most high-value added employers don't want to hire people near what used to be typical retirement ages, and you can't time when or how the next two or three recessions are going to affect your career.
So, listen to the parent. But, you've got more working years ahead of you than he states.
Luke, help me take this mask off
In fact, you are not old at all (you can't be old: you're younger than I am).
You are over thirty, though, so your brain is fully mature.
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
Asking such a question about anything shows that you are too old. Whether you are 12 or 52, you are too old when you ask such a question.
Do I want to learn a new and for what reason?
That is the question.
If I were independently wealthy...No, I'd never work again, I can't imagine anyone who would go to a job again if they didn't have to.
I'm not defined by my work....
If I didn't have to have a job, I'd spend my days tinkering around with things are fun. Some would be computer related, but not anything for money or that would likely earn money.
When I got tired of that, then I'd take a vacation. I'd spend my time learning how to do neat things..play guitar, martial arts....more time in the gym...doing all the stuff that I don't have time for because I have to work a fuckin' job for money.
Work is a means to make money, so I can buy and do the things I want to do in my life in the time I'm not working.
Why does that sound so strange?
Light travels faster than sound. This is why some people appear bright until you hear them speak.........
Make the leap to Consultant. Consultant is just another word for "continuous, steep learning curve". At 30 it's a setup for failure. At 50 it's just right. Am on my 8th year, strictly corp-to-corp (including via regular recruiters) and it pays incredibly well. Corporations just want solutions. You just want to code. Perfect!
You'll lose.
Become an expert in something the young do not know. That will give you more value.
Web development is the worst idea you could have. Everyone does it and it could be done by anyone.
Better make yourself irreplaceable by going for a niche.
It has been really hard to learn languages like lua, python and java.
The hardest part is programming elaborate workarounds to not having pointers.
These youngsters dont know what their missing!
Seriously - Yoga.
I'm only 29 but I'm obsessed with the concept of getting older and losing my razor sharp skillz :)
So I do Yoga, stretch, relax, read, talk, play. If you fully enjoy life you'll find that technology is just a tool. Your brain will be flexible and fresh enough to adapt to any situation. At least that's what I tell myself.
I've worked in enough environments to know how different they can be from each other. Yes, I spent a few years in a large company just like you describe. Everything was about politics. Management was incompetent, doing anything about it was impossible, trying to convince them they were making bad decisions just got you cited for your "bad attitude", and everyone's main goal was to keep their head down, protect their turf, and try to move up the ladder.
I've also worked in fantastic environments were everyone was competent, everyone respected each other, and we were all working together for common goals. If your workplace isn't like that, find another one. Don't make excuses for it or say, "That's just how things are," because that's not how things are everywhere. It took me a year and a half of being miserable before I made the decision to leave my large company, but I'm so glad I did. I now look back on those years like a bad dream from which I've since awakened.
And if you're in management, remember that you are responsible for shaping your company's culture. If everyone under you seems negative, if they're just interested in telling you things can't be done or have to be done differently, don't blame them; blame yourself. People act that way when they're in an environment that encourages them to behave that way. As a manager, you have enormous power to shape that environment. I've seen time and again how much difference a manager can make. When employees question their manager's decisions, a good manager sees this as a sign of involved employees who care about the direction of the business. A bad manager sees it as a sign of bad morale. The good manager engages the employees in responding to the criticisms, which leads to good morale. The bad manager blows them off, or worse, faults them for speaking up, which leads to genuine bad morale.
"I'm too busy to research this and form an educated opinion, but I do have time to tell everyone my uninformed opinion."
There is a ton of work available in C++ where I am. I've worked in C++ for about 8 years, having come from the Java world, and routinely worked with coworkers nearing retirement. Even better, many of the skills and good habits you may have acquired in more functional and finicky languages can prove useful.
If you want to pick up something cutting-edge and fresh, I'd highly recommend generic GPU programming. Highly sought after by computer vision and scientific computation, it feels like assembly and writes like C on LSD. There also just aren't all that many people in the field yet, so it's still at the point where writing a frame differencing algorithm on your home machine can be a foot in the door.
I hire experienced coders who know what I'm talking about and what I want. They are twice as expensive as the kids who are fresh out of college, but they are many more times as productive because they don't make the mistakes kids will make. An experienced programmer is worth his weight in platinum.
But I will add one caveat: if I detect rote thinking, a world-weary mien, or an inflexible attitude it instantly disqualifies a candidate. Ornery is fine, even good. But inflexible? Nah, that knocks 'em right out of the running. Why would I want to hire someone who cranked out the same piece of code for their corporate master for 20 years and who's going to be constantly snorting and pshawing every time I try to push the envelope?
So I'd say, learn the new language, pick up some nontraditional platforms like a smartphone or tablet, start hacking, and rekindle your excitement about technology. Be ready to haul out an iPad that you hacked during an interview and beam with your love of doing cool things with tech. Instant hire.
If you don't want to do that, probably better to stay in Project Management.
Do what you can, with what you have, where you are.
If it's too loud, you're too old.
These are my friends, See how they glisten. See this one shine, how he smiles in the light.
Really? And that's all you noticed that was wrong?
There are many good programming tutorials here:
http://www.thenewboston.com/
Java, Objective C etc..
I'm 55, a programmer, and I've been out of work for two years.
I'm a 58-year old Perl programmer and system administrator enjoying my challenging work.
1. I'm old. One 5 hour energy drink revvs up your basic 20 year old code monkey all day. I need a saline drip with caffeine in it all day to keep going.
I ride my bicycle 160 km each week, and have more energy than many younger programmers.
2. I'm expensive. I have 30 years of experience in the 'biz and a masters degree in CS. I'm not cheap. You could hire two 25 year olds for what I'm asking.
I am productive, have good control in deciding what I do, and enjoy a mentoring role.
3. I've been exposed to every nasty little mindgame management has at it's disposal. And sometimes I have the bad manners to call people on it. This is called "having a bad attitude".
I understand what pressures people are under, and get along well with my work mates and managers.
You are too old if you think you are. Otherwise, you can learn a great deal every day up to the day you die.
My background: Cobol, several business Basics, Pascal, a little 6502 Assembler, a lot of Perl (data mining and repurposing archival data for more than a decade). I have also managed to completely forget Fortran and awk. (And pretty much Cobol, too, for that matter).
My sense of where things are going: HTML 5 is going to require a lot of programmers who are really savvy in Javascript. Including its "advanced" features. The problem with learning Javascript is that of discerning good practice from the mounds of drivel that have been written about it. Javascript is THE language for front-end work in a cloud or client / server situation. You get to leverage all the stuff that is built into the browser. You also get to play with closures, prototypes (in place of classes), and anonymous objects, which offer several new ways of looking at problems.
On the server or cloud side, PHP is going to see an increasing amount of use. Its early versions had several intrinsic weaknesses but it has pretty much grown out of those.
Will
You are why I hate living in this country.
It's an occupational hazard of indoor manager/coder types.
http://www.vitamindcouncil.org/about-vitamin-d/how-to-get-your-vitamin-d/vitamin-d-supplementation/
Vegetable deficiency disease (in part from stress) is a killer too.
http://www.drfuhrman.com/library/foodpyramid.aspx
http://drfuhrman.com/library/article16.aspx
http://www.drfuhrman.com/library/PCI_angioplasty_article.aspx
Fixing both of those issues in my own life has led to more energy and mental clarity for learning new things.
Otherwise, code monkeys are at big risk of more than bad management from eating chips, drinking soda, and working indoors, which curtails the time for learning on this plane of existence:
"Code Monkey"
http://www.youtube.com/watch?v=v4Wy7gRGgeA
Exercise, good sleep, and other lifestyle issues can also contribute to having more energy and more mental capacity.
http://www.bluezones.com/
Also, there is a lot to be done for improving software projects beside code, so you might be able to push your project management skills in new directions, like discussed by David Eaves here for FOSS projects:
http://www.slideshare.net/david_a_eaves/community-management-presentation/
A 21st century issue: the irony of technologies of abundance in the hands of those still thinking in terms of scarcity.
You can learn a new language. I don't know if you can get a job, but that's not necessarily your fault. I would say there is definitely a bias against older developers. A real mistake, IMO, but ... I really think that knowing assembler of any kind gives any programmer a 'leg up', especially if significant assembler coding has been done (PIC, ARM, Arduino, etc.). Especially today with new CPUs, portable devices and the explosion of embedded CPUs in practically everything. It depends on what you want to do, and whether you really like doing it enough to follow through, even for no return.
Even though I am post 60, I am still actively working as a software developer. Attempts have been made to move me into management, but I don't want to manage. I also plan to keep doing it until I drop dead. I want to design and develop software. This is what I like to do. If I left/lost my job, I would have a hard time finding another, I'm sure. So, I would probably try cell phone apps or something like that. I do keep current, but work mostly in C/C++, PHP and SQL doing 'back-end' development, but I can handle HTML, Javascript, XML and the like when needed. I have even done an app or two with Java MIDP which is still used on many cellphones.
I do it because I like it. It's what I want to do. What do you want to do?
I'm also currently in the process of learning VHDL, which is sort of a programming language too (even though it ultimately gets translated into hardware). So no, IMO you're not too old. But also keep in mind what the guy who posted the first reply said.
At this point, I figure switching jobs may be difficult given the economy and my age. I'm hoping to hang on to the day job for now, but get back into doing a little consulting on the side. If the consulting market really heats up, I may consider going back to doing that full-time (which is what I did until about 6 years ago).
My father is over 70, not a programmer by trade, and is still learning new languages (Lua & Python).
The issue, I think, is motivation. Despite all the criticism he has for every non-C++ language ("leave my memory be!"), he has fun learning them -- and applies them successfully to his research projects.
if you have to ask, you've lost your edge. I'd focus on flipping burgers.
there are 3 kinds of people:
* those who can count
* those who can't
"Dr. Lixia Yang (above) and her co-author, Ralf Krampe of the Max Planck Institute for Human Development, Germany, found that seniors were able to retain 50 per cent of concepts they learned almost a year before."
If you are having to ask the question, like you need permission, perhaps you are too old. Don't go gabbing to a bunch of people with nothing better to do than scan comments and comment on comments on old articles and re-hashes of re-posts. Go study your new language, instead. I was 35 when I quit my job as a Java web developer and started medical school. I'm going to finish in May of 2012. If I had asked others if I could do it, I wouldn't've gotten up and gotten it done. They would have told me I was at a comfortable job, making a comfortable living. Why would I do any such thing that might impact my family? My family managed. I'm still happily married. We haven't starved yet or had to live on the street. It's working out. Go. Learn your new language. Do not ask other people if you can or cannot do something new. The only person in the galaxy that can actually answer that question is you. You are welcome.
I'm a 37-years old hardware architect/system engineer/logic designer; worked in a several start-ups and large companies. In the last couple of years I published a few well-read articles and a 478-page book on FPGA design. Will see where it leads.
Why?
Light travels faster than sound. This is why some people appear bright until you hear them speak.........
Interesting thread. I am an engineer turned programmer due to a combination of job-market and my interest and abilities in programming and algorithms, and I am up there in age (56). I enjoy solving problems and working technically and so never tried to move into any kind of management. And I also have this fear that one day I no longer will be considered for a new job (if I need one) because I have gotten too expensive. However, due to company finances, I have had to change jobs a number of times over the last decade, and each time, despite receiving a depressingly large number of rejections, I have managed to land something. The reason? Not because I am an expert in any particular language or technology (I have no formal software development education, and have programmed a little in just about everything including APL, Fortran, PHP, Java, C++ etc. etc.) and I am at least factor two more expensive than most of my colleagues. It has been explained to me that I have been hired each time because there was a need for someone with more experience in general, and with a more general broad experience in various aspects of IT technology. Programming APL after having knowledge of C# code architecture makes one a better APL programmer. Likewise, programming Java having algorithmic experiences from more engineering type jobs working with Fortran and Pascal makes one a better Java programmer. Not every company, but many have so far been willing to pay my salary instead of hiring another far cheaper, perhaps more formerly educated in some language but less experienced colleague. In short, there is still a vast need for non-managerial highly technical employees with a large experience base (either broad like mine or focused in a particular technology). It is just a matter of finding the enlightened employer needing such a person.
Well, I wouldn't say you're too old to learn, but it only depends on you.
I've been programming the last 25 years of my life and as I'm reaching 55, and after starting with the Z80 Assembler and Pascal, continued with C for 10 years and for another 12 with Java + SQL, I'm now learning Python :D
I think the real question is: "Do you really want to learn another language?"
I'm 58 and still do a lot of programming. It is in the nature of the job to keep learning. I teach CS at a a university and learn new things regularly. I dove into shader languages and the new style of GL programming this spring. I think I can learn fairly readily, though I do get a little tired of looking up things I already know perfectly well how to do in C/C++. I assume this comes with experience more than simply age. 40 is fairly young for thinking you might be a little old for learning new things. I hope to remain capable of learning new things until I die. Having my brain start to malfunction is not a happy thought.
Some of the posts mention that experienced programmers can bring better solutions to the the table. This is true for those who work and study. It is not a natural result of aging or of continuing to program the same type of application over and over again. This kind of thinking usually results from having worked on a variety of project requiring different solution techniques.
Programming was simpler when I started in 1976. On my first job I recall reading the ANSI standard manual for Fortran 77. It was short enough that I knew essentially the whole language. C++ is probably about 10 times more language to learn than Fortran 77 and I don't think I have it all memorized. Added to that is the enormity of libraries available. Any libraries I used on the first job were locally developed and extremely small (16 bit computers with 64KB program size). Today the library possibilities are endless. No one can be an expert in all the libraries available for C++. The essential requirement for success in programming (other than programming skill) is the willingness to learn.
I seriously doubt that most people with 35 years programming experience would be much better than 25 year olds with 10 years experience. I think I am pretty good, but the best of the graduates from our program are probably pretty close to equal in skill by 25. Age may bring wisdom, but not even that is guaranteed.
Ray Seyfarth, ray.seyfarth@gmail.com, http://rayseyfarth.blogspot.com
Some examples:
Respect the Constitution
I'm not an Apple fanboy but, if I were confronting learning a new language right now, I'd learn Objective C and focus on iPad development. Then I'd focus on whatever language and framework serves it's biggest competitor best. right now Android is looking good but you've got at least 2 years before you should even think about anything other than Objective C.
WHY, Objective C? Why iPad development? Well, it looks like your accustomed to DECENTLY DOCUMENTED LANGUAGES AND FRAMEWORKS. iPad developers enjoy the best documentation in the industry. You're first task is to update the markets you serve - iPads cover the mobile and tablet markets. Your next task is to become platform agnostic after proving your value in iPad development.
Old, experienced guys are turned to every time the enterprise transitions a technology from the exciting PR move to the mission critical line of business. If I were you I'd take a PM role once every 4 years or so to keep that option open and do what you love enough to excel at. (Yeah, I dangled a preposition)
Every rule has more than one consequence.
In other words, start a company. If you're not inspired, find someone who is -- you'll need a team anyway. There's no security, no health care - wait, that's pretty much of jobs. Especially if you lose a job. Some may call it a bubble, but however long it lasts, right now there's plenty of money chasing social media plays, and a few other techie kinds of things. Take it and you may succeed. If not, you're actually better off than you were before, because now you have startup experience, and are more likely to be hired into another startup.
Michael Odza, Digital Media Strategist
Your comments sound rather /extreme/ to me. If you could, you'd spend your time on nothing but the things you like, but since you can't, you go for the "whatever it takes" approach hoping that one day you'll be able to do whatever you like.
Yes, you're right, *IF* I'd win the lottery I would likely give up my (current) job too and spend my times on other things that have peaked my interest over the years but were out of reach due to time/money restraints.
However, since most people realize upfront it's quite unlikely they'll win the lottery they look for a way to still do those things they find interesting, even if it is in a restricted way. And if those things "coincidently" can be combined with making money then I think at the end of the line they (we) 're better off.
It's all great to plan ahead and give up "your best years" right now spending the biggest part of your active time on things you don't like simply to make as much money as possible so you can do whatever you want during your (early) retirement. I sincerely hope it never happens, but if you're diagnosed with cancer in 10 years time (more likely than winning the lottery btw) you'll feel VERY cheated by life ...
IMHO, it's all about balance.
If there is one thing to be learned on slashdot, it has to be sarcasm.
creativity, ingenuity and energy are the domain of the young. responsibility is the domain of the experienced. but... the more skills you have the more valuable you are. even weasly execs that have been butt fucked up the chain of command can be in the firing line at a moments notice. the old "its not what you know its who you know" is mostly true, but in this economic climate, "money talks and bullshit walks" is much more valid. you can bullshit your way to the top, but chances are everyone knows thats how you got there, including your boss. many people also get pushed up the chain of command to keep them from getting in the way of real work (the Dilbert principle). if you find your job easy, you're in the wrong job. if you're not fucking up occasionally or getting stressed, you're in the wrong job. if you're a programmer, learn a new language (if you're not familiar with web languages like php then that would be an excellent place to start - mysql & php for dummies originally got me going). the more you can offer your employer, the more expensive it becomes for them to replace you. also, don't be a pain in the arse but don't be one of those quiet ones that it takes a week to notice that you've had a heart attack and died at your desk; be a little assertive and make the odd suggestion that you can back up. some companies make it hard and some bosses are just morons so in that case i feel sorry for you and you should keep flicking out resumes if you hate your job. at the end of the day as an old fart, while you may think you're worth more, your best bargaining chip (if you can afford it) is that you can always accept less than what you're worth, and if the alternative is a pension then you might want to consider lowering your expectations to compete in a dog eat dog world. everyone wants to make more money, but if you're in an industry where your abilities are shared by 20-something year olds, then you're kinda limited to competing with them (even in management you face the same prospect). a career path where experience does count for a lot is engineering (and i'm talking about real nuts and bolts engineering as opposed to "software engineers"); graduate engineers will never match their experienced counterparts because engineering is about judgement and that ability can only be gained through experience (ability to look at a bridge design and know if its strong enough). but there are also other careers where experience is worth a lot, such as airline pilots; basically any job where fuckups can kill a lot of people. while there are plenty of programming jobs where fuckups can kill (such as programming avionics gear), there wouldn't be too many run of the mill web app or windows programmers in that position. judgement is made in programming; for example experienced programmers can probably come up with something more effective, but managers know that if you throw enough cheap young energy at a programming problem you'll eventually get there by brute force, and companies aren't interested in good quality software; they just want something they can sell for a profit (and if there is prospect for support and customers having to pay for upgrades and bug fixes thats even better).
If unfortunately *you* found yourself out of a job, I don't know if any CEO would hire you. You've basically said that at under 50 you've already checked out. You're only willing to give the company only 8 or 9 hours a day, never on weekends. You have a very bad opinion of many of the people who work for you, thinking you know their job better than they do. You may believe you're better at hiding those opinions than the programmer who's out of work, but really it doesn't fool anybody after awhile. It doesn't sound like you are a very enthusiastic supporter of your CEO. Given the attitudes in your post, what CEO knowing about them would hire you for a VP position? In short, I really don't think you're any better than the poor guy that started this thread, just luckier.