Time for the world realise this tech stuff and programming has been around about 100 years! Let that settle in. A century of code. So the tech population is now clever and curious 8 year olds all the way through to 80+ curious and seasoned Algol programmers. And we ALL have value.
#endofrant
https://www.jpl.nasa.gov/edu/news/2016/10/31/when-computers-...
You will also notice the words "computer", "input", and "output" are used without needing to be explained.
Every new cyle comes with ideas that are similar to what we have seen before. Sometimes I find myself thinking, OK, been there, done that, doesn't work. But I suspect that there is a sort of experience bias that lets me see the similarities far more clearly than what's new and different.
In every cycle people claim that it's nothing new and yet, with hindsight, we often find that small differences were important enough to change the world unpredictable ways.
I think it has value for older folks to contribute arguments and perspectives, but let's not be too self-righteous about it. Similar ideas can lead to very different outcomes in a different context.
The amount of "how do I justify a rewrite because our tech stack is bad" posts you see in your typical reddit/etc programmer forum would remind you of this.
These are old complaints.
My dad worked in the tech industry since the pre-Mosaic days, and even then you'd hear the same arguments and complaints.
The same way people complain about React today is the same way people complained about Spring, and then about how old school C programmers complained about C++ with it "training wheels", and BASIC programmers complaining about "OOP", and old school networking types complaining about built-in TCP/IP instead of spinning up your own stack.
Technologies and frameworks change. That's how tech always works. Sure I can demolish a building with a sledgehammer, but why not adopt dynamite or bulldozers if it efficiently solves the problem.
At some point, all these complaints are just Ludditism from techies who didn't upskill and/or are unable to communicate.
Us older heads know how often it goes wrong, and know that without a tangible user benefit or commercially positive outcome... It's just busy work.
Oh you are going to rewrite established solution X in Y in 2 years with 5 devs, and it's going to solve all of the problems we have in X, awesome!
Ignoring that solution Y is so new that the guy proposing it has never actually delivered an enterprise solution in it. And since they just got hired, they have no idea what the user facing problems X is actually exhibiting. Often the problems with X are organizational, managerial, and prioritizing. Switching tech doesn't magically change the decision makers.
Invariably hiring a guy who has a string of 18-24 month jobs on his resume, which, uncannily, is the typical runway of a Greenfield re-write project before heads roll.
Not every tech is the new Spring, OOP, etc.
Not every project benefits from being immediately migrated to the new thing.
Once you've been through a few train wreck "get on the latest thing" projects, you see the benefit of actually delivering to users, regardless of whether the tech is bleeding or trailing edge.
If you are a small tech org, the benefit of being able to hire a team of people who have SUCCESSFULLY delivered with TechX (which is 3-10 years old) can outweigh jumping onto the latest thing.
I think the problem here is the usual bloat and enshitification that these tools eventually devolve to due to their success. People get so used to them they want to use them for everything and create this universe where you now forgot why they were created and the places they were useful.
But what about all the mis-adopted or abandoned tech that blew up projects.
The amount of stuff ported to NoSQL that had no business doing so. UML/Nocode tools in the 90s.
A lot of the push away from Java only for a lot of performance considerations pushing devs back to it. Sorry about the projects that got force migrated to Scala since it was, briefly, The New Thing.
The one man webdev app deployed firmwide on some brand new framework which was immediately deprecated.
Again, nothing wrong with any of these tech choices if they were driven by actual user requirements which exceeded the current implementation tech. But most of us know that is rarely the actual motivation of devs...
MongoDB easy (in a way) replication put every single database vendor on watch and led even PostgreSQL to improve, i think we live in a different environment right now due to all the experiments the NoSQL folks made. It might not have all panned out but I think the whole thing was a huge positive for the market, people stated to experiment and try new stuff again instead of "oh it doesn't look like a relational model, it sucks".
I completely agree with this. I’m also in my 50s but I lean techno-optimist. Whenever there’s a new hype cycle, I’m looking for those small differences that might overcome the hurdles we’ve seen in the past. For example, the PicturePhone was demoed in 1964. Now we’re all on Zoom constantly. I’ve lived through many AI hype cycles. The current LLM craze is significantly different from past exuberance. LLMs aren’t perfect but they are remarkable when they work.
Same fundamental design approach, but needed another 25 years of improvement in battery and motor tech.
IIRC the first electric car was proposed in the 1920s or thereabouts.
Why not constructively contribute by explaining what could be different for the idea to work this time? Or if you hate innovation (i.e. retrying age old ideas slightly differently - hoping this time it will work), why don't you pick another industry?
I mean, at least Andreessen communicates directly, even if he's out of touch and tone deaf.
Anyway, we all have our gripes, and I think this article is poorly written, and the original article it links to is even worse. Doing no service to the fact that the people currently orbiting our little hovel of geekdom leave a lot to be desired. Or maybe you think this rant is poorly written and misses the mark...
Charisma is active - as in, the charismatic leader talks you into believing their bullshit. Reality distortion field is passive - as in, you hang out too much around the leader, or people hanging out around the leader, and you end up believing their bullshit.
Back in the day that was called 'being charming', not 'charismatic', and it was an offense: you're being intentionally dishonest and manipulative. Now it just means it's cute. Language changes...
Being charming to old school Germans means you’re a scam artist/unauthentic.
Most ‘greatest generation’ folks (if they’re still alive) had a similar feeling/overtone.
Because it’s true - someone being charming is making themselves likable to be liked (selling themselves), instead of letting their warts show. Because at a minimum they want your company. And it often works.
Someone being grumpy and unpleasant probably doesn’t give a shit, eh? And isn’t trying to sell you anything. In fact, chances are they’d be happier if you didn’t buy anything, and left them alone.
Which one is more likely to be a scam?
It’s what happens when scammers run amok (like now) and they are the ones that have to clean up the mess.
We’ll get another generation like that soon.
Eventually, people just get tired of doing it the same way.
A lot of "tech" is mature now. People whine "where's the innovation" in phones, for example. At this point, WTF do you want them to do? Where's the "innovation" in spreadsheets or word processors?
It IS kinda boring. And it's not going to get better when it's a bunch of recycled pablum shat out by "AI."
I blame greed. It was all the people coming into the field for the money and trying to entertain themselves at work because they don't like tech, they like feeling smart.
At the same time, I wouldn't write off machine learning models so quickly. Applied in tight focus, they're unlocking a bunch of capabilities, even if consumer-grade Dall-E, ChatGPT etc are mostly automated bullshit generators.
While it might be the case, there's definitely something else going on which I would describe as tech "globalisation" or "unification". The industry that looked like an archipelago of islands with their own ecosystems, philosophies and values increasingly looks like monoculture fields replicated zillion times (yc-style startups and "big tech co" being the two most popular breeds). Of course, the reality is more subtle than this - but the alternatives voices and perspectives are completely overpowered by the mainstream narratives - to the point of being barely detectable.
I'm prompted to think about this after watching the last Apple event livestream, and thinking to myself "these people all seem so /old/". Steve Jobs seemed ancient to me when he returned to Apple in 1997: he was 42.
This is not to say that techs, hackers, etc, have grown old -- but the distribution of ages has definitely widened, and its center may have shifted a little right too. That leaves plenty of room for much younger people to look at much older people and wonder at their strange, blowhard opinions. It also leads to older types feeling tired and bored with tech : and projecting that as the dominant tone to those of any age.