Um, I'm 54 and the languages of my 20's were C, C++, etc.
I also fairly regularly get calls from recruiters.
> So yes, you either need to find a job that doesn't change (eg a plumber or a teacher) or you need to constantly battle to maintain relevancy in a fast-changing industry or you need to become master of your own fate.
Or, you can be a driver of this change yourself by developing a modern, advanced programming language.
Not everyone has a wikipedia article :)
1. create a website from your own name, like walterbright.com, and put your professional work there
2. create a github account under your own name, and contribute to significant projects using it
3. ditto for stackoverflow, hackernews, gamedev.net and other relevant forums
4. write interesting and useful tech articles under your own name
I.e. your name is your brand, make use of it. If you use a pseudonym and hide your contact info or otherwise put up barriers to being contacted, you'll lose opportunities.
Aside from that, one the best ways to get recruited is to show up at tech conferences and engage with the other participants. A lot of companies use tech conferences as ways to find good engineers.
If you're broke and can't afford to go to a tech conference, submit papers to them and try to do a presentation - speakers usually get expenses paid.
In my experience using a pseudonym consistently works just as well. Most people don't even realized my "real" name isn't Swizec until we start signing contracts.
Yes, I also introduce myself as Swizec when meeting people in person. Especially people who might google me.
The fact that you are the inventor of the D programming language puts you in a very different league of people.
The C guru looked at me and said "Who the fuck do you think you are thinking you can write a C compiler?", and not in a nice way, either.
So what's stopping you?
And frankly your post had me thinking this whole afternoon.
What is really stopping me. And I have to frankly say, Nothing. Thanks for this valuable advice.
Internet branding is overrated. Personal network is a lot more important :)
I'm 53, know many engineers 45+, none of them are (still) hawking their Cobol/Ada/Forth skills. Just like the young 'uns, we learned C++, Python, Java, Javascript; we use node.js (if it's indicated), we read HN and other tech sites, etc. If we don't, then we're idiots and deserve not to get hired, and we know that.
One thing I've discovered is that knowing the new stuff in conjunction with some of the lost arts (messy old C builds, hardware-related mysteries, debugging without debuggers) gives me some skills that are not easy to come by, and that is a real advantage getting work. There will always be legacy systems that are 10-15 or more years out of date, and a market to keep them running.
the languages of my 20's were C, C++, etc. As in "I wrote compilers for these languages".
If you aren't getting calls from recruiters, then none of the rest of us will.
For those of you who don't know, he wrote, so far as I can tell, the first native c++ compiler.
ex-MWC guy: ...ihnp4!mwc!wgl
Judging by HN, about 60 per year
Do people really think if you're 45 you worked in Cobol?
It's a weird time to be a mainframer. If you are an experienced specialist you can charge insane hourly rates. At the same time, some bigger orgs have started transitioning off the old stack because all the experts keep dying or retiring.
At some point mainframe specialist skills will go from insanely valuable to completely worthless.
Although after I left Quantico they put me in a billet working with dBase III, I could just as easily been assigned to a billet at a RASC where I would have been using COBOL.
I once worked at a startup whose cofounders told me that I was the oldest person in the office (having just turned 26) because "people over 30 don't get technology", meanwhile, they couldn't understand HTML, much less programming, and therefore had to hire me.
The very best programmer I know works primarily in Ada at his day job, whereas I know all the trendy web fads. If I had to choose him or me as an employee to write code, regardless of language, I'd choose him, objectively. If he starts working on whatever I'm working on, he'd almost certainly be better at it than me in a week. Whenever I have a difficult programming problem, I can struggle with it for hours (or days), and he can make it clear in minutes. He can look at my code in a language he's never seen before, for example, and solve my problem. It seems like a lot of companies are in the habit of hiring resumes instead of people.
The older you are, the more time you've had not only to gain concrete skills, but to learn to abstract your existing skills and knowledge to apply to other things.
Some of the seemingly widespread opinions in this industry (or at least among startup scene types) make me wonder how most of you manage not to drown when it rains. Some of the stuff I hear just makes no sense. It's not based in logic.
Fortunately for guys like my friend, defense contractors and other huge corporations will be hiring devastatingly skilled people who have "boring, obsolete" skillsets for the foreseeable future. They're probably too smart to work at our on-average-destined-to-fail startups anyway.
Contrary to popular belief, computer skills really don't decay that much. "New" things aren't really that new, they're almost always related to or based on something we've seen before, and if you're really any good at what you do, it won't take you long to get a grasp on it.
Analogy: If you wouldn't hire Bruce Lee because he doesn't know the latest direct-to-DVD self-defense technique by Generic UFC Guy (TM)... you're making a huge mistake.
tl;dr: make snap judgements and you're going to wind up sub-optimal employees.
Unfortunately the older your are, you are less flexible, less adjusting, running short of energy, you can't take risks as you have a family, you can't work too hard or push yourself too much because there are health risks associated with that. The list goes endless. Its not a very comfortable position to be in old age.
As some one who is in 20's and watching people in their 40's(My uncles) and my father(in his 60's) I can tell you the only chance we engineers have is to make loads of money, real estate and savings before we are 40-45. Else we are screwed. That unfortunately is the most blunt way to put it.
You may believe in whatever you may like about experience coming with old age, but your employers will take raw passion and energy over accumulated experience any day.
Your best bet is to make a lot of money and be safe or risk going through a lot of pain when you grow old.
I don't spend as much time on work as I did when I was younger, but I get a lot more done. I have also learned a few things about how to motivate myself (eg, delayed gratification)
If you're trying to live a good life, your best bet is probably not to focus entirely on making a lot of money, but to find what makes you happy. As a physician, you get to meet old people. Now that I know some old investment bankers, I don't envy the ones who focused on making tons of money. They can't climb the stairs to their ocean view bedrooms, they can't fit into their British sports cars and they never have time to drive them. Managing the paperwork of their assets becomes their full time job.
My dad is a 68-year-old engineer, he seems happy, and making more than ever as a consultant. The fact that he likes restoring hot rods works well when the money guys find out and they can exchange pictures of Shelbys.
Best advice for growing old: buy a one-story house. You can get to your bedroom and your kitchen.
(1) http://www.nytimes.com/2010/06/01/health/research/01happy.ht...
Bull Shit. Stereotypes are just stereotypes. If you follow one you will be one. I am 41 year old engineer(programmer) & Entrepreneur. One project I am coding now has Java, C++, Go all together. The younger programmers in my team were sort of scared to touch C++ part. I am encouraging one of them to learn Go.
I do two projects at a time, one of my own and another for a client. Support the former a bit with the consulting money I get from the latter.
I wrote the above to counter your ageist myths. You are younger and I presume flexible enough to correct them :-)
PS: I didn't down vote you BTW.
Why would you think so? I left home at age 18. My parents were 37 and 40 years old at the time. At that time and for many years after that, I had tons of non-work priorities, certainly more than my parents. And I don't think that's an exception. Most people never really make work their priority. Don't mistake that for an age related phenomenon.
"Is it an example of ageism if someone who is 45 can't find a job when what they know is Ada, Cobol and Forth?"
No. Is it an example of racism if you didn't want to hire a drug trafficking nigerian scammer and pedophile as a baby sitter for your 5 year old daughter?
The idea that these are even relevant examples is ageism or racism. I don't know a single 45 year old software engineer who knows Ada, Cobol and Forth. They didn't serve in Vietnam either.
Everyone knows they have to be up-to-date with current technologies and it becomes easier with age because many changes are very superficial to the point of being trivial.
Ruby is Ruby, but do you use webrick? mongrel? thin? unicorn? passenger? Whoops! You chose what?! everyone knows that hasn't been supported for 6 months when the guy writing it quit supporting it because someone insulted him on a mailing list!
The stuff around a language is generally what changes more often than the language, and keeping up can be a challenge, regardless of age.
Do you mean 'software' engineering? Given its about a 40th reunion, it's likely the comment was about a more established field of engineering.
If anything I would have thought there would be more 40-60 year olds in the work force than 20-40 year olds (or at least a close number). So either some of them have to move into management of non technical staff or you end up with a very top heavy management structure.
Tech companies seem to prefer a flatter management structure to avoid too much bureaucracy.
Not so well. Pyramidal company structures get narrower as you go up.
"Moving to management" doesn't mean you suddenly just create Powerpoints all day. If you're a good technical manager you can suddenly use your skills to multiply your contributions far beyond what you'd be able to do as a single person.
Let's start with the common premise that a good programmer is 10x better than a bad one. A good first level manager, who has 10 reports, could effect a difference of 100x. And a good senior manager, who has 10 midlevel reports, could effect a multiplier of 1000x.
If approximately half the workforce is between 40 and 60 and half is between 20 and 40, then half your staff are managers. That would work if only two people report to each manager (branching factor of 2), but it seems very inefficient to have so many levels of management: log_2(#staff).
On the other hand, with a branching factor of 10 only 1/9th of your workforce are managers, so management positions only support those between 55 and 60.
The point of the original comment was that you can't have "move into management" as the default career track for people in their 40's. There just aren't enough management positions.
Totally agree. The thing is that that applies not only management but to senior development positions as well. Most firms have no need for a workforce that's 100%, 80% or 60% senior devs. There is a LOT of grunt development that needs to be done and the older you are the more money you're going to want.
We can call them managers, senior devs, whatever, but the truth is that there's not enough room for everyone to constantly be moving up and making more money. Engineers have created a very egalitarian workforce and in most cases it's great but this is one of those cases where it doesn't work. Industries that have been around longer have already figured this out (law, banking, etc) where you have the "up or out" mentality. There's been a lot of work and research done showing how and why this works and how to create the proper balance depending what sort of work you're doing. The more cutting edge work you're doing the more senior devs you need but the lower percentage payout the partners get.
It's not a matter of moving people to management or not but a simple fact of we can't all be at the top of a firm and if you're not moving up it's better to replace you with someone younger and cheaper who can do the same thing.
Check out the book Managing the Professional Services Firm for more, it's a great read and really applies to software.
Engineering is an art.
In tech you are trying to make something no one has done before so you want the young hungry engineer.
My experience indicated that they were planning to use too many "new things" simultaneously. If any one beta-level technology failed, the whole project would fail. My Plan B was to essentially solve the main problem it was meant to solve with a minimal core built with tools we knew would work. Put that online on time, then incrementally upgrade features using the new technologies.
Since my group would need some of the services of this software project, I went off and built part of Plan B myself (the part covering what our group would need) as a secret side project using old fuddy-duddy technologies that worked but weren't new, exciting, and unknown. When the 90-day project wasn't ready on Day 90, I put my own online. It worked perfectly. This VP and her minions were angry about it. "It demonstrated a lack of faith in her team."
Two YEARS later, their 90-day Plan A finally shipped. She and the CIO never forgave me, though. I, the old guy, had used 80/20 to deliver the core of what was needed on the day they said it was needed, and I did it alone. Still, they remained convinced that "young, hungry" engineers were more likely to "be on board" with projects like the one they designed, and that was what mattered.
I've seen countless failures like this. I was able to stop a couple before they collided with harsh reality. It never got me any friends in upper management, but saved a couple companies.
If your success had made a big story, it would have become a case study. It becomes intellectually insulting to them.
It directly means they are not capable of doing their jobs properly.
One fact every one need to realize, It's great to be young. But age is not static. Those who are young today have a very narrow window of 9-10 years. Beyond that we are all the same.
The Asian locales had no old system to fall back on, so when Plan A didn't ship and I revealed my (fully localized) Plan B, they adopted it immediately. If I hadn't done my Plan B, the Asians would have had to go back to product registration by postcard.
Alternatively, choose the older engineer with the experience to know: "You know what? Fundamentally, what we're building here is the same as this thing from 10 years ago".
I walked through it with him and explained that you don't realize how much stuff is the same anywhere. Communicating with customers & stakeholders is the same anywhere. Working with your coworkers is the same anywhere. Managing a project has the same steps in every company and if you're good at it it will translate. Likewise requirements gathering. Your knowledge of various domains that you pick up. Etc etc etc.
MOST of what you're trying to do has been done before. All the day-to-day work that makes your business successful has been done thousands of times before. The only thing that's new is a few minor implementation details.
The other thing is all these founders are so young they may lack the experience or maturity to hire an older person.
This entire thread is based on the following:
"I saw this comment left on a Wall Street Journal article:"
So in other words somebody made a comment.
A comment!
Not a WSJ story even, or a story in a b newspaper or, but a blog comment.
Add: I mean if someone had posed an "Ask HN" question and everybody gives their thoughts (anecdotal or otherwise) that's fine. But this???
Add: With the resulting suggestion, once again based on a blog comment taken as being true, authentic, researched and validated: "Do your future self a favor, find another occupation."
1. Finding ANY job when you're 60 is hard;
2. Engineers (who are still engineers) at 40+ will often be passed over in favour of twentysomethings.
Engineering is such a young industry that I'm not sure we've really faced (1) yet (since the number of people who started engineering in the 70s is but a drop in the ocean compared to the number in the workforce today). It'll be interesting to see how the industry has evolved in 30 years.
(1) is a pretty strong driver for everyone having a long term plan to control your own fate, which means working for yourself. That is, if you're not in industry with inbuilt protections (eg teaching).
(2) is harder to pin down.
On the one hand, there is a certain (un)survivor bias in that many who started as engineers in their 20s are managers or the like by their 40s. So are those who remain in engineering a good sample?
Also, the older you get in general the more non-work priorities you have. Family, for example. This can reduce the amount of time you spend on self-improvement. This industry almost requires constant learning, reinvention and skill acquisition. Is it an example of ageism if someone who is 45 can't find a job when what they know is Ada, Cobol and Forth?
It's often said that a good technical foundation and education means you can pickup any language. This is true but picking up new skills is both a habit and a skill, one that atrophies if left untapped (IMHO). It's also a question of degree. Perl to Python? Not a big gap. Ada to Ruby? Well....
That all being said, there is age discrimination in this industry. I've personally witnessed someone say "I prefer new grads so I can mold them". That's fine and all but if you say that and don't hire a 50 year old programmer that's a good basis for an age discrimination suit because, well, it is age discrimination.
So yes, you either need to find a job that doesn't change (eg a plumber or a teacher) or you need to constantly battle to maintain relevancy in a fast-changing industry or you need to become master of your own fate.
This is known.