The Grumpy Programmer has Advice for Young Computer Workers (Video)
Bob Pendleton calls his blog "The Grumpy Programmer" because he's both grumpy and a programmer. He's also over 60 years old and has been programming since he was in his teens. This pair of videos is a break from our recent spate of conference panels and corporate people. It's an old programmer sharing his career experiences with younger programmers so they (you?) can avoid making his mistakes and possibly avoid becoming as grumpy as he is -- which is kind of a joke, since Bob is not nearly as grumpy as he is light-hearted. (Transcript covers both videos. Alternate Video Link One; Alternate Video Link Two)
"Bob Pendleton calls his blog "The Grumpy Programmer" because he's both grumpy and a programmer."
Thanks, Rob!!
You were critically hit for no damage. The bruise will look nice, and maybe the scars will make good party talk.
The transcript reads like a conversation between two guys with almost nothing to say. I'm honestly not sure what my takeaway from this should have been. Guy was a working programmer for 30 years (unemployed for the last 12+), and now he's... ...a guy making small-talk in a video?
Help me understand what I missed.
Robin Miller: But age discrimination in employment, have you encountered?
Bob Pendleton: Oh, absolutely. I got laid off on my 49th birthday and haven’t been able to find a full time job since.
One piece of advice I always give younger engineers and programmers is to be increasingly vigilant about your career as you age. In the last decade or so before retirement one is very vulnerable to layoffs, because one's salary is high and one's formal education was a long time ago.
I'm one of these grumpies. Some of what I had to say may be useful to the wet-behind-the-year dopes. Not likely, though, because, back when I was at their age, I didn't listen to the old geezers, and that both helped me as well as screwed me.
So, given the rapid speed of change in the landscape of IT industry, I have to wonder how relevant our experiences and lessons would be to the young'uns.
Fuck systemd. Fuck Redhat. Fuck Soylent, too. Wait, scratch the last one.
It's 2014 and we still have streaming video served up as FLASH???? ON SLASHDOT?!?!?!?!?! What a joke.
I am not sure there's much advice us older programmers can give new developers because the industry is a lot different now.
In the old days we were often tasked with solving a problem, and we were more-often free to use whatever tools and technology were best, and we also thought of development environments as tools, which we could switch out if the application required something different. We also did all our own testing. I recently worked with a younger programmer on a project and it was miserable. He couldn't give me 20 lines of code that didn't have a bug in it, because he was dependent upon having some QA person test his work and an IDE that would hilight every mistake.
Nowadays there is so much abstraction going on in programming, people don't really seem like they're programming as much as they're using some sort of GUI development tool and plodding through innumerable amounts of API documentation and going on witch-hunts to try and figure out why something that's documented to work, doesn't actually work. I remember a big Oracle project I was on where my software wouldn't work properly and I couldn't figure out why. It took me several months of bitching on usenet to finally get a rep within Oracle contact me privately and tell me I wasn't crazy, they knew about the bug and just weren't acknowledging it. In the old days, there wasn't as much of that going on. Programming was simpler and less bureaucratic.
. Only those few who specialized in now ancient technologies will have any prospects beyond age 40.
Maybe it's you? I'm 45 and recruiters bother me more than ever. I keep my tech skills current, and carefully manage my career so as not to get stuck looking like an expert only on old things. Senior engineers are golden right now - I find it a great place to be. If what I do could be done by a kid anywhere, well, I'd be a terrible engineer after 20+ years.
The worst part is, there is no such thing as job security.
True enough, but it doesn't matter. Other than during the dot-bust, it's never taken me long to get a series of interviews whenever I wanted/needed a new job. This is not a career where staying for a long time at any company is usually rewarded, this is a job where technical success stories on your resume from many years of companies are rewarded.
If you want to join the Video Game Industry, all this same stuff applies, only cranked up to 11!
Any job that sounds fun like that will be exploitive and pay less. There's likely no worse corner of this industry than the large game companies. Find something to work on that puts your friends to sleep when you describe it, but people in the industry know is important.
Socialism: a lie told by totalitarians and believed by fools.
Actually more often I have seen the opposite: claims the new stuff is going to be faster, the compiler is not smart enough to figure out that they are the same, and thus you should use the new stuff.
There was a coworker who insisted that using C++ std::foreach for loops was faster because "the compiler knows you can't break out of it and thus can optimize the whole thing". I had two objections to this: first of all it would be a really stupid optimizing compiler that could not figure out there are no "break" statements inside the for loop. And second the C++ was still allowed to throw exceptions in both cases.
The other objection I had was that the functors were unreadable.
Yet another objection is my suspicion that the optimization would be far worse on the functors due to the enormous header files of templates they actually used and I expected the optimizer for the simple for loop to have fewer bugs in it. But I did not test this.
when I discovered that he doesn't bother to proofread or use a spell checker.
I don't care how long he's been doing it, sloppiness is a sign of a poor programmer.
Do you happen to know who is in that picture? That is John McCarthy the inventor of Lisp. The joke is on you.
And that's why, if you can, you go back to college to get a Bachelor or Masters degree when you get into your late 30's early 40's.
That is the worst possible advice you could possibly give, except I guess for killing yourself.
That is when instead of SPENDING ALL YOUR SAVINGS ON SOMETHING THAT WILL NOT MATTER, you should instead think about switching to consulting and increasing your earnings. Can't find a full-job easily past 40-50? Learn to make people pay what you are really worth for the vast amounts of experience you have, because that is worth a lot, save up what you can and enjoy retirement eventually, possibly a lot earlier than you would have if you burned your money like an idiot getting a business degree so you could be unemployed with all the younger business majors who cannot find jobs either.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
As I near the end of a nominally successful electrical engineering career that spans the humble analog beginnings of automation to the roboticized present, I can look back and smile at what a smart-assed punk kid I was, deriding the old-timers with snot-nosed comments and the immeasurable over-confidence of youth.
Barring an early death, everyone gets old. Know what? I neither desire nor require the respect or veneration of the young. I got mine. As jobs get scarcer and pay less with each passing year, all I can say to the smartaleck young snerts is, "Suck it. See you in St. Croix."
On the other hand, ask me nicely and I'm happy to lend a helping hand.
Respect is a two-way street with no speed limit.
Scruting the inscrutable for over 50 years.
No, the real joke is that he never actually said that.
SJW's don't eliminate discrimination. They just expropriate it for themselves.
Yes, age discrimination is horrible and very real. I just hit 45 and am seeing it first hand. I work for a 'hot' type company and they actually said in a company wide meeting 'look around you. Notice that you don't see much grey hair. That is on purpose as we want people on their way up, not out'. I was shocked. Meanwhile their people 'on the way up' hack out some of the worst code I have ever seen. We could use a few more people on their way out to actually make some scalable and well architected products so our servers don't fail under the weight of this pile of crap they created. Thing that sucks is I am right now the best I have ever been with all of this experience and I am afraid it is going to get harder and harder to get a decent job.