1) A young company, light on technical background, has build a castle on webscale sand. A few of the smarter young folks have become experts in this system, and get a lot of clout by solving "difficult" problems. Suddenly an old guy comes along and says "lets just use MySQL and CREATE INDEX". Basically, he's been there, done that, and realized that J2EE + MySQL will get the job done with a minimum of fuss, or that the "simplification" that comes from denormalizing carries a huge maintenance penalty.
This old guy threatens the young "experts" - if the system is rebuilt according to industry standards, suddenly they are just another dev.
2) The old guy hasn't kept up with the times, and is stuck in ancient (and outdated) ways of doing things - manual management of memory, FooBarFactoryFactory, etc.
You can't transpose these justifications onto non-Asian minorities, women, etc. A non-Asian minority or female 25 year old is fundamentally equivalent to a white/Asian 25 year old male. Nodejs is equally "close to the metal" regardless of your demographics.
Tech in 1996 was radically different - a CD ROM filled with a small subset of wikipedia was actually a huge technical challenge. As a result the old guy really is different.
On a personal note, at my current company I'm both the oldest techie and also the only techie who isn't a member of the majority ethnic group (sliced in US terms, at least). My age is a significant factor - I'm sometimes out of touch (I know fuckall about angular.js) and sometimes I'm the voice of experience (we should have a metrics server and use it for all the things). My ethnic diversity is completely irrelevant.
Garbage collectors have been around since the 60s with LISP.
I find it amusing to see that the first language I was taught in an academic setting in 1996, Caml Light (ancestor of OCaml), is still very relevant today!
I wish my application to Linn to work on the Rekursiv hardware had gone a bit further though...
[NB I am resisting the temptation to comment on the assertion that Lisp is a functional programming language! ;-)]
Cambridge Lisp was written in BCPL which was one of the languages provided with the machine so you probably wouldn't want to completely replace the instruction set.
As the saying goes, every field learns from its history - except software development.
There are also a lot of "new and hot" things which are not programming language features at all - e.g., the lambda architecture, the rise of bayesian inference, and other such things. Even relational databases - so old that it's easy to forget they were "new and hot" (with good reason).
All of this is quite old too. As I said, I learned ML as an undergraduate in 96, 20 years ago. Back then, many "hackers" laughed about such languages.
Actually, that's why I think a more foundational CS curriculum is a good thing, as opposed to those that are heavily based on technologies.
Interesting you brought this up, because I've noticed two different approaches to this from older developers. One group is exactly like you describe, still tracking every single precious byte their code uses.
The other is like "my first PC had one megabyte and cost $3000 so don't tell me I can't allocate half a gig to this process here's $5 just go buy some more RAM!!".
What is held over from the old days is efficient code. Not just big huge blocks that are unknowns. Ability to profile and REALLY debug, particularly profiling. Each cycle counts as much today as it did then. Seems most newer programmers were never taught that. Even web code at scale need to be clean and quick.
That dovetails nicely with "culture fit", and both points are also unfair and possibly untrue stereotypes. So I wouldn't count them as counterexamples to the above maxim.
People complain that old guys program like they never left the 90's. No one complains that an ethnically Mexican person never left Mexico, or that someone "programs like a girl".
The only code related ethnic stereotype I've ever heard is about Russians/Ukrainians/other slavs; a lone wolf writing efficient, high quality, extremely monolithic code, usually in a non-trendy language (PHP, C, C++, sometimes Erlang or old school Lisp).
Old people tend to not want shitty deals.
It's why Al Queada use suicide bombers its cheap to train and does not need high quality recruits
- under 35 years of age at entry
- at least 10 years' service
- at least three campaigns (some had as many as 12 campaigns)
- had to literally face enemy fire at the front and survive
https://en.wikipedia.org/wiki/Old_Guard
I wonder what the tech equivalent is?
Programming involves less drama, but every now and again you need the services of someone who knows the system inside out and has a collection of weird tricks that will get you working again.
I think Al Qaeda uses suicide bombers mostly because they're hard to detect and let you strike a target with zero warning; it's an ultimate guerilla tactic. That young engineers tend to be particularly happy to wear the explosive vests seem to be incidental and not the reason for this tactic.
I agree with your French/British example though.
If old people have a great deal from their current employer, they'll stay employed and the number of old people in the industry will remain constant. If old people find themselves unemployed due to a reorg or startup failure or whatever, they'll take the best deal on offer - and the number of old people in the industry will remain constant.
If the number of old people in the industry is falling, I'd be interested in some statistics about where they're going.
I don't know how many are getting jobs, but I'd guess that a lot are taking early retirement. If so, the number of older workers is falling....
As a statistical aggregate, the amount of useful, valuable, monetizable work done by a human for a fixed quantity of effort positively correlates with the number of hours they have performed the same work over their lifetime. Even in tabletop RPGs, a level 20 character can soundly stomp a level 1 character of the same class. Why do so many people seem to think that experience only counts in games?
If young people do indeed work harder, it is probably because they have not yet learned how to work smarter, and they still have to compete with older workers. They can work harder, accept lower pay, work more hours, produce less work-product, or some combination.
Anecdotally, I know for a fact that I don't work anywhere near as hard as I did when I was younger. I don't need to.
That would make management look bad, so ...
"Put in more 'face time' without complaining."
There, I fixed it for you :-) I do agree with your post, BTW.
For instance, "More experienced people are likely to look down their nose at company culture" doesn't really have a comparison with any other protected class.