This article in different forms keeps making the rounds and it's just so tiring. Yeah, let's remember everything that was great about 25 years ago and forget everything that sucked. Juxtapose it with everything that sucks about today but omit everything that's great. Come on man.
If you think things suck now, just make it better! The world is your playground. Nobody makes you use YAML and Docker and VS Code or whatever your beef is. Eclipse is still around! There's still a data center around your corner! Walk over and hang a server in the rack, put your hardly-typechecked Java 1.4 code on there and off you go!
> The world is your playground. Nobody makes you use YAML and Docker and VS Code or whatever your beef is
Nobody, except your future employment prospects.
There's good reasons and bad reasons for a lot of technical options; "can I hire people to do it?" is a very good reason, but it does directly lead to CV-driven-development, where we all chase whatever tech stack the people writing the job adverts have decided is good.
The same people who capitalise "MAC" in "MAC & PC", the same people who conflate Java with JavaScript, the same people who want 10 years experience in things only released 3 years ago.
Right, and there's the rub, and what's behind all these changes - coordination. We containerized to coordinate our ability to use lots of different runtime environments. We typescript'd and python'd the web stack so that our frontend and our data friends could feel at home in the backend. We created ever-more-elaborate package repositories to make layering increasingly complex software projects simpler.
I think what people who write essays like this wish for is the smaller scale of things. Industrial steel production is objectively better than old-timey blacksmithing, but hammering out sets of cutlery certainly feels a lot more personal. Steelmaking wasn't better before all these fancy mechanisms and danger and pollutants and logistics, but when it was craft, it was more satisfying to work on.
Sure, you can do that for your hobby projects. But "at work" you generally have these decisions made for you. And these decisions have changed over time for the wrong reasons.
As an aside: if we say k8s, we should also say j8t.
> But "at work" you generally have these decisions made for you.
The idea that most employers make terrible decisions now, and amazing decisions back in the day, is plainly false. The author vividly recollects working at a decent Java shop. Even there I strongly doubt everything was amazing as they describe, but it sounds decent indeed. But plenty businesses at the time used C++, for no good reason other than inertia, usually in Windows-only Visual C++ 6-specific dialects. Their "build server" ran overnight, you'd check in your code in the late afternoon and get your compile errors back in the morning. The "source control" worked with company-wide file locks, and you'd get phoned your ass back to the office if you forgot to check in a file before leaving. Meanwhile, half the web was written in epic spaghetti plates of Perl. PHP was a joy to deploy, as it is now, but it was also a pain to debug.
If you care deeply about this stuff, find an employer who cares too. They existed back then and they exist now.
> Their "build server" ran overnight, you'd check in your code in the late afternoon and get your compile errors back in the morning.
This. Let's keep things in perspective when people complain about long Rust compile cycles. And even that's a whole lot better than filling in paper-based FORTRAN or COBOL coding forms to be punched into cards in the computing room and getting back line-printed program output (or a compiler error) the next week.
Rust's notorious compile times sticks out like a sore thumb partly because other system languages can run laps before your Rust build is done. And also because everyone and their grandma swears Rust is blazing fast.
Until you have to compile the program without prior build cache or start a build in a CI pipeline.
This is like economic growth: First bad, then upwards trajectory, then now in free-fall
You are describing it: Things in programing were bad, then suddenly all in the upside UNTIL it start to coming down.
Is not a refute of the problem. Is to pick a moment were both were bad, and like all the discussions about tech, MASSIVELY ignore that MASSIVE internet with MASSIVE money with MASSIVE backing is worse than before.
Is like people complaining that pistols on the wild west kill as do nuclear weapons, ignoring the massive difference in size and blast damage
In large C++ codebases of mediocre quality (the example I'm referring to is a manufacturer of large complex machines), yes.
People would compile their local unit locally, of course (a "unit" would be a bunch of files grouped together in some hopefully-logical way). But they wouldn't be 100% sure it compiled correctly when integrated with the larger codebase until the nightly build ran. So like if you didn't change the .h files you were pretty sure to be in the clear, but if you did, you had to be careful and worse-case-scenario do a 1-day-per-step edit-compile-test loop for a week or so. I'm not entirely sure how they managed to keep these compile failures from hurting other teams, but they didn't always (I think they had some sort of a layered build server setup, not too dissimilar from how GH Actions can do nightlies of a "what if this PR were merged with main now").
Visual Studio 6 itself was pretty OK actually. Like the UI was very limited (but therefore also fast enough), but compiling smallish projects went fine. In fact it was known to be a pretty fast compiler, I didn't mean to suggest that VC++6 implies overnight builds. They just coincided. In fact better-structured big-ish C++ projects (pimpl pattern anyone?) could probably recompile pretty quickly on the computers of the day.
It was definitely on the order of hours for large code bases - the Microsoft Excel team passed out punishment “suckers” for those who broke the build - causing 100+ people to not have a new working build to look at and test.
Linux kernel compiles in the 1990s were measured in hours, and that codebase was tiny compared to many. So, yep, builds were slow, slow enough to have an entire xkcd comic written about them.
Entire builds being slow isn't the main point though, it's iteration time from changes. I have a hard time believing people were working on a single compile a day and building an entire huge program on every iteration. That's the whole point of compilation units.
The reasons are always the same. 20% because some changes are actually improvements, and 80% cargo cultism where if you just build the right containers and chant the correct YAML incantations, you too will become a Google… followed by the phase where everybody just keeps doing these things because they organizationally don’t know any other way anymore, until the next big trendy thing, which does revert some of the issues of the previous trendy thing, but introduced a new set of already solved problems because this profession is incredibly myopic when it comes to history.
> Yeah, let's remember everything that was great about 25 years ago and forget everything that sucked. Juxtapose it with everything that sucks about today but omit everything that's great. Come on man.
That's fair. When I see bad code today, and try to explain to myself what's bad about it, I realize that people totally did the same things 25 years ago.
Nowadays there is just so much more code, and we stand on taller piles of "architecture" trying to scale higher heaps of expectations. The thing is, the effect of the bad stuff seems to compound more readily than the effect of the good stuff. And meeting the demand for more code involves broadening the base of people doing the coding.
> If you think things suck now, just make it better! The world is your playground.
For PAPER I'm targeting Python 3.6+ (where they added `pathlib.Path` and f-strings, and upgraded the SSL version) with the intent to support it indefinitely (which involves forking certain dependencies).
I think it is a great exercise of self awareness to take a step back and see how things are done now.
I started my first prpgramming job in 2003. Some things where better, others were worse. But the only way we can improve the "craft" of software development is by having introspection. It's kindnofnwhat happen during the "software crisis" of the 80s, and why "waterfal" was rrplaced by "iterative" software development.
Now, with such an impactful change like AI aided coding, it is a great opportunity to see if we can evolve anything in the building process.
Yes, good of you to ask. But don’t you worry your little head, now! You aren’t the first patient that developed a thin skin from their own medicine, and you won’t be the last.
Yea, my immediate reaction was, “Okay. Stop doing all the stupid stuff.” If you want to program like it’s 1999, go for it. I generally don’t use AI, for instance. I just haven’t found it to be a net-positive yet.
Yes, sometimes it's that, but what I've observed in the field is self-inflicted by programmers. It's the impostor syndrome. They don't know, but they don't want to show that they don't know. They look around for clues of what to choose. Monkey see, monkey do. And then, like monkeys, they bash their keyboard until it seems to work.
And in fact, professionally, I still live in the good old days. I code in Java 21, I minimize dependencies, and I use an IDE that can do the heavy lifting when I want to refactor something…which is often. I produce a .jar that gets installed with a loader script rather than in the cloud. And it all works, and it’s *stable*.
Just yesterday a friend and I was talking about writing a clone of a popular website, using the technologies of yesteryear. There's absolutely no reason why we wouldn't be able to make a credible competitor using mod_perl and db2.
From a technological view, we're a point where your development stack doesn't matter all that much.
>Nobody makes you use YAML and Docker and VS Code or whatever your beef is.
Not VS Code, but maybe YAML and Docker if your company is trying to align what tools it uses. C# places might still force you to use Visual Studio proper. Everyone says use the right tool for the job, but for bog standard CRUD web development, we do have a shitload of tools that work and there's multiple ways to get to a fast, working product.
I still chuckle that my laptop is 3 times as fast as the cloud thing that serves our CRUD app and we pay many more times for it, but also knowing full well I do not ever want to be RDP'ing into a production box again and pouring through IIS or Windows logs.
What I definitely do see is a degradation in making choices about when to adopt a more complicated technology because of the incentives of the hiring market.
People have loudly beaten the drum to keep your skills up to date and so people choose stuff that's popular because it benefits them personally, even when the product doesn't need it. This in turn leads companies to only select people who know that stack, and the more that companies do that, the more people make technical choices to get them the best job that they can handle.
We absolutely, very much 100% see that happening now with LLM AI if you ever needed a bigger piece of proof. Pretty much everything that is happening now has just been a louder example of every bad practice since the run up to the dotcom bust.
Because of that, I'd frankly never suggest running on-prem or building a local-only app unless there was a much bigger reason (legal, security, whatever) especially if the other products in the company have chosen the cloud.
Why? Because convincing the next job that that would have been the right choice is too hard.
Edit: and to someone else's point, I made the choice to be in the Microsoft/Azure/Windows hell hole but digging myself out and moving to something else is practically working a second full-time job and holding 2 ecosystems in my head at once
On the one hand: yes, this dev has clearly chosen a career/language specialization that puts him knee-deep in the absolute worst tooling imaginable.. I cannot fathom a workflow this fucking miserable and if this was my day to day, I would be far, far more depressed than I already am.
AND, the fact that so very very much of our industry does run, perhaps not all of, but a significant amount of a workflow not awfully different from this is IMO, an indictment of our trade. To invoke the immortal sentiment of the hockey coach from Letterkenny, this shit is FUCKING embarrassing.
So much major software that ships in a web browser because writing for Windows, Mac and Linux is just too hard you guys, it's simply too much for a sweet little bean like Microsoft ($3.62 trillion) to manage as they burn billions on AI garbage, is FUCKING embarrassing.
Half the apps on my phone are written this way which is why they can barely manage 30hz on their animations, die entirely when S3 goes down, and when they are working, make my phone hot. To run an app that lets me control my thermostat from my desk. That's FUCKING embarrassing.
And my desktop is only saved by virtue of being magnitudes more powerful than my original one back in the 90's, yet it only seems a scant more capable. In the early 00's I was sitting on Empire Earth and chatting with people over TeamSpeak. My computer can still do this, and with the added benefit of Discord can stream my game so my friends can all watch each other, and that's cool, apart from I lose about 10 fps just by virtue of having Discord open, and when I'm traveling? Oh god forget it, Discord flounders to death on hotel wifi despite it being perfectly cromulent DSL speeds. Not BLAZING, surely, but TeamSpeak handled VOIP over an actual DSL connection, with DSL latency, in the 00's. That's FUCKING embarrassing.
All our software now updates automatically by default, and it's notable when that's a GOOD thing. Usually what it actually means is the layout of known features changes for seemingly arbitrary reasons. Other times more dark patterns are injected. And Discord, not to pick on them, but they're the absolute fucking worst for this. I swear they push an "update" every time one of their devs sneezes, I usually have to install 18 such updates on each launch, and I run it very regularly! And for all that churn, I couldn't tell you one goddamn thing they actually added recently. FUCKING embarrassing.
And people will say "oh they could be better," "we know we can do it better," "these aren't the best companies or apps" okay but they are BIG ones. If the mean average car in America got awful fuel economy, needed constant service, was ill-designed for it's purpose and cost insane amounts of money...
Oh, that happened too. I think I just made my metaphor more embarrassing for another industry.
I wish people were not so inclined to reply with "Ad Hominem Ridicule" one liners. I like a good joke, but such replies lack a certain level of content that addresses the point and feel "low effort".
I do agree that comparing the past with the present if fraught with complicated nuances, and people do tend to see the past with rose tinted glasses. But, I read Talwar's blog post more as a personal reflection on their experiences they are facing and not some kind of scientific treatise on what went wrong.
fair criticism; didn’t mean this as an ad hominem but rather a summarization of (as the comment I replied to points out) this genre of article that keeps coming up (and not just for programming); it’s exhausting mindset to see repeatedly and breaking it down into the core argument (“I liked things better when I was younger”) does have some value IMO
if this were titled “Java/JavaScript peaked” or “my reflections on XYZ” and written like that, I wouldn’t have given it a second thought. but claiming programming peaked 15 years ago leads me to not feel bad about my summarization
You'll get old too one day and it will look a whole lot different watching the younguns stumble through completely avoidable mistakes and forget the long lessons of your life that weren't properly taught or were just ignored.
We have records from many periods in history of old men crowing about how society is collapsing because of the weak new generations. Thing is, maybe they were always right, and the new generations just had to grow up and take responsibility? And then again, maybe sometimes they were little too right and society did in fact collapse, but locally.
“Hard times create strong men. Strong men create good times. Good times create weak men. And, weak men create hard times.”
Agreed! If anything, I think I'm tired of the "everyone says this when they get old!" hot take. Sometimes things really do get visibly worse and the intergenerational complaining about it is due to it really happening.
I bring this example up every time, but I'm a baseball fan. And seemingly every generation of fan has said there's more people striking out than there used to be. Is it because there part of getting old as a baseball fan? No! It's really happening. Strikeouts have quite literally been going up from one decade to the next for basically a century.
So sometimes it's because the thing is really happening. Environmental ecosystem collapse? Real. People having shorter attention spans every next generation? Real! Politics getting worse? Well, maybe the 1860s were worse, but the downward trajectory over the last 50 years seems pretty real. Inefficiency of increasingly automagic programming paradigms? Real!
Sometimes things are true even if old people are saying them.
> Hard times create strong men. Strong men create good times. Good times create weak men. And, weak men create hard times.
Actually it's the opposite.
Strong men create hard times by trying to show to each other how strong they are. Hard times create weak men because during hard times strong men kill each other, thus mostly weak men remain. Weak men create good times because instead of trying to show their strength they just build stuff so that the world is easier for them. In good times people breed and the population returns to the mean with just enough strong men to start the cycle again.
WWII was the last time strong men created hard times. We are overdue for another round and it shows.
That's because the thesis it's expounding on isn't "old people don't like change", but rather "experienced people often see their juniors unknowingly making avoidable mistakes".
An interesting Reddit r/AskHistorians thread on the question """Does the aphorism "Hard times create strong men. Strong men create good times. Good times create weak men. Weak men create hard times", accurately reflect the evolution of civilizations through history and across different cultures?"""
copying only the conclusion for a tl;dr: "The only way that the aphorism explains history is by reinforcing confirmation bias - by seeming to confirm what we already believe about the state of the world and the causes behind it. Only those worried about a perceived crisis in masculinity are likely to care about the notion of "weak men" and what trouble they might cause. Only those who wish to see themselves or specific others as "strong men" are likely to believe that the mere existence of such men will bring about a better world. This has nothing to do with history and everything with stereotypes, prejudice and bias. It started as a baseless morality tale, and that is what it still is."
That reply completely misunderstands the quote. It is about how people with integrity, who are willing and able to put out effort and endure difficulties to build a better future, do usually manage to make things better than those who do not.
It’s essentially a truism warning people that problems you ignore don’t fix themselves, and has nothing to do with gender or gender stereotypes, that’s a linguistic misunderstanding. In this context, “men” is gender neutral and means “people.” In old english, the word “men” is explicitly gender neutral and there was a different word, “wēr” for male people, which is still used in some contexts, e.g. “werewolf” means wolf man.
I’m not sure what you mean. I don’t see a bias here, the point is plainly stated: the notion of weak men is dubious. You might not agree, but then engage with something substantial.
If you don’t see a bias in political communication (and that is what all of this is), then chances are very high you share the bias.
Abundance allows comfort, comfort enables complacency, and complacency can weaken the social fabric by encouraging short-term gratification over long-term maintenance.
People worry about masculinity because masculinity requires structured, pro-social outlets to not be toxic. A aimless or misdirected male population is an incredibly corrosive and/or dangerous thing. It can rot out a society from within, or make a society susceptible to subversion from without.
Societies use rhetoric about strength because if a society does not maintain systems that cultivate competence, responsibility, purpose, and pro-social ambition (especially in its most impulsive members), it becomes brittle.
You're doing the same assuming "good times = comfort = weakness" as a thing you already think, which is what the long reply I linked is debunking. What you said implies an opposite, something like: scarcity and famine strengthens the social fabric by encouraging long-term thinking over short-term maintenance. Actually it doesn't, scarcity leads to dog-eat-dog short-term survival tactics anything from stealing from neighbours, eating next year's seeds, up to eating the farm dog or selling the farm machinery or cannibalism, and leads to squalor, disease, and fire risks because nobody has time or energy or resources to spare on anything but the most urgent survival.
Abundance, by contrast, allows seed saving, food storage for winter, spare resources to use on washing and hygiene and medicine and recovering from illness, rule of law and enforcement, time away from subsistence farming and scavenging for food to enable things like developing metalworking skills, inventing, practicing archery, spending time on other society-building rituals like building churches and going to church.
> "A aimless or misdirected male population is an incredibly corrosive and/or dangerous thing"
If they are "incredibly dangerous" does that not make them "strong"? These are supposed to be the "weak men" created by "good times", aren't they? Are they strong men created by weak times who are themselves creating weak times by rotting society? Or are they strong because they are men, independent of the times? Does this fit into the saying at all?
> scarcity and famine strengthens the social fabric by encouraging long-term thinking over short-term maintenance
Famine is not isomorphic to “hard times”, and particularly not what the aphorism is referring to: self-created hard times, wherein a society’s ability to self-sustain and compete externally is needlessly curtailed.
> If they are "incredibly dangerous" does that not make them "strong"?
I said corrosive and/or dangerous, and weakness can be both corrosive and dangerous.
What you linked to was not a debunking. It was a political viewpoint. Reasonable arguments exist for a different one.
> "particularly not what the aphorism is referring to"
The aphorism does not say what it is referring to, you are making this up so it says what you want it to say (which is bias). This wouldn't be a problem if you used that to make a point and argue your point, but it is a problem when you just go "I imagine that it means something else, so you're wrong". Self-created hard times such as ... what? If laziness in farming doesn't create famine in winter... what hard times are more relevant than that for a society in 0 AD? "Needlessly curtailed" by who or what effect?
> "I said corrosive and/or dangerous, and weakness can be both corrosive and dangerous."
Can it. Is there any way to measure this weakness? Is it actually a thing?
> The aphorism does not say what it is referring to
In which case it makes no falsifiable claims. If “hard times,” “weak men,” and “strong men” have no stable meaning, the cycle can’t explain anything and can be retrofitted to any narrative. There would be nothing to argue for or against.
That isn’t the case. “Hard times” in this context means the cumulative internal consequences of institutional decay, complacency, and short-termism. Not natural disasters. That’s why your famine example is irrelevant.
> Is there any way to measure this weakness? Is it actually a thing?
Sociological concepts are evaluated by their broad effects, not by a single scalar value. Declining institutional competence, eroded norms, reduced accountability, and loss of collective purpose are both observable and historically recurrent.
That’s your opinion, but like I said it’s not valid to imply that it is the normal view and those not agreeing are biased. Instead of trying to hear understand and challenge what historians have to say you flee intellectually, which is ironic given your take on strong men.
I’m not historian but for example I could challenge the idea that a rhetoric about strength and keeping a masculine ideal for the young male population was non existent in European feodality where only nobility had the privilege of fighting, and 90% of the population were farmers. Or that 2000 years ago Jesus already challenged the idea that men needed to be strong in the traditional sense, and that real courage was loving and forgiving among others. I could go on with fashion and clothes but maybe just look at a West European king painting to reevaluate what masculinity is supposed to look like traditionally.
My understanding is that your rhetoric appears only recently (and is therefore not traditional) coinciding with nationalism rise and the need for bodies to throw in the total war (another modern invention) meat grinder.
You can disagree, and I’m open to hearing your counter arguments, because I’m not dismissing you as biased.
> Instead of trying to hear understand and challenge what historians have to say
One self-described historian. On a Reddit post. Let’s not pretend this is the unified or authoritative voice of the discipline.
> I could go on with fashion and clothes but maybe just look at a West European king painting to reevaluate what masculinity is supposed to look like traditionally.
You’re conflating aesthetic masculinity with functional masculinity, and that’s a category error. The aphorism isn’t about how men dressed in the 17th century or how they signaled status — it’s about what kind of men can sustain a civilization.
In this context, “strong men” refers to individuals who demonstrate the discipline, competence, long-term responsibility, and willingness to bear risk that are required to build, maintain, and defend the institutions that keep a society stable — especially when conditions are difficult. It’s a sociological concept, not an aesthetic one, and it has nothing to do with your personal distaste (or favor) for particular cultural aesthetic expressions of masculinity.
Everything you've said about comfort and complacency is equally if not more true of scarcity though. Scarcity leads directly to short-term thinking because there's no future to plan for or maintain. Erosion of social bonds happens as desperation increases and people turn to grifting and taking advantage of each other. The original quote is a little too tidy, an oversimplification that fails to grasp a complex reality and seems to have its own agenda/bias. Which you presumably agree with or you would have caught it. The truth is that there are varying levels of easy and hard times, and either one can "create" either kind of man. (And I'm ignoring masculinity as an issue; everybody knows whether they're a man or not.)
Or I can reframe it one more way: If good times create weak men, then all the rich people currently running things corruptly and soaking up whatever 90% of the wealth, are weak, and all the discipline and virtue in society are among the rest of us. Cultivate competence, responsibility, purpose and pro-social ambition in the super-rich and you might have something there.
"Strongly" and "just like everyone else" are contradictory, no? Assuming "strongly" is somehow relative. If you have an absolute measuring scale for bias-bringing-to-bear, I would love to hear about it.
Just because it says "men" doesn't mean it's about masculinity. Rather, my reading of "strong men" is closer to "people with a strong work ethic, integrity, and zero tolerance for corrupt grifters," and my reading of "weak men" is "people with zero work ethic who are in fact, corrupt grifters."
they were not right and I promise when I’m old, I will not have this attitude. it’s one of my least favorite types of people; and that’s precisely my point, old men have been saying society is collapsing since ancient times, yet here we are, with things better than ever
Fwiw I'm with you here. It's perfectly possible to stay excited about new stuff. Just.. take it for a spin! Find the good parts even when they re-make mistakes from the last time someone tried sth like this 2 decades ago.
Like, when React was new I had total Delphi deja vu. And then they went about reinventing MVC (not the Rails MVC, real MVC) and calling it "unidirectional data flow" instead of just MVC, and feeling all smart about themselves and doing proud conference talks, and I was like "this is just MVC but with worse naming".
But React also made it so that every component is designed to be reusable. Like, in Delphi you had a "Form" on which you dropped "Controls" and then you could also create your own controls if you were really advanced. But most people didn't feel like they were advanced enough, so code reuse was a mess. React made it so that every control (cough component) is reusable, because using components is the same as making components. That's a good idea! Purely functional UI, that's also a good idea! Then they threw OO out instead of fixing it, that was a terrible idea, but bottom line it's still great! Plus, Delphi didn't have to deal with the horrible mess that is HTML and CSS so it had it easy.
But yeah lots of people my age saw the same, saw how it was just Delphi all over again but with different mistakes, and focused on the mistakes. It really is purely an attitude thing.
I'm having a lot of fun with signals and SolidJS and observables now and it baffles me that something so elegant and fast took this long to be discovered (or more like, to get ergonomic and mainstream enough).
> I promise when I’m old, I will not have this attitude.
To my ears this is a hilariously naive statement. It sounds to me to be roughly the equivalent or a 7-year old saying "Adults have boring jobs where they sit at a desk all day. I hate it. I promise when I'm old I'm gonna be an Astronaut or play Major League Baseball."
It's not that they don't mean it, it's that one should make promises about a situation they can't yet understand. While some of those kids probably did end up being astronauts or baseball players 99%+ who made that promise didn't. It turns out that being an adult gives them perspective that helps them realize the reasons they want a desk job even if they don't like it, or for many they actually enjoy their desk job (ex they like to program).
So the same if a million young people all thought similarly, and then magically changed their view when they got there dont promises your going to be the one who will break the streak.
You might turn out to be an astronaut, but many people listening, based on good previous evidence will rightly assume you won't.
Read what you just wrote. You are just declaring a belief, not making an actual point.
Do you expect to learn? Get wiser?
If you do, you will eventually develop wisdom that younger people don’t have yet - or may never get. Younger people find new ways to do many things better, but regress in other ways. Lacking your (and your generation’s common) experiences.
Which is why the only old people who can’t see any real regression are … well I have yet to meet that kind of old person, other than those unfortunate to have dementia.
Also, every new better (or perceived better) way to do things has to reinvent many obvious things all over again. Things many won’t realize were already solved by previous practices. Which takes time.
So meanwhile, regressions.
And there is no assurance that new ways will really be better, after all regressions are addressed. Because it is impossible to see all the implications of complex changes.
Anyone who isn’t aware that the amount of today’s glue code, rewriting of common algorithms for slightly different contexts, the mush mash of different tools, platforms, and dependencies, and all their individual quirks, was a non-optimal outcome…
But the current pain points will drive a new way. And so it goes.
Progress is not smooth or monotonic.
It is a compliment to discount that you won’t also notice. Not a critique.
??? my point is someone who doesn’t know the first thing about me called me naive and made bold claims about my future that I’m certain are wrong; time will tell but there’s nothing of substance to discuss from their comment, hence my reply
you’ve also just said a ton of stuff I don’t disagree with, but I’m not sure what discussion you’re trying to have here
I do regret the time spent reading this article and participating in this comment section; that was naive of me!
> Anyone who learns anything looks back on a naive version of themselves. I remember thinking a lot like you, too.
I'm so glad that for the most part in my early internet days (early 2000s), I was pseudonymous. I tended to have very strong opinions about stuff I had barely just learned and didn't have experience to get nuances. My political opinions have completely flipped and I look back on my young firebrand days and unfortunately see lots of young people repeat the same vapid shit that I believed because I was ignorant but convinced it all followed from simplistic crap ideas I was raised with.
"...it’s one of my least favorite types of people; and that’s precisely my point, old men have been saying society is collapsing since ancient times, yet here we are, with things better than ever"
Which is a pretty strong opinion. Also, pretty much all societies that ever existed have collapsed. When that happens, life generally sucks and lots of people die. I'm not just talking about ancient Rome or Greece, or Easter Island, or the fall of dozens of different empires, or more recently South Sudan or Haiti.
Other people in thread called you naive. I won't insult you like that but just given the statements here, there's a whole lot of familiar-sounding overconfidence that reminds of things I'd have said in my 20s.
If you don't think they were at least sometimes right, to what do you instead attribute the various cases of socio-economic collapse documented throughout history?
I'm not sure that's directly analogous, though. We're talking about people looking at specific cultural trends and making reasoned arguments about specific causes and effects, not just saying "X will happen". Specific models and assumptions about how human societies work are often validated by historical example, and don't just predict end states, but sequences of events that extend over longer terms.
When people say they see history repeating itself, it's worth hearing them out.
> I’m saying if every generation has old men screaming “society is collapsing”, they aren’t right, even when they’re locally “right”
But every generation doesn't have old men screaming "society is collapsing" at the same rate. There's always a baseline of people with a "get off my grass" mentality, but if you factor that out, occurrence of people actually pointing out that the world is on a dangerous path isn't uniform from one era to the next. Very few people, if any, were seriously making such an argument 30 years ago.
People who are genuinely making reasoned arguments, and not just complaining about things being outside their comfort zone, should absolutely be taken seriously.
> claiming programming peaked 15 years ago is absurd
Well, what are you measuring? It certainly peaked in some dimensions 15 years ago. Whether you personally see those dimensions as important is of course a subjective question.
You know what made javascript so common, accessible, and thus later universal?
Putting things on a screen was (is) stupidly simple.
That's the whole thing. It's not the types or npm or whatever. It's that you could start with C/Python/Java and spend your first 6 months as a coder printing and asking values on a dark terminal (which is something a newbie might not even have interacted with before) or you could go the html/css/javascript route and have animations moving in your screen you can show to your friends on day one.
Everything flows from that human experience. UIs are Electron because creating UIs for a browser is an extremely more universal, easy and creative-friendly experience than creating UIs for native apps, particuarly if JS is your native language for the previously stated reason.
The industry failed to adapt to the fact that the terminal wasn't any longer the reality of computer users, and the web kinda filled that niche by default.
Also, React was an answer to the advent of mobile phones, tablets, smart tvs, and basically all the explosion of not-a-desktop computer form factors. You could no longer assume your html was a proper format for everything. So you need an common API to be consumed by a mobile app, a tv app, a tablet app... react was the way to make the web another of the N apps that use the api, and not get special treatment. The idea made sense in context, back then.
> Putting things on a screen was (is) stupidly simple.
This is why HTML is still a great language for building UIs and that's why Visual Basic had a huge success in the early 90s: drag UI components on a panel, write the callbacks for clicks, save and distribute the exe. Almost anybody could do it.
React and its siblings are much more complicated than that.
It's my belief that we peaked on January 1, 2000. We had successfully released most of the stress baked into the worlds infrastructure with the sudden phase change of "backward compatibility" caused by the IBM 360 series introduction decades earlier.
We had Windows 2000, a server operating system that worked well as a desktop. Both Visual Basic 6 (aka VB6) and Borland Delphi allowed drag and drop GUI application development. Microsoft Office Professional supported most of the features of VB6 while controlling Spreadsheets, Databases, and other documents.
Anyone skilled in a domain other than computing could spend time and put together a reasonably decent application to help with their jobs, and it just worked. You could then call in a professional to clean up edges and make it faster/more reliable if it needed to be scaled.
The documentation was available for pretty much everything, in print, and on screen, with working examples for almost every single function.
It was before the whole .NET distraction, and forcing web pages into everything.
It definitely wasn't perfect... we didn't have widespread version control. No Mercurial or GIT. Mostly, it was numbered PKzip files stored on floppy disks.
We still don't have reliable secure operating systems, I think we've missed that window. Genode was my hope, but it remains a collection of ingredients instead of a daily driver.
It’s so very ironic that your comment appears on this particular post. We had a much better version of this with interface builder on NeXT in the late 1980s (and later Mac OS X). Similar tooling existed for DOS and Windows.
You literally laid out your UI in a WYSIWYG, drag and dropped connections to your code, and had something working on day one.
It was even easier than the web, because what you were laying out were full components with code and UI and behavior. The web still hasn’t caught up with that fully.
When I see comments like these, I better understand why old timers shake their fist at the youngsters reinventing the wheel badly because they don’t understand what came before.
>We had a much better version of this with interface builder on NeXT in the late 1980s (and later Mac OS X)
I don’t disagree, that just wasn’t available as a starting to program option when my generation started learning around 2005. If it still existed, it was way too niche for me to know about as a beginner.
And I don’t include myself in the generation that started programming through JS, I went the console route a bit earlier. But I have seen friends enter programming later on and it’s clear why that is the main choice.
Interface Builder was still the standard way to build Mac apps in 2006, and with some improvements, has remained a standard way to build Mac and iOS apps to this day (but now we also have SwiftUI).
Fair, but how common were Macs in 2006 for newcomers?
At least in my corner of the world they were practically non existing. The first time I saw macOS at all was in 2012, and it was on my pc after managing to turn it into a hackintosh with help from some random Eastern European guy from a message board.
It always felt like a huge miss to me that Microsoft didn’t bring Access to the web and/or mobile apps. For all its flaws, it was a simple drag-and-drop editor that almost anyone could use to build simple apps that could power decent-sized businesses.
It's horrifying to see someone who started working 10 years after me talking about "when I was young" :-D
Programming was more exciting when you had amazing things to imagine having - like a 256 colour screen or BASIC that ran as fast as machine code (ACORN ARCHIMEDES) or the incredible thought of having a computer powerful enough to play a video and even having enough storage to hold a whole video!
2400bps! Checking email once a day
Everything came true. My screen has 16million colours and I don't notice. I have 12 cores and 64GB of memory and fibre optic internet. The extremely exciting future arrived. That mind-expanding byte article I read about Object Oriented programming came true enough for us to see that it wasn't the answer to everything.
There are 2 problems now - nothing one does is unique. You can't make a difference because someone else already has done whatever you can think of doing ....and of course AI which is fun to use but threatens to make us even more useless.
I just cannot really get my sense of excitement back - which may just be because I'm old and burned out.
In an ironic twist of life, this is almost what I'm back doing right now. I turned off notifications and pull messages years ago because of all the messages I'm getting for a dozen different systems. I check mail at most a few times per day and that's it. I wouldn't be able to work if I'd have to actively keep an eye on them. I can get away with it because everybody is using Slack for work or WhatsApp for personal life, so there is no urgency to check mail. I'm on Slack too, so I see if I have messages there but WhatsApp is silenced and I allow no notification of any sort on the lock screen of my phone.
It's not just that you're old and burned out. There is a declining marginal value of improvements.
Take sound, for example. Going from "no sound" to "sound" was huge. Going from just beeps to IBM PC sound was a real step. CD-quality was a real step. Going from CD-quality to 64-bit samples at a 1 MHz sample rate is a yawn. Nobody cares. The improvement on CD quality isn't enough to be interesting.
I have high enough bandwidth. Enough screen resolution. Enough RAM, enough CPU speed, good enough languages freely available, enough data.
The problem is, everything that was an easy win with all that has already been done. All that's left is things that aren't all that exciting to do.
(I don't think this is permanent. Something will come along eventually - a new paradigm, a new language, a new kind of data, something - that will open a bunch of doors, and then everything will be interesting again.)
I'm disappointed that you said "2400bps" instead of "2400 baud". :/
It's always surprising to me when I see people being nostalgic for the old days. Yes, things seemed simpler, but it was because there was less you could do.
I'll always fondly remember my attempt to get on GeoLink with a 300 baud modem, and then my parents realizing that the long distance calls made it far, far too expensive to use, and returning it. Sure, I was disappointed at the time, but it wasn't too much later that 56k modems existed and we had a local unlimited internet provider. And now it's a fun story.
But I was actually just as frustrated at the time as I am now, but for different reasons. Change exists, and that's good.
I agree that it feels harder to make your mark today. But I don't think it's actually harder. There's plenty of fun things that people would love to see people do. Just yesterday, I found out about the Strudel musical programming language and watched an amazing video of someone making Trance with it. And those kind of discoveries happen constantly now, where they were pretty seldom back 30 years ago.
We're at the point that anyone can make a game, app, webpage, etc if they put enough effort into it. The tools are so easy and the tutorials are so plentiful and free that it's really just about effort, instead of being blocked from it.
I've been saying "we live in the future" about once a month for years now. It's amazing what we have today.
> Yes, things seemed simpler, but it was because there was less you could do.
And because computing was less mature and a younger field overall. If computers remained stagnant for 500 years, fixed as they were in 1980, I bet that programming would become increasingly more complex, just to enable doing do more with less
For me, starting with 1978 hand soldered NASCOM-1 kit (2MHz Z80, 1KB RAM for user, 1KB for display) to my current hand built 10-year old tower with a core i7-5930K processor.
2MHz 8-bit -> 3.5GHz 64-bit multi-core CPU
1KB -> 32GB RAM (a factor of 32 million times more memory !!)
offline -> 9600 baud BBS -> 1Gbps fiber + internet
From hand assembling on paper (or just entering memorized hex opcodes directly into memory) to vibe coding "build me an app to do xxx", or talking to Gemini on my iPhone (would have looked like an alien artifact in 1978) asking it pretty much anything.
What will the next 50 years bring? Will it be as amazing as NASCOM-1 -> iPhone + Gemini? I used to think so, and certainly in 50 years I'd expect full-blown human-level AGI to be here, but will it feel that much different ?
> I'm disappointed that you said "2400bps" instead of "2400 baud". :/
haha :-) It was of course 2400 baud and we were using FidoNET which was very very exciting at that time in Zimbabwe. We'd spend 10 minutes trying to get a dial tone sometimes but it was magic when you connected and saw something was coming in. International telephone calls were so expensive that we talked to my brothers overseas once or twice a month at best. With email we could chat every day if we wanted.
The limitation then was information - no internet, no manuals no documentation. I wrote a text editor and did my best to make it fast with clever schemes but it always flickered. Many years later a pal at university in South Africa casually mentioned that graphics memory was slow so it was actually best to write to memory and then REP MOVSB that to the graphics memory. I cursed out loud at this and asked him how he knew that?! Well, he lived in a more modern country and could buy the right books. Nowadays you really can be a linux kernel programmer in the Congo if you want to.
Thank you for sharing this. I started as a youngling on a 300 baud modem. 1200 baud upgrade modems had a zeitgeist of being just for piracy — who else would need so much bandwidth said those who charged by the minute. Information wasn’t flowing freely and resource-dense countries had advantages to spread it around themselves. Before HTTP and WWW there wasn’t much information architecture existent either.
But what makes me happy to hear is that - on the other side of the planet - random kids were also plugging in a modem, to get connected with each other and press at the edge of the future.
> I started my first real, full-time job in 2010. We wrote Java...
I started my first real, full-time job in 1992. Back here we write C, or maybe C++ if we're feeling cutting-edge. The Sparc 10 can get a bit slow when we're all on it, but I have a shelf full of O'Reilly X Windows books to look through if I can't figure something out. My mate in London sent me a QIC tape with something called "gcc" on it: sounds exciting, but before I can install it I have to find a spare day to update SunOS first.
This 2010 programming setup seems pretty amazing tbh... can't wait to get me some of that. Nice languages and tooling, no more having to edit makefiles by hand in emacs or laboriously debug in gdb. Bet they don't even use sourcesafe anymore.
I reckon by 2025 they'll have god-like stuff: fast, reliable hardware with more memory and storage than you can eat; powerful development and collaboration tools; lots of ways to find answers without having to ask that guy over in the other building. And a lot of it will be basically free! I wonder how they'll feel about all that awesome dev power, and whether they'll still use X terminals.
Programming has evolved several times since the early 90s (when I got in this business) and I had the impression it had already evolved several times by the 90s (especially talking with old mainframe or COBOL programmers).
It's evolving again now, and that process is painful. Nobody knows what the future holds.
> Funnily enough, everything ran at about the same speed as it does now.
Actually, where I was sitting on a decent PC with broadband Internet at the time, everything was much, much faster. I remember seeing a video on here where someone actually booted up a computer from the 2000's and showed how snappy everything was, including Visual Studio, but when I search YouTube for it, it ignores most of my keywords and returns a bunch of "how to speed up your computer" spam. And I can't find it in my bookmarks. Oh well.
Wow that was a great read, thank you. It's funny that it is already starting to break due to all of the links and ad tracking, which is another kind of rot.
Use Linux/KDE. None of the gains from the switch to SSDs have been lost. Everything is instant even on an n100. You only need something more powerful for compilation, gaming, or heavy multimedia (like the 200 Mbps 4k60 video my camera produces, which isn't accelerated by most processors because it's using 4:2:2 chroma subsampling).
Xfce or LXQt are also great alternatives, blazing fast even on 15 year-old hardware. Old hardware can be slow for basic web browsing and multimedia (e.g. watching videos with modern codecs) but other low-level uses are absolutely fine.
> "I remember seeing a video on here where someone actually booted up a computer from the 2000's and showed how snappy everything was, including Visual Studio"
Was it this one? Casey Muratori ranting about Visual Studio Debugger slowness, and he shows a video of Visual Studio opening and debugging faster on a single core Pentium 4 from 20 years earlier - https://youtu.be/GC-0tCy4P1U?t=2160
Or this one? Roger Clark developing Notepad in C++ on Windows 2000 and commenting how fast Visual Studio opens: https://youtu.be/Z2b-a4r7hro?t=491
Yeah, that's the one! And hmm, it's interesting that there's more than one video out there going "look how fast old computers were from a user standpoint". They've really been boiling the frog when it comes to terrible UX over the past 20 years.
Given the refinements to the hardware, the modern scale of manufacturing and accessible market, and the sheer amount of engineering manpower a tech company can bring to bear nowadays, you'd think standards would have risen into the stratosphere, but instead the tech consumer is cowed into accepting slow, buggy, abusive, invasive trash.
These days to get a snappy experience, one has to aggressively block everything and only selectively unblock the bare minimum, so that one doesn't get tons of bloat thrown in the direction of one's browser. Oh and forget about running JavaScript, because it _will_ be abused by websites. And then sites have the audacity to claim one is a bot.
Many websites are so shitty, they don't even manage to display static text, without one downloading tons of their JS BS.
I can't recall desktop application times, but I remember using the web in the 00s. Websites took a noticeable blip to load. Pictures took seconds to minutes to load, top to bottom, on my connection. Runescape took an hour to update on dial up.
I do remember applications like Microsoft word's UI constantly freezing though.
You can view shorts on desktop. In a browser on desktop, when you see one on your subscriptions tab (or the front page if you still use that), you can right-click and open in new tab. You can replace "shorts/" with "watch?v=" in the URL and load the same video in the regular UI. You don't have to scroll down.
I've been coding since 40 years old and professioannly since about 30. And let's set this straight: it is much (much, like really much) better nowadays.
We have super powerful editors, powerful languages, a gazillion of libraries ready for download.
I use to write video games and it took months (yeah, months of hobby-time) to put a sprite on a screen.
And for Java, yeah, things have improved so much too: the language of today is better, the tooling is better, the whole security is more complex but better, the JVM keeps rocking...
> I use to write video games and it took months (yeah, months of hobby-time) to put a sprite on a screen.
I'm not sure how that happened - in DOS you could copy things to the framebuffer. There were libraries like Allegro which came with a million features including sound/UI/sprite rendering/animation/effects etc. out of the box.
But anyways copying a sprite to a screen is not hard even if you don't use a single piece of foreign code - you can read in a BMP file and just copy it row-by-row to the screen.
I'm talking about things that were long before DOS even existed.
At that time you didn't even have the tools to cut sprites from image in the first place. That's why it took a lot of time (and I was 12 years old and my dad was pretty far away from an engineer, that didn't help).
I'm 53, started at 10. At that time, being able to edit a line of code without re-typing it completely was "cool" :-) Then, on apple 2, we had GPLE (global program line editor) then Assembler toolkit which had an editor. Then I moved to PC. First I used GWBasic (it had an editor) then Turbo Pascal, then multi-edit, then emacs, then Visual Studio, then Eclipse, then Word (became a manager :-)), then back to emacs and VSCode (coding again!) and a bit of Kate.
The author is writing like Java was outlawed or something. There are tons of shitty enterprise Java jobs out there for those who want them. Personally, I worked one of those jobs a decade ago, and the article's description of the "golden age" didn't bring back good memories.
It's easy enough to avoid the NPM circus as well. Just don't put JavaScript on your resume and don't get anywhere near frontend development.
Things don't always get worse. Sometimes they get better.
TypeScript recently invited people to try their new compiler which is 7-10x faster. [1]
VS Code is popular, but personally I write TypeScript in Vim, which is definitely faster and less resource-intensive than Eclipse. But thanks to VS Code's invention of the Language Server Protocol and its subsequent adoption in many editors, I can get 'compile the code as you type' functionality. [2]
And then there's runtime speed. Java used to have legendarily slow startup times, and they're still an issue today. JavaScript's modern runtimes are optimized to start fast. On the other hand, Java still holds the crown for throughput, so it's a mixed bag. But if you want even better throughput without sacrificing too much usability, today we have Rust, as well as a vastly improved C++. (Though both of those languages have terrible compile times.)
[2] To be fair, a memory usage comparison should compare Eclipse not to Vim itself, but to the whole [Vim + coc.nvim + TypeScript compiler] stack, of which most of the memory usage comes from the TypeScript compiler. I'm not sure how that compares to Eclipse. But I'm more concerned about typing latency, where I _do_ only care about Vim itself because all the LSP stuff is asynchronous.
> We also saw the rise of React, which is possibly the greatest tragedy to ever befall front-end programming (and I say this as a recovering React fan).
Amen. Github (just to cite one example) has become much less usable since they switched to React. And it's clearly not a site that needs React, since it worked fine for 17 years without it.
I am still a happy programmer after all these years using only node, express, postgres and sublime. I try not to listen to the sirens singing on the rocky shores...
Just landscape changed significantly comparing to 2010.
Before you didn't have current smartphones and tablets. On desktop you could just support windows only (today probably have to macOS as well). On browser you didn't have to support Safari. You didn't have to worry much about screen DPI, aspect ratio, landscape vs portrait, small screen sizes. Your layout didn't have to be adaptive. There was not much demand for SPA. Back then there was much less people worldwide with access to internet.
Maven was a great idea. Introduce a high barrier to entry for publishing packages. Paired with a search box operated by carrier pidgeon, this effectively meant what you were looking for didn't exist. Every time you had any kind of quirky need, you had to write it out by hand, or find someone smarter than you to do it for you, or worst of all buy it from a vendor for lots of money at horrible quality. People recite 'DSA is bad for coding challenges, when will I need to write a hash map', but once upon a time you did have to write a hash map here and there. Supply chain vulnerability is a cost, but the product was worth the cost: you can just import the darn package!
I need a map of key ranges to values with intelligent range merging, it is right there on crates.io to import, it has been there since 2016, Maven Central didn't get one until 2018. In the olden days either it was in Apache Commons or it didn't exist. Halcyon days those.
“ Once our work is done, we create a “pull request”. This is a way of emulating open-source development inside a single company, which as we know, is the only way to work. Typically, this means that the code is downloaded and built on another computer, and then several hours later, a colleague will come along and ask to change a few words. Once we change these words, the computer builds everything again, and then the next day, the same colleague will allow the code to be merged into the mainline.”
Fix this and your life will be much better, generate testable preview apps on every pr, this feedback loop is a velocity killer. Management for some reason never wants to prioritize speeding it up even though it slows down every single project so advise to just do it and not ask permission.
JavaScript is an interpreted language: write, run. No build steps required.
Building was introduced as a temporary measure, to handle cross-browser awkwardness (grunt and stuff like that). People overused it. We totally don't need it anymore. TypeScript is awesome but a major blocker to this return to a more nimbler ecosystem.
People in the 2000s discovered that mixing code with HTML tags was bad and big complexity demon mansion. By the end of the 2000s, this was fixed in the tools of that time. I consider JSX a best-practices regression. It feels like ASP.NET, but the kids don't notice because they have never seen ASP.NET.
For a while, we also saw npm as temporary. A better thing, more web-friendly, would appear. That never happened.
I just liked programming when it contained a comprehensible amount of abstraction. Stacks have become so tall it is not even feasible for a single human to comprehend what is occurring. I also liked when standards had less surface area. Working in healthcare it has become obvious standards only ever get added, never removed. Complexity is absurd now. I'm not championing that we all become experts in bare metal assembly, but I feel for OP and a desire to at least fundamentally understand what is happening on some level.
> We run our k8s cluster in the “Cloud”. It’s a bunch of services that run on Linux, but we don’t run Linux ourselves, we run it on VMs that we rent by the hour for approximately the same cost as buying a computer outright every month. We do this because no one knows how to plug a computer in any more.
My mind struggles with this reality everyday... the "cloud" has to be the most successful rebrand of all time. In 2005: "Be very careful what data you share on the internet". In 2025: "Yeah, I just put all my shit in the cloud".
I get it. I agree with most of this article. But also like, nothing went away.
If you pine for the days of Java and Maven, you can still do that. It’s all still there (Eclipse and NetBeans, too!)
If you don’t like using Node and NPM, that’s totally valid, don’t use them. You can spin up a new mobile app, desktop app, and even a SaaS-style web app without touching NPM. (Even on fancy modern latest-version web frameworks like Hanami or Phoenix)
If you don’t want everyone to use JS and NPM and React without thinking, be the pushback on a project at work, to not start there.
Programming with Rust and deployment and mgmt with Nix is so much better to how things used to be. Did I mention how much better my Helix works than how Neovim used to? Revision control with JJ, conflict resolution with mergiraf. My personal computers are more powerful than ever before and can get amazing stuff done super fast.
Everything is better and keeps getting better if you make good decision instead of following the lowest common denominator tech.
Java is usable now, but in 2013 it was the worst debugging experience one could have. I would rather work with PHP5 than with Java (unless I started a project from scratch). Also auto-refactoring was clearly worse, because well, Java. It was around that time that I tried Scala then Clojure, and even if debugging the JVM was still an experience (to avoid as much as possible), at least limited side effects reduced the issues.
If programming peaked, it certainly wasn't in 2010.
> it was the worst debugging experience one could have.
Hard disagree. I'm not going to argue that Java debugging was the best, however:
1. You could remote debug your code as it ran on the server.
2. You could debug code which wouldn't even compile, as long as your execution path stayed within the clean code.
3. You could then fix a section of the broken code and continue, and the debugger would backtrack and execute the code you just patched in during your debugging session.†
This is what I remember as someone who spent decades (since Java 1.0) working as a contract consultant, mainly on server side Java.
Of course this will not convince anyone who is determined to remain skeptical, but I think those are compelling capabilities.
† Now I code in Rust a lot, and I really enjoy it, but the long compile times and the inability to run broken code are two things which I really miss from those Java days. And often the modern 2025 debugger for it is unable to inspect some for the variables for some reason, a bug which I never encountered with Java.
That's how I felt at the time, it was my first job and I only had better experiences since then (and I gave it a try again in 2019 and the experience was way, way better). You're right, it probably wasn't the worst of the era, it will still be inferior than any experience a dev would have in 2025.
For the 1: not really applicable in my case. For 2: I didn't know this. For 3: yes, but it worked only for a subset of issues, and honestly much more usable with Clojure and Scala.
I primarily worked with Hadoop and ETLs, you probably won't be able to convince me to be fair.
My first text editor for PHP was Komodo Edit, it was super slow and everyone jump shipped to Sublime Text, then VSCode was slower than Sublime but had incredible industry supported extensions like Git and Prettier, programming didn't peak during my PHP days, in fact the PHP frameworks sites I used are still around and incredibly slow.
I am building an AI coding tool that doesn't eat RAM, there are super lightweight alternatives to Electron.
Well i am a Java developer in 2025 and we still use maven, we also got IntelliJ which is miles better than eclipse and the company where I am does hire testers.
The world is not worse, you just ended up stuck in the wrong tech stack with the wrong company.
I do agree that the JS ecosystem is terrible tho, and i was a full time js dev before (now i only do some frontend from time to time) we already have a dedicated frontend team.
> Funnily enough, everything ran at about the same speed as it does now.
I've often thought about how certain properties of humans impacts the tech we make and accept.
For instance, to a human, something happening in a couple of seconds is quick, and in several seconds is fairly quick. Hence, build steps etc tend to creep up to those sorts of numbers.
In this respect I’m liking vibe coding. I can tell it use html css and js only and make me a frontend.
That obviously has severe limitations but ideal if you don’t like the front end framework scene and want to put all your logic in backend. And there I find it a bit easier to navigate
RIP guys in corporate that have things imposed on them
Javascript wins by keeping the costs down. Companies today want to do more with less, which is how it should be and you are still free to choose from a myriad of technologies. When you pair this setup with LLMs, it's actually the best it has ever been IMO.
If the author doesn't want to work with NPM and the JavaScript ecosystem he could just get a job writing Spring/Boot, which makes up probably 90% of the jobs at large enterprise companies. I don't agree that this world has disappeared...
Defining peak programming as entreprise Java using Eclipse on SVN is border delusionnal imo.
> And here’s the funny thing: it never broke, because the person who built it did it well, because it wasn’t taxed within an inch of its life, and because we were keeping an eye on it.
I think I’m lucky, because for me it’s the other way. In 2009 I started my first real programming job writing c++ in vim. For the last 5 years I’ve been writing rust in helix and things have never been better.
Programming used to be about finding the best way to communicate with the device. Now the device is trying to figure out the best way to communicate with you.
There's something to this. I recently shipped a music curation site and deliberately avoided React/Next/etc - just HTML, CSS, vanilla JS. The cognitive load difference is stark. The 'peak' might be less about capability and more about us rediscovering that simpler tools often suffice.
Same. I build stuff for local businesses in my area with nothing but boring old HTML, PHP, CSS and JS. I guess my shit isn't "web scale" but it works, and it works consistently, with minimal downtime, and it worked during both Amazon and Cloudflare's latest outages.
I don't need my software to eat the world, I'm perfectly content with it just solving someone's problems.
It's all about picking the right tools for the job. The "cognitive load" might be larger in a vanilla project compared to React when your interface is more complex and interactive.
Honestly, the person should spend their time of fixing their shit instead of writing blog posts.
I find intellij a great IDE, modern frameworks are fun to use, ai helps me doing things i don't want to do or things i just need (like generate a good README.md for the other people).
Containers are great and mine build fast.
My Startup has a ha setup with self healing tx to k8s and everything is in code so i don't need to worry to backup some random config files.
Hardware has never been that cheap. NVMs, RAM and Compute. A modern laptop today has a brilliant display, quite, can run everything, long batterytime.
Traffic? No brainer.
Websphere was a monster with shitty features. I remember when finally all the JEE Servers had a startup time of just a few seconds instead of minutes. RAM got finally cheap enough that you were able to run eclipse, webserver etc. locally.
> The most popular is “VS Code”, which needs only a few gigabytes of RAM to render the text.
> We used Eclipse, which was a bit like VS Code.
This made me laugh. You can't possibly be a serious person if you think Eclipse was better in any way shape or form than VS Code.
I don't have a great memory, but one thing I can absolutely still remember with 100% clarity is how bloated and memory hungry Eclipse was. It was almost unusable.
Me, a young, but old fart at heart, writing firmware in C and applications in C++ (just for Qt!) that see everything wrong with the programming world today VS the junior that keep asking why we don't do the thing in javascript so we can have it on mobile as well (we do, we just use a different framework 'cause react won't ever cut it for our needs. It just takes a bit of what is called "effort" to make things look the same on all platforms) and wants emails lists to plan going out for a drink instead of, you know, asking. We're all in the same small office. Same stuff about deploying, we need github (no we don't. private git server), we need aws, woah what is this npm attack you're talking about?
At times it seems he's learning, but then he leans back into GPT and it feels like a lost cause. Yo bro it's crazy, i just deleted 2k lines of code, as if it was normal, with me raising eyebrows asking how many modules were outright deleted and never needed to be there in the first place.
Problem is, GPT and company will happily throw a lot of puke at the project and trust me bro that's essential we plan every single possible feature first and foremost instead of just testing the basics and build on top of them, because we have literally two requirements, so it's taking two months to do something i could do in two weeks, not because i'm more experienced, but because we should be doing what i'm telling to do, and not discuss whatever bullcrap the artificial manager is suggesting, which i would love to have the power to outright ban from our network.
Me and the junior have more or less the same age, just very different life journeys that led to programming
strawman dystopia. simply choose to continue applying wise practices of old. be the effect you wish to see in the world. just because others are jumping off a cliff like lemmings does not mean you must as well
I'm enjoying some things about the programming world now, especially compared to my professional start circa 1997.
I started on C++ on Windows, using MFC, and also using Visual Basic 5.0 when it came out. VB made my eyes bleed, but a lot of people are nostalgic about it. Visual C++ did not have many fans, but it had a lot of users. I got the first taste of the Microsoft treadmill during those days, where they would get you to use a new thing, and then in a few months they hardly used it anymore, and they were promoting the next new thing. As soon as you got comfortable with MFC, they were pushing ATL, and then .NET, etc. Really, the people who were happy with what they had and never upgraded were better off.
I narrowly missed the big-manual days of programming, where it was unlikely you had online resources to help you through it. The Turbo Pascal folks and the early Mac folks remember that well. Instead, we had the big online help file (CHM) and search engines like Altavista. Code examples were few and far between. We often spent a lot of time just figuring out how to make the right incantations to get things to do what we wanted. There was a happy path, like with MFC if you make the same exact application over and over again. And then there is the difficult path, where you want it to be a little innovative.
I came across Squeak Smalltalk and used that a lot for my own personal exploration, so I always felt like there was something missing from the world that actually came to be. Still, working alone on Squeak is only as fun as long as you don't get bored and don't need something that Squeak was too slow to handle.
Like the author, I was into pair programming (eXtreme programming, actually). I never understood its detractors. Working was pretty fun.
I never liked the MS ecosystem so I enthusiastically accepted Java. IBM offered a lot of support for Linux and there were good applications waiting to be written. It had its growing pains but quickly settled in to being very productive. In this period, Intellisense and similar technologies were becoming commonplace and the Refactoring Browser had been developed (for Smalltalk but then basically for Java). IntelliJ IDEA was released and was, honestly, revolutionary. The previous IDEs were just not serious until they caught up with the developer support in IDEA.
I figured out that being a professional programmer is not for me, because I don't enjoy working on projects, and I went back to school, eventually becoming a veterinarian. So my professional career kind of ends there.
I enjoy programming, but as a casual programmer it is hard to work on something and come back to it every few months. Things do seem to rot. What compiled before doesn't now. Library use changes radically. If you started a React project before hooks, you know what I mean. Sure, you can still do it without hooks, but nobody does so you're on your own.
What AI does is it makes exploration and problem solving, as well as understanding what I did a few months ago so much easier. I don't have anyone to pair-program with. But the AI makes it easier to be the programmer who's not in the driver seat. I like that, and I think it could lead to good things in the field. The big risk is that LLMs are not very good at future things. If things are out of their training window, they make lots of annoying mistakes. For example, Debian Bookworm and Debian Trixie are somewhat different, and Claude doesn't know what it's doing yet with Trixie. Claude thinks the most recent version of Python is 3.11 or something. With LLMs you have to be comfortable working on yesterday's code. But for most of us, that's OK.
This feels very much like the tired "the modern internet sucks - the old web with old websites was better!" trope that appears on here regularly.
You can still code the old way just like you can still put up your old website. No one is forcing you to use AI or VS Code or even JavaScript.
Of course you.might not getting those choices at work, but that is entirely different since your paid to do a job that benefits your employer, not paid to do something you enjoy.
This article in different forms keeps making the rounds and it's just so tiring. Yeah, let's remember everything that was great about 25 years ago and forget everything that sucked. Juxtapose it with everything that sucks about today but omit everything that's great. Come on man.
If you think things suck now, just make it better! The world is your playground. Nobody makes you use YAML and Docker and VS Code or whatever your beef is. Eclipse is still around! There's still a data center around your corner! Walk over and hang a server in the rack, put your hardly-typechecked Java 1.4 code on there and off you go!
> The world is your playground. Nobody makes you use YAML and Docker and VS Code or whatever your beef is
Nobody, except your future employment prospects.
There's good reasons and bad reasons for a lot of technical options; "can I hire people to do it?" is a very good reason, but it does directly lead to CV-driven-development, where we all chase whatever tech stack the people writing the job adverts have decided is good.
The same people who capitalise "MAC" in "MAC & PC", the same people who conflate Java with JavaScript, the same people who want 10 years experience in things only released 3 years ago.
Right, and there's the rub, and what's behind all these changes - coordination. We containerized to coordinate our ability to use lots of different runtime environments. We typescript'd and python'd the web stack so that our frontend and our data friends could feel at home in the backend. We created ever-more-elaborate package repositories to make layering increasingly complex software projects simpler.
I think what people who write essays like this wish for is the smaller scale of things. Industrial steel production is objectively better than old-timey blacksmithing, but hammering out sets of cutlery certainly feels a lot more personal. Steelmaking wasn't better before all these fancy mechanisms and danger and pollutants and logistics, but when it was craft, it was more satisfying to work on.
It sounds fun hammering out a set of cutlery but after the... Like... First two... You go screw this, give me a metal stamping press.
That was very well said - that's how I really feel.
Sure, you can do that for your hobby projects. But "at work" you generally have these decisions made for you. And these decisions have changed over time for the wrong reasons.
As an aside: if we say k8s, we should also say j8t.
> But "at work" you generally have these decisions made for you.
The idea that most employers make terrible decisions now, and amazing decisions back in the day, is plainly false. The author vividly recollects working at a decent Java shop. Even there I strongly doubt everything was amazing as they describe, but it sounds decent indeed. But plenty businesses at the time used C++, for no good reason other than inertia, usually in Windows-only Visual C++ 6-specific dialects. Their "build server" ran overnight, you'd check in your code in the late afternoon and get your compile errors back in the morning. The "source control" worked with company-wide file locks, and you'd get phoned your ass back to the office if you forgot to check in a file before leaving. Meanwhile, half the web was written in epic spaghetti plates of Perl. PHP was a joy to deploy, as it is now, but it was also a pain to debug.
If you care deeply about this stuff, find an employer who cares too. They existed back then and they exist now.
> Their "build server" ran overnight, you'd check in your code in the late afternoon and get your compile errors back in the morning.
This. Let's keep things in perspective when people complain about long Rust compile cycles. And even that's a whole lot better than filling in paper-based FORTRAN or COBOL coding forms to be punched into cards in the computing room and getting back line-printed program output (or a compiler error) the next week.
Rust's notorious compile times sticks out like a sore thumb partly because other system languages can run laps before your Rust build is done. And also because everyone and their grandma swears Rust is blazing fast.
Until you have to compile the program without prior build cache or start a build in a CI pipeline.
This is like economic growth: First bad, then upwards trajectory, then now in free-fall
You are describing it: Things in programing were bad, then suddenly all in the upside UNTIL it start to coming down.
Is not a refute of the problem. Is to pick a moment were both were bad, and like all the discussions about tech, MASSIVELY ignore that MASSIVE internet with MASSIVE money with MASSIVE backing is worse than before.
Is like people complaining that pistols on the wild west kill as do nuclear weapons, ignoring the massive difference in size and blast damage
Amen.
We love the idea that we don't have any agency in this field and we're constantly being pushed by the mean baddies at the top.
Not everyone has the privilege to live in world regions where there is a wealth of options in job opportunities.
Did people really only compile once a night in the days of visual studio 6? There were pentium 2s and 3s back then.
In large C++ codebases of mediocre quality (the example I'm referring to is a manufacturer of large complex machines), yes.
People would compile their local unit locally, of course (a "unit" would be a bunch of files grouped together in some hopefully-logical way). But they wouldn't be 100% sure it compiled correctly when integrated with the larger codebase until the nightly build ran. So like if you didn't change the .h files you were pretty sure to be in the clear, but if you did, you had to be careful and worse-case-scenario do a 1-day-per-step edit-compile-test loop for a week or so. I'm not entirely sure how they managed to keep these compile failures from hurting other teams, but they didn't always (I think they had some sort of a layered build server setup, not too dissimilar from how GH Actions can do nightlies of a "what if this PR were merged with main now").
Visual Studio 6 itself was pretty OK actually. Like the UI was very limited (but therefore also fast enough), but compiling smallish projects went fine. In fact it was known to be a pretty fast compiler, I didn't mean to suggest that VC++6 implies overnight builds. They just coincided. In fact better-structured big-ish C++ projects (pimpl pattern anyone?) could probably recompile pretty quickly on the computers of the day.
It was definitely on the order of hours for large code bases - the Microsoft Excel team passed out punishment “suckers” for those who broke the build - causing 100+ people to not have a new working build to look at and test.
Linux kernel compiles in the 1990s were measured in hours, and that codebase was tiny compared to many. So, yep, builds were slow, slow enough to have an entire xkcd comic written about them.
Entire builds being slow isn't the main point though, it's iteration time from changes. I have a hard time believing people were working on a single compile a day and building an entire huge program on every iteration. That's the whole point of compilation units.
The "terrible decisions" of yore hold no comparison to today's "terrible decisions". It's not the same ballpark, it's not the same sport.
jubernetes?
That's the "let's rewrite k8s in proper enterprise Java like it was meant to be in the first place, none of this Golang nonsense" project.
funny enough, I believe Kubernetes before v1.0 _was_ written in Java!
jubernetet
> And these decisions have changed over time for the wrong reasons.
Have you ever considered that you don’t understand why those decisions were made and that’s why you think they were made for the wrong reasons?
I simply don't agree with the reasons, while you seem to imply that all decisions made, are good.
The reasons are always the same. 20% because some changes are actually improvements, and 80% cargo cultism where if you just build the right containers and chant the correct YAML incantations, you too will become a Google… followed by the phase where everybody just keeps doing these things because they organizationally don’t know any other way anymore, until the next big trendy thing, which does revert some of the issues of the previous trendy thing, but introduced a new set of already solved problems because this profession is incredibly myopic when it comes to history.
If Google does it, maybe it'll work out for my small business, right...?
> j8t
Javascript?
That would solve the trademark problem...
> if we say k8s, we should also say j8t
It’s that one extra spoken syllable that pushes it into k8s I guess. ¯\_(ツ)_/¯
But it's only used in written form. You don't actually say out loud "kay eight es", do you?
Kocho rolls out the tongue for Spanish speakers.
Sounds like “coso” (“thingy”, mildly despective).
Haha, oh my, no. That would be silly.
Clearly it’s “Kates”. Like “sk8er boy”.
How do you say i18n?
In my head?
Something like slurring the word “internationalization” combined with 18. “Ill-ateen-yon”
(In general I hate these numeric abbreviations, they’re terribly opaque to anyone who’s not clued in)
One of my favorite T shirts is a custom black one that says `f2k i18n` in a white typewriterish coding font. (Thanks Roman!)
Most people are confused by it. When I start to explain it, I sound like a jerk who hates foreigners.
The programmers on the street point and smile at it. If they work in `l14n`, they come up and give me a hug.
l10n, surely?
You are correct! I need a tshirt to keep it straight.
Eye eighteenin
institutionalization
Kates vs Jate?
kate's
Seriously? What if you have a Kate in your team?
Then she ends up taking the blame for causing lots of headaches from people that can’t parse context
It's sometimes Kate, Jason, or Yamal.
But it's always Dennis.
The automated system rejects their CV when applying obviously
> If you think things suck now, just make it better
This completely ignores the fact we're doing this for our boss, not for ourselves
> Yeah, let's remember everything that was great about 25 years ago and forget everything that sucked. Juxtapose it with everything that sucks about today but omit everything that's great. Come on man.
That's fair. When I see bad code today, and try to explain to myself what's bad about it, I realize that people totally did the same things 25 years ago.
Nowadays there is just so much more code, and we stand on taller piles of "architecture" trying to scale higher heaps of expectations. The thing is, the effect of the bad stuff seems to compound more readily than the effect of the good stuff. And meeting the demand for more code involves broadening the base of people doing the coding.
> If you think things suck now, just make it better! The world is your playground.
I agree with this. A lot of the modern expectation is artificial, emphasizing form over function. Even where it isn't, a lot of the modern technique is unnecessary cargo-culting. You can do a lot locally if you believe in your machine (https://thundergolfer.com/computers-are-fast ; https://www.youtube.com/watch?v=ucWdfZoxsYo).
For PAPER I'm targeting Python 3.6+ (where they added `pathlib.Path` and f-strings, and upgraded the SSL version) with the intent to support it indefinitely (which involves forking certain dependencies).
They don't want a cure, they want something they can bitch about.
I think it is a great exercise of self awareness to take a step back and see how things are done now.
I started my first prpgramming job in 2003. Some things where better, others were worse. But the only way we can improve the "craft" of software development is by having introspection. It's kindnofnwhat happen during the "software crisis" of the 80s, and why "waterfal" was rrplaced by "iterative" software development.
Now, with such an impactful change like AI aided coding, it is a great opportunity to see if we can evolve anything in the building process.
Speak for yourself. The pathologies/neuroses on display here... 'cure'... 'bitch'... seriously, are we still talking about software?
Is that so, doctor?
Yes, good of you to ask. But don’t you worry your little head, now! You aren’t the first patient that developed a thin skin from their own medicine, and you won’t be the last.
Yea, my immediate reaction was, “Okay. Stop doing all the stupid stuff.” If you want to program like it’s 1999, go for it. I generally don’t use AI, for instance. I just haven’t found it to be a net-positive yet.
The better tools are already there. It's not about making it better. It's about most programmers today choosing mediocrity.
Sometimes, you can avoid contact with this mediocrity, but often you don't and you're forced to play in this swamp.
> choosing
Sometimes the programmer doesn't get to choose. I do find the business drive toward mediocrity quite maddening.
Yes, sometimes it's that, but what I've observed in the field is self-inflicted by programmers. It's the impostor syndrome. They don't know, but they don't want to show that they don't know. They look around for clues of what to choose. Monkey see, monkey do. And then, like monkeys, they bash their keyboard until it seems to work.
And in fact, professionally, I still live in the good old days. I code in Java 21, I minimize dependencies, and I use an IDE that can do the heavy lifting when I want to refactor something…which is often. I produce a .jar that gets installed with a loader script rather than in the cloud. And it all works, and it’s *stable*.
Just yesterday a friend and I was talking about writing a clone of a popular website, using the technologies of yesteryear. There's absolutely no reason why we wouldn't be able to make a credible competitor using mod_perl and db2.
From a technological view, we're a point where your development stack doesn't matter all that much.
>Nobody makes you use YAML and Docker and VS Code or whatever your beef is.
Not VS Code, but maybe YAML and Docker if your company is trying to align what tools it uses. C# places might still force you to use Visual Studio proper. Everyone says use the right tool for the job, but for bog standard CRUD web development, we do have a shitload of tools that work and there's multiple ways to get to a fast, working product.
I still chuckle that my laptop is 3 times as fast as the cloud thing that serves our CRUD app and we pay many more times for it, but also knowing full well I do not ever want to be RDP'ing into a production box again and pouring through IIS or Windows logs.
What I definitely do see is a degradation in making choices about when to adopt a more complicated technology because of the incentives of the hiring market.
People have loudly beaten the drum to keep your skills up to date and so people choose stuff that's popular because it benefits them personally, even when the product doesn't need it. This in turn leads companies to only select people who know that stack, and the more that companies do that, the more people make technical choices to get them the best job that they can handle.
We absolutely, very much 100% see that happening now with LLM AI if you ever needed a bigger piece of proof. Pretty much everything that is happening now has just been a louder example of every bad practice since the run up to the dotcom bust.
Because of that, I'd frankly never suggest running on-prem or building a local-only app unless there was a much bigger reason (legal, security, whatever) especially if the other products in the company have chosen the cloud.
Why? Because convincing the next job that that would have been the right choice is too hard.
Edit: and to someone else's point, I made the choice to be in the Microsoft/Azure/Windows hell hole but digging myself out and moving to something else is practically working a second full-time job and holding 2 ecosystems in my head at once
I both agree and disagree with you.
On the one hand: yes, this dev has clearly chosen a career/language specialization that puts him knee-deep in the absolute worst tooling imaginable.. I cannot fathom a workflow this fucking miserable and if this was my day to day, I would be far, far more depressed than I already am.
AND, the fact that so very very much of our industry does run, perhaps not all of, but a significant amount of a workflow not awfully different from this is IMO, an indictment of our trade. To invoke the immortal sentiment of the hockey coach from Letterkenny, this shit is FUCKING embarrassing.
So much major software that ships in a web browser because writing for Windows, Mac and Linux is just too hard you guys, it's simply too much for a sweet little bean like Microsoft ($3.62 trillion) to manage as they burn billions on AI garbage, is FUCKING embarrassing.
Half the apps on my phone are written this way which is why they can barely manage 30hz on their animations, die entirely when S3 goes down, and when they are working, make my phone hot. To run an app that lets me control my thermostat from my desk. That's FUCKING embarrassing.
And my desktop is only saved by virtue of being magnitudes more powerful than my original one back in the 90's, yet it only seems a scant more capable. In the early 00's I was sitting on Empire Earth and chatting with people over TeamSpeak. My computer can still do this, and with the added benefit of Discord can stream my game so my friends can all watch each other, and that's cool, apart from I lose about 10 fps just by virtue of having Discord open, and when I'm traveling? Oh god forget it, Discord flounders to death on hotel wifi despite it being perfectly cromulent DSL speeds. Not BLAZING, surely, but TeamSpeak handled VOIP over an actual DSL connection, with DSL latency, in the 00's. That's FUCKING embarrassing.
All our software now updates automatically by default, and it's notable when that's a GOOD thing. Usually what it actually means is the layout of known features changes for seemingly arbitrary reasons. Other times more dark patterns are injected. And Discord, not to pick on them, but they're the absolute fucking worst for this. I swear they push an "update" every time one of their devs sneezes, I usually have to install 18 such updates on each launch, and I run it very regularly! And for all that churn, I couldn't tell you one goddamn thing they actually added recently. FUCKING embarrassing.
And people will say "oh they could be better," "we know we can do it better," "these aren't the best companies or apps" okay but they are BIG ones. If the mean average car in America got awful fuel economy, needed constant service, was ill-designed for it's purpose and cost insane amounts of money...
Oh, that happened too. I think I just made my metaphor more embarrassing for another industry.
old man claims society collapsing; back in his day…
I wish people were not so inclined to reply with "Ad Hominem Ridicule" one liners. I like a good joke, but such replies lack a certain level of content that addresses the point and feel "low effort".
I do agree that comparing the past with the present if fraught with complicated nuances, and people do tend to see the past with rose tinted glasses. But, I read Talwar's blog post more as a personal reflection on their experiences they are facing and not some kind of scientific treatise on what went wrong.
fair criticism; didn’t mean this as an ad hominem but rather a summarization of (as the comment I replied to points out) this genre of article that keeps coming up (and not just for programming); it’s exhausting mindset to see repeatedly and breaking it down into the core argument (“I liked things better when I was younger”) does have some value IMO
if this were titled “Java/JavaScript peaked” or “my reflections on XYZ” and written like that, I wouldn’t have given it a second thought. but claiming programming peaked 15 years ago leads me to not feel bad about my summarization
You'll get old too one day and it will look a whole lot different watching the younguns stumble through completely avoidable mistakes and forget the long lessons of your life that weren't properly taught or were just ignored.
We have records from many periods in history of old men crowing about how society is collapsing because of the weak new generations. Thing is, maybe they were always right, and the new generations just had to grow up and take responsibility? And then again, maybe sometimes they were little too right and society did in fact collapse, but locally.
“Hard times create strong men. Strong men create good times. Good times create weak men. And, weak men create hard times.”
― G. Michael Hopf, Those Who Remain
Agreed! If anything, I think I'm tired of the "everyone says this when they get old!" hot take. Sometimes things really do get visibly worse and the intergenerational complaining about it is due to it really happening.
I bring this example up every time, but I'm a baseball fan. And seemingly every generation of fan has said there's more people striking out than there used to be. Is it because there part of getting old as a baseball fan? No! It's really happening. Strikeouts have quite literally been going up from one decade to the next for basically a century.
So sometimes it's because the thing is really happening. Environmental ecosystem collapse? Real. People having shorter attention spans every next generation? Real! Politics getting worse? Well, maybe the 1860s were worse, but the downward trajectory over the last 50 years seems pretty real. Inefficiency of increasingly automagic programming paradigms? Real!
Sometimes things are true even if old people are saying them.
> Hard times create strong men. Strong men create good times. Good times create weak men. And, weak men create hard times.
Actually it's the opposite.
Strong men create hard times by trying to show to each other how strong they are. Hard times create weak men because during hard times strong men kill each other, thus mostly weak men remain. Weak men create good times because instead of trying to show their strength they just build stuff so that the world is easier for them. In good times people breed and the population returns to the mean with just enough strong men to start the cycle again.
WWII was the last time strong men created hard times. We are overdue for another round and it shows.
The quote at the end has absolutely nothing to do with old people not liking change.
It kind of does, no one repeating it ever thinks they’re the weak men creating hard times
That's because the thesis it's expounding on isn't "old people don't like change", but rather "experienced people often see their juniors unknowingly making avoidable mistakes".
An interesting Reddit r/AskHistorians thread on the question """Does the aphorism "Hard times create strong men. Strong men create good times. Good times create weak men. Weak men create hard times", accurately reflect the evolution of civilizations through history and across different cultures?"""
copying only the conclusion for a tl;dr: "The only way that the aphorism explains history is by reinforcing confirmation bias - by seeming to confirm what we already believe about the state of the world and the causes behind it. Only those worried about a perceived crisis in masculinity are likely to care about the notion of "weak men" and what trouble they might cause. Only those who wish to see themselves or specific others as "strong men" are likely to believe that the mere existence of such men will bring about a better world. This has nothing to do with history and everything with stereotypes, prejudice and bias. It started as a baseless morality tale, and that is what it still is."
https://old.reddit.com/r/AskHistorians/comments/hd78tv/does_...
That reply completely misunderstands the quote. It is about how people with integrity, who are willing and able to put out effort and endure difficulties to build a better future, do usually manage to make things better than those who do not.
It’s essentially a truism warning people that problems you ignore don’t fix themselves, and has nothing to do with gender or gender stereotypes, that’s a linguistic misunderstanding. In this context, “men” is gender neutral and means “people.” In old english, the word “men” is explicitly gender neutral and there was a different word, “wēr” for male people, which is still used in some contexts, e.g. “werewolf” means wolf man.
[dead]
Ironic given how strongly Reddit, r/AskHistorians, and the humanities in general bring their own biased lens to bear. Just like everyone else.
I’m not sure what you mean. I don’t see a bias here, the point is plainly stated: the notion of weak men is dubious. You might not agree, but then engage with something substantial.
If you don’t see a bias in political communication (and that is what all of this is), then chances are very high you share the bias.
Abundance allows comfort, comfort enables complacency, and complacency can weaken the social fabric by encouraging short-term gratification over long-term maintenance.
People worry about masculinity because masculinity requires structured, pro-social outlets to not be toxic. A aimless or misdirected male population is an incredibly corrosive and/or dangerous thing. It can rot out a society from within, or make a society susceptible to subversion from without.
Societies use rhetoric about strength because if a society does not maintain systems that cultivate competence, responsibility, purpose, and pro-social ambition (especially in its most impulsive members), it becomes brittle.
You're doing the same assuming "good times = comfort = weakness" as a thing you already think, which is what the long reply I linked is debunking. What you said implies an opposite, something like: scarcity and famine strengthens the social fabric by encouraging long-term thinking over short-term maintenance. Actually it doesn't, scarcity leads to dog-eat-dog short-term survival tactics anything from stealing from neighbours, eating next year's seeds, up to eating the farm dog or selling the farm machinery or cannibalism, and leads to squalor, disease, and fire risks because nobody has time or energy or resources to spare on anything but the most urgent survival.
Abundance, by contrast, allows seed saving, food storage for winter, spare resources to use on washing and hygiene and medicine and recovering from illness, rule of law and enforcement, time away from subsistence farming and scavenging for food to enable things like developing metalworking skills, inventing, practicing archery, spending time on other society-building rituals like building churches and going to church.
> "A aimless or misdirected male population is an incredibly corrosive and/or dangerous thing"
If they are "incredibly dangerous" does that not make them "strong"? These are supposed to be the "weak men" created by "good times", aren't they? Are they strong men created by weak times who are themselves creating weak times by rotting society? Or are they strong because they are men, independent of the times? Does this fit into the saying at all?
> scarcity and famine strengthens the social fabric by encouraging long-term thinking over short-term maintenance
Famine is not isomorphic to “hard times”, and particularly not what the aphorism is referring to: self-created hard times, wherein a society’s ability to self-sustain and compete externally is needlessly curtailed.
> If they are "incredibly dangerous" does that not make them "strong"?
I said corrosive and/or dangerous, and weakness can be both corrosive and dangerous.
What you linked to was not a debunking. It was a political viewpoint. Reasonable arguments exist for a different one.
> "Famine is not isomorphic to hard times"
Nobody claimed it was
> "particularly not what the aphorism is referring to"
The aphorism does not say what it is referring to, you are making this up so it says what you want it to say (which is bias). This wouldn't be a problem if you used that to make a point and argue your point, but it is a problem when you just go "I imagine that it means something else, so you're wrong". Self-created hard times such as ... what? If laziness in farming doesn't create famine in winter... what hard times are more relevant than that for a society in 0 AD? "Needlessly curtailed" by who or what effect?
> "I said corrosive and/or dangerous, and weakness can be both corrosive and dangerous."
Can it. Is there any way to measure this weakness? Is it actually a thing?
> The aphorism does not say what it is referring to
In which case it makes no falsifiable claims. If “hard times,” “weak men,” and “strong men” have no stable meaning, the cycle can’t explain anything and can be retrofitted to any narrative. There would be nothing to argue for or against.
That isn’t the case. “Hard times” in this context means the cumulative internal consequences of institutional decay, complacency, and short-termism. Not natural disasters. That’s why your famine example is irrelevant.
> Is there any way to measure this weakness? Is it actually a thing?
Sociological concepts are evaluated by their broad effects, not by a single scalar value. Declining institutional competence, eroded norms, reduced accountability, and loss of collective purpose are both observable and historically recurrent.
That’s your opinion, but like I said it’s not valid to imply that it is the normal view and those not agreeing are biased. Instead of trying to hear understand and challenge what historians have to say you flee intellectually, which is ironic given your take on strong men.
I’m not historian but for example I could challenge the idea that a rhetoric about strength and keeping a masculine ideal for the young male population was non existent in European feodality where only nobility had the privilege of fighting, and 90% of the population were farmers. Or that 2000 years ago Jesus already challenged the idea that men needed to be strong in the traditional sense, and that real courage was loving and forgiving among others. I could go on with fashion and clothes but maybe just look at a West European king painting to reevaluate what masculinity is supposed to look like traditionally.
My understanding is that your rhetoric appears only recently (and is therefore not traditional) coinciding with nationalism rise and the need for bodies to throw in the total war (another modern invention) meat grinder.
You can disagree, and I’m open to hearing your counter arguments, because I’m not dismissing you as biased.
> Instead of trying to hear understand and challenge what historians have to say
One self-described historian. On a Reddit post. Let’s not pretend this is the unified or authoritative voice of the discipline.
> I could go on with fashion and clothes but maybe just look at a West European king painting to reevaluate what masculinity is supposed to look like traditionally.
You’re conflating aesthetic masculinity with functional masculinity, and that’s a category error. The aphorism isn’t about how men dressed in the 17th century or how they signaled status — it’s about what kind of men can sustain a civilization.
In this context, “strong men” refers to individuals who demonstrate the discipline, competence, long-term responsibility, and willingness to bear risk that are required to build, maintain, and defend the institutions that keep a society stable — especially when conditions are difficult. It’s a sociological concept, not an aesthetic one, and it has nothing to do with your personal distaste (or favor) for particular cultural aesthetic expressions of masculinity.
Everything you've said about comfort and complacency is equally if not more true of scarcity though. Scarcity leads directly to short-term thinking because there's no future to plan for or maintain. Erosion of social bonds happens as desperation increases and people turn to grifting and taking advantage of each other. The original quote is a little too tidy, an oversimplification that fails to grasp a complex reality and seems to have its own agenda/bias. Which you presumably agree with or you would have caught it. The truth is that there are varying levels of easy and hard times, and either one can "create" either kind of man. (And I'm ignoring masculinity as an issue; everybody knows whether they're a man or not.)
Or I can reframe it one more way: If good times create weak men, then all the rich people currently running things corruptly and soaking up whatever 90% of the wealth, are weak, and all the discipline and virtue in society are among the rest of us. Cultivate competence, responsibility, purpose and pro-social ambition in the super-rich and you might have something there.
"Strongly" and "just like everyone else" are contradictory, no? Assuming "strongly" is somehow relative. If you have an absolute measuring scale for bias-bringing-to-bear, I would love to hear about it.
It’s relative to no bias at all, and I was trying to be gracious.
Just because it says "men" doesn't mean it's about masculinity. Rather, my reading of "strong men" is closer to "people with a strong work ethic, integrity, and zero tolerance for corrupt grifters," and my reading of "weak men" is "people with zero work ethic who are in fact, corrupt grifters."
they were not right and I promise when I’m old, I will not have this attitude. it’s one of my least favorite types of people; and that’s precisely my point, old men have been saying society is collapsing since ancient times, yet here we are, with things better than ever
Fwiw I'm with you here. It's perfectly possible to stay excited about new stuff. Just.. take it for a spin! Find the good parts even when they re-make mistakes from the last time someone tried sth like this 2 decades ago.
Like, when React was new I had total Delphi deja vu. And then they went about reinventing MVC (not the Rails MVC, real MVC) and calling it "unidirectional data flow" instead of just MVC, and feeling all smart about themselves and doing proud conference talks, and I was like "this is just MVC but with worse naming".
But React also made it so that every component is designed to be reusable. Like, in Delphi you had a "Form" on which you dropped "Controls" and then you could also create your own controls if you were really advanced. But most people didn't feel like they were advanced enough, so code reuse was a mess. React made it so that every control (cough component) is reusable, because using components is the same as making components. That's a good idea! Purely functional UI, that's also a good idea! Then they threw OO out instead of fixing it, that was a terrible idea, but bottom line it's still great! Plus, Delphi didn't have to deal with the horrible mess that is HTML and CSS so it had it easy.
But yeah lots of people my age saw the same, saw how it was just Delphi all over again but with different mistakes, and focused on the mistakes. It really is purely an attitude thing.
I'm having a lot of fun with signals and SolidJS and observables now and it baffles me that something so elegant and fast took this long to be discovered (or more like, to get ergonomic and mainstream enough).
> I promise when I’m old, I will not have this attitude.
To my ears this is a hilariously naive statement. It sounds to me to be roughly the equivalent or a 7-year old saying "Adults have boring jobs where they sit at a desk all day. I hate it. I promise when I'm old I'm gonna be an Astronaut or play Major League Baseball."
It's not that they don't mean it, it's that one should make promises about a situation they can't yet understand. While some of those kids probably did end up being astronauts or baseball players 99%+ who made that promise didn't. It turns out that being an adult gives them perspective that helps them realize the reasons they want a desk job even if they don't like it, or for many they actually enjoy their desk job (ex they like to program).
So the same if a million young people all thought similarly, and then magically changed their view when they got there dont promises your going to be the one who will break the streak.
You might turn out to be an astronaut, but many people listening, based on good previous evidence will rightly assume you won't.
> situation they can't yet understand
you’re wrong right here — I understand. you’re just speaking nonsense and bullshit; you sound naive to me
Read what you just wrote. You are just declaring a belief, not making an actual point.
Do you expect to learn? Get wiser?
If you do, you will eventually develop wisdom that younger people don’t have yet - or may never get. Younger people find new ways to do many things better, but regress in other ways. Lacking your (and your generation’s common) experiences.
Which is why the only old people who can’t see any real regression are … well I have yet to meet that kind of old person, other than those unfortunate to have dementia.
Also, every new better (or perceived better) way to do things has to reinvent many obvious things all over again. Things many won’t realize were already solved by previous practices. Which takes time.
So meanwhile, regressions.
And there is no assurance that new ways will really be better, after all regressions are addressed. Because it is impossible to see all the implications of complex changes.
Anyone who isn’t aware that the amount of today’s glue code, rewriting of common algorithms for slightly different contexts, the mush mash of different tools, platforms, and dependencies, and all their individual quirks, was a non-optimal outcome…
But the current pain points will drive a new way. And so it goes.
Progress is not smooth or monotonic.
It is a compliment to discount that you won’t also notice. Not a critique.
??? my point is someone who doesn’t know the first thing about me called me naive and made bold claims about my future that I’m certain are wrong; time will tell but there’s nothing of substance to discuss from their comment, hence my reply
you’ve also just said a ton of stuff I don’t disagree with, but I’m not sure what discussion you’re trying to have here
I do regret the time spent reading this article and participating in this comment section; that was naive of me!
Fair enough.
The word “naive” was a strong one to throw at you, but I think in the context it reflected irony and humor, not disrespect.
Anyone who learns anything looks back on a naive version of themselves. I remember thinking a lot like you, too.
(I don’t think things are collapsing, but do see significant unnecessary regressions in the state of programming: Madness, insanity, everywhere! :)
> Anyone who learns anything looks back on a naive version of themselves. I remember thinking a lot like you, too.
I'm so glad that for the most part in my early internet days (early 2000s), I was pseudonymous. I tended to have very strong opinions about stuff I had barely just learned and didn't have experience to get nuances. My political opinions have completely flipped and I look back on my young firebrand days and unfortunately see lots of young people repeat the same vapid shit that I believed because I was ignorant but convinced it all followed from simplistic crap ideas I was raised with.
> I tended to have very strong opinions about stuff I had barely just learned and didn't have experience to get nuances
I don’t do this; among other differences with y’all in this thread, it’s why I’m not worried about the caution presented here
Yet you wrote:
"...it’s one of my least favorite types of people; and that’s precisely my point, old men have been saying society is collapsing since ancient times, yet here we are, with things better than ever"
Which is a pretty strong opinion. Also, pretty much all societies that ever existed have collapsed. When that happens, life generally sucks and lots of people die. I'm not just talking about ancient Rome or Greece, or Easter Island, or the fall of dozens of different empires, or more recently South Sudan or Haiti.
Other people in thread called you naive. I won't insult you like that but just given the statements here, there's a whole lot of familiar-sounding overconfidence that reminds of things I'd have said in my 20s.
way to prove his point
> they were not right
If you don't think they were at least sometimes right, to what do you instead attribute the various cases of socio-economic collapse documented throughout history?
if I predict a recession every year I’ll be right eventually
I'm not sure that's directly analogous, though. We're talking about people looking at specific cultural trends and making reasoned arguments about specific causes and effects, not just saying "X will happen". Specific models and assumptions about how human societies work are often validated by historical example, and don't just predict end states, but sequences of events that extend over longer terms.
When people say they see history repeating itself, it's worth hearing them out.
I’m saying if every generation has old men screaming “society is collapsing”, they aren’t right, even when they’re locally “right”
(broken clock right twice a day)
I’m all for hearing well-reasoned arguments; presenting pithy quotes as fact is absurd; claiming programming peaked 15 years ago is absurd
> I’m saying if every generation has old men screaming “society is collapsing”, they aren’t right, even when they’re locally “right”
But every generation doesn't have old men screaming "society is collapsing" at the same rate. There's always a baseline of people with a "get off my grass" mentality, but if you factor that out, occurrence of people actually pointing out that the world is on a dangerous path isn't uniform from one era to the next. Very few people, if any, were seriously making such an argument 30 years ago.
People who are genuinely making reasoned arguments, and not just complaining about things being outside their comfort zone, should absolutely be taken seriously.
> claiming programming peaked 15 years ago is absurd
Well, what are you measuring? It certainly peaked in some dimensions 15 years ago. Whether you personally see those dimensions as important is of course a subjective question.
Old man yells at cloud native...
Agreed. If folks want to write java in elipse they are more than welcome to do so... dont understand these yelling at clouds posts really
Only if they found their own companies. Usually those decisions were already made for you.
You know what made javascript so common, accessible, and thus later universal?
Putting things on a screen was (is) stupidly simple.
That's the whole thing. It's not the types or npm or whatever. It's that you could start with C/Python/Java and spend your first 6 months as a coder printing and asking values on a dark terminal (which is something a newbie might not even have interacted with before) or you could go the html/css/javascript route and have animations moving in your screen you can show to your friends on day one.
Everything flows from that human experience. UIs are Electron because creating UIs for a browser is an extremely more universal, easy and creative-friendly experience than creating UIs for native apps, particuarly if JS is your native language for the previously stated reason.
The industry failed to adapt to the fact that the terminal wasn't any longer the reality of computer users, and the web kinda filled that niche by default.
Also, React was an answer to the advent of mobile phones, tablets, smart tvs, and basically all the explosion of not-a-desktop computer form factors. You could no longer assume your html was a proper format for everything. So you need an common API to be consumed by a mobile app, a tv app, a tablet app... react was the way to make the web another of the N apps that use the api, and not get special treatment. The idea made sense in context, back then.
> Putting things on a screen was (is) stupidly simple.
This is why HTML is still a great language for building UIs and that's why Visual Basic had a huge success in the early 90s: drag UI components on a panel, write the callbacks for clicks, save and distribute the exe. Almost anybody could do it.
React and its siblings are much more complicated than that.
It's my belief that we peaked on January 1, 2000. We had successfully released most of the stress baked into the worlds infrastructure with the sudden phase change of "backward compatibility" caused by the IBM 360 series introduction decades earlier.
We had Windows 2000, a server operating system that worked well as a desktop. Both Visual Basic 6 (aka VB6) and Borland Delphi allowed drag and drop GUI application development. Microsoft Office Professional supported most of the features of VB6 while controlling Spreadsheets, Databases, and other documents.
Anyone skilled in a domain other than computing could spend time and put together a reasonably decent application to help with their jobs, and it just worked. You could then call in a professional to clean up edges and make it faster/more reliable if it needed to be scaled.
The documentation was available for pretty much everything, in print, and on screen, with working examples for almost every single function.
It was before the whole .NET distraction, and forcing web pages into everything.
It definitely wasn't perfect... we didn't have widespread version control. No Mercurial or GIT. Mostly, it was numbered PKzip files stored on floppy disks.
We still don't have reliable secure operating systems, I think we've missed that window. Genode was my hope, but it remains a collection of ingredients instead of a daily driver.
It’s so very ironic that your comment appears on this particular post. We had a much better version of this with interface builder on NeXT in the late 1980s (and later Mac OS X). Similar tooling existed for DOS and Windows.
You literally laid out your UI in a WYSIWYG, drag and dropped connections to your code, and had something working on day one.
It was even easier than the web, because what you were laying out were full components with code and UI and behavior. The web still hasn’t caught up with that fully.
When I see comments like these, I better understand why old timers shake their fist at the youngsters reinventing the wheel badly because they don’t understand what came before.
Microsoft broke every single one of those tools. And made their own that would never work in a competing OS.
If you are looking for somebody to shake your fist at, try the market protection agencies all over the world.
>We had a much better version of this with interface builder on NeXT in the late 1980s (and later Mac OS X)
I don’t disagree, that just wasn’t available as a starting to program option when my generation started learning around 2005. If it still existed, it was way too niche for me to know about as a beginner.
And I don’t include myself in the generation that started programming through JS, I went the console route a bit earlier. But I have seen friends enter programming later on and it’s clear why that is the main choice.
Interface Builder was still the standard way to build Mac apps in 2006, and with some improvements, has remained a standard way to build Mac and iOS apps to this day (but now we also have SwiftUI).
Fair, but how common were Macs in 2006 for newcomers?
At least in my corner of the world they were practically non existing. The first time I saw macOS at all was in 2012, and it was on my pc after managing to turn it into a hackintosh with help from some random Eastern European guy from a message board.
It always felt like a huge miss to me that Microsoft didn’t bring Access to the web and/or mobile apps. For all its flaws, it was a simple drag-and-drop editor that almost anyone could use to build simple apps that could power decent-sized businesses.
BASIC made it even easier to put things on a screen. We had commands like this:
In Apple BASIC:
- HPLOT x, y
- HPLOT x1, y1 TO x2, y2
In QuickBASIC on MS-DOS:
- PSET (x, y), color
In contrast I don't find HTML to be "stupidly simple" at all.
> The industry failed to adapt to the fact that the terminal wasn't any longer the reality of computer users
I'm still waiting for some GUI-based terminal to appear
I want to call git in Scratch!
Jupyter notebook UI is essentially a proper GUI-based REPL/terminal.
It's horrifying to see someone who started working 10 years after me talking about "when I was young" :-D
Programming was more exciting when you had amazing things to imagine having - like a 256 colour screen or BASIC that ran as fast as machine code (ACORN ARCHIMEDES) or the incredible thought of having a computer powerful enough to play a video and even having enough storage to hold a whole video!
2400bps! Checking email once a day
Everything came true. My screen has 16million colours and I don't notice. I have 12 cores and 64GB of memory and fibre optic internet. The extremely exciting future arrived. That mind-expanding byte article I read about Object Oriented programming came true enough for us to see that it wasn't the answer to everything.
There are 2 problems now - nothing one does is unique. You can't make a difference because someone else already has done whatever you can think of doing ....and of course AI which is fun to use but threatens to make us even more useless.
I just cannot really get my sense of excitement back - which may just be because I'm old and burned out.
> Checking email once a day
In an ironic twist of life, this is almost what I'm back doing right now. I turned off notifications and pull messages years ago because of all the messages I'm getting for a dozen different systems. I check mail at most a few times per day and that's it. I wouldn't be able to work if I'd have to actively keep an eye on them. I can get away with it because everybody is using Slack for work or WhatsApp for personal life, so there is no urgency to check mail. I'm on Slack too, so I see if I have messages there but WhatsApp is silenced and I allow no notification of any sort on the lock screen of my phone.
It's not just that you're old and burned out. There is a declining marginal value of improvements.
Take sound, for example. Going from "no sound" to "sound" was huge. Going from just beeps to IBM PC sound was a real step. CD-quality was a real step. Going from CD-quality to 64-bit samples at a 1 MHz sample rate is a yawn. Nobody cares. The improvement on CD quality isn't enough to be interesting.
I have high enough bandwidth. Enough screen resolution. Enough RAM, enough CPU speed, good enough languages freely available, enough data.
The problem is, everything that was an easy win with all that has already been done. All that's left is things that aren't all that exciting to do.
(I don't think this is permanent. Something will come along eventually - a new paradigm, a new language, a new kind of data, something - that will open a bunch of doors, and then everything will be interesting again.)
I'm disappointed that you said "2400bps" instead of "2400 baud". :/
It's always surprising to me when I see people being nostalgic for the old days. Yes, things seemed simpler, but it was because there was less you could do.
I'll always fondly remember my attempt to get on GeoLink with a 300 baud modem, and then my parents realizing that the long distance calls made it far, far too expensive to use, and returning it. Sure, I was disappointed at the time, but it wasn't too much later that 56k modems existed and we had a local unlimited internet provider. And now it's a fun story.
But I was actually just as frustrated at the time as I am now, but for different reasons. Change exists, and that's good.
I agree that it feels harder to make your mark today. But I don't think it's actually harder. There's plenty of fun things that people would love to see people do. Just yesterday, I found out about the Strudel musical programming language and watched an amazing video of someone making Trance with it. And those kind of discoveries happen constantly now, where they were pretty seldom back 30 years ago.
We're at the point that anyone can make a game, app, webpage, etc if they put enough effort into it. The tools are so easy and the tutorials are so plentiful and free that it's really just about effort, instead of being blocked from it.
I've been saying "we live in the future" about once a month for years now. It's amazing what we have today.
> Yes, things seemed simpler, but it was because there was less you could do.
And because computing was less mature and a younger field overall. If computers remained stagnant for 500 years, fixed as they were in 1980, I bet that programming would become increasingly more complex, just to enable doing do more with less
From no internet to internet but only at work, to 56k at home, to DSL, to fiber. That's quite a ride in one lifetime.
For me, starting with 1978 hand soldered NASCOM-1 kit (2MHz Z80, 1KB RAM for user, 1KB for display) to my current hand built 10-year old tower with a core i7-5930K processor.
2MHz 8-bit -> 3.5GHz 64-bit multi-core CPU
1KB -> 32GB RAM (a factor of 32 million times more memory !!)
audio casette storage -> 4TB HDD
16x48 char display -> GTX 980 Ti 2560x1600 gfx (+ 6 TFLOPs)
offline -> 9600 baud BBS -> 1Gbps fiber + internet
From hand assembling on paper (or just entering memorized hex opcodes directly into memory) to vibe coding "build me an app to do xxx", or talking to Gemini on my iPhone (would have looked like an alien artifact in 1978) asking it pretty much anything.
What will the next 50 years bring? Will it be as amazing as NASCOM-1 -> iPhone + Gemini? I used to think so, and certainly in 50 years I'd expect full-blown human-level AGI to be here, but will it feel that much different ?
> I'm disappointed that you said "2400bps" instead of "2400 baud". :/
haha :-) It was of course 2400 baud and we were using FidoNET which was very very exciting at that time in Zimbabwe. We'd spend 10 minutes trying to get a dial tone sometimes but it was magic when you connected and saw something was coming in. International telephone calls were so expensive that we talked to my brothers overseas once or twice a month at best. With email we could chat every day if we wanted.
The limitation then was information - no internet, no manuals no documentation. I wrote a text editor and did my best to make it fast with clever schemes but it always flickered. Many years later a pal at university in South Africa casually mentioned that graphics memory was slow so it was actually best to write to memory and then REP MOVSB that to the graphics memory. I cursed out loud at this and asked him how he knew that?! Well, he lived in a more modern country and could buy the right books. Nowadays you really can be a linux kernel programmer in the Congo if you want to.
Thank you for sharing this. I started as a youngling on a 300 baud modem. 1200 baud upgrade modems had a zeitgeist of being just for piracy — who else would need so much bandwidth said those who charged by the minute. Information wasn’t flowing freely and resource-dense countries had advantages to spread it around themselves. Before HTTP and WWW there wasn’t much information architecture existent either.
But what makes me happy to hear is that - on the other side of the planet - random kids were also plugging in a modem, to get connected with each other and press at the edge of the future.
I used to play British Legends on Compuserve at 300 baud and wrote a CNET 5-star software that was a hit worldwide in the late 90s.
Get off my lawn!
And yes, the whole "when I was young" saga starting in ... 2010 ... made me pause too.
> I started my first real, full-time job in 2010. We wrote Java...
I started my first real, full-time job in 1992. Back here we write C, or maybe C++ if we're feeling cutting-edge. The Sparc 10 can get a bit slow when we're all on it, but I have a shelf full of O'Reilly X Windows books to look through if I can't figure something out. My mate in London sent me a QIC tape with something called "gcc" on it: sounds exciting, but before I can install it I have to find a spare day to update SunOS first.
This 2010 programming setup seems pretty amazing tbh... can't wait to get me some of that. Nice languages and tooling, no more having to edit makefiles by hand in emacs or laboriously debug in gdb. Bet they don't even use sourcesafe anymore.
I reckon by 2025 they'll have god-like stuff: fast, reliable hardware with more memory and storage than you can eat; powerful development and collaboration tools; lots of ways to find answers without having to ask that guy over in the other building. And a lot of it will be basically free! I wonder how they'll feel about all that awesome dev power, and whether they'll still use X terminals.
I came here to say something like this.
Programming has evolved several times since the early 90s (when I got in this business) and I had the impression it had already evolved several times by the 90s (especially talking with old mainframe or COBOL programmers).
It's evolving again now, and that process is painful. Nobody knows what the future holds.
> Funnily enough, everything ran at about the same speed as it does now.
Actually, where I was sitting on a decent PC with broadband Internet at the time, everything was much, much faster. I remember seeing a video on here where someone actually booted up a computer from the 2000's and showed how snappy everything was, including Visual Studio, but when I search YouTube for it, it ignores most of my keywords and returns a bunch of "how to speed up your computer" spam. And I can't find it in my bookmarks. Oh well.
> I remember seeing a video on here where someone actually booted up a computer from the 2000's and showed how snappy everything was...
Was this what you were referring to?: https://jmmv.dev/2023/06/fast-machines-slow-machines.html
Notice also how you can clearly see which window is selected, and which item within that window is selected. Microsoft has just lost the plot.
Wow that was a great read, thank you. It's funny that it is already starting to break due to all of the links and ad tracking, which is another kind of rot.
Use Linux/KDE. None of the gains from the switch to SSDs have been lost. Everything is instant even on an n100. You only need something more powerful for compilation, gaming, or heavy multimedia (like the 200 Mbps 4k60 video my camera produces, which isn't accelerated by most processors because it's using 4:2:2 chroma subsampling).
> Use Linux/KDE
I do. It's not without its problems but currently it's the least bad solution.
Xfce or LXQt are also great alternatives, blazing fast even on 15 year-old hardware. Old hardware can be slow for basic web browsing and multimedia (e.g. watching videos with modern codecs) but other low-level uses are absolutely fine.
> "I remember seeing a video on here where someone actually booted up a computer from the 2000's and showed how snappy everything was, including Visual Studio"
Was it this one? Casey Muratori ranting about Visual Studio Debugger slowness, and he shows a video of Visual Studio opening and debugging faster on a single core Pentium 4 from 20 years earlier - https://youtu.be/GC-0tCy4P1U?t=2160
Or this one? Roger Clark developing Notepad in C++ on Windows 2000 and commenting how fast Visual Studio opens: https://youtu.be/Z2b-a4r7hro?t=491
Yeah, that's the one! And hmm, it's interesting that there's more than one video out there going "look how fast old computers were from a user standpoint". They've really been boiling the frog when it comes to terrible UX over the past 20 years.
Given the refinements to the hardware, the modern scale of manufacturing and accessible market, and the sheer amount of engineering manpower a tech company can bring to bear nowadays, you'd think standards would have risen into the stratosphere, but instead the tech consumer is cowed into accepting slow, buggy, abusive, invasive trash.
These days to get a snappy experience, one has to aggressively block everything and only selectively unblock the bare minimum, so that one doesn't get tons of bloat thrown in the direction of one's browser. Oh and forget about running JavaScript, because it _will_ be abused by websites. And then sites have the audacity to claim one is a bot.
Many websites are so shitty, they don't even manage to display static text, without one downloading tons of their JS BS.
The browser is one thing, but even native applications have worse input latency than they did in the 80's and 90's.
https://danluu.com/input-lag/
https://news.ycombinator.com/item?id=25290118
I think the web is not livable anymore without Firefox and uBlock Origin.
I can't recall desktop application times, but I remember using the web in the 00s. Websites took a noticeable blip to load. Pictures took seconds to minutes to load, top to bottom, on my connection. Runescape took an hour to update on dial up.
I do remember applications like Microsoft word's UI constantly freezing though.
YouTube has become enshittified at a record clip. Search is useless and shorts have turned it into just another TikTok brain dopamine machine.
> just another TikTok brain dopamine machine.
You can fight this machine.
You can view shorts on desktop. In a browser on desktop, when you see one on your subscriptions tab (or the front page if you still use that), you can right-click and open in new tab. You can replace "shorts/" with "watch?v=" in the URL and load the same video in the regular UI. You don't have to scroll down.
I've been coding since 40 years old and professioannly since about 30. And let's set this straight: it is much (much, like really much) better nowadays.
We have super powerful editors, powerful languages, a gazillion of libraries ready for download.
I use to write video games and it took months (yeah, months of hobby-time) to put a sprite on a screen.
And for Java, yeah, things have improved so much too: the language of today is better, the tooling is better, the whole security is more complex but better, the JVM keeps rocking...
And now we've got Claude.
I'm really happy to be now.
> I use to write video games and it took months (yeah, months of hobby-time) to put a sprite on a screen.
I'm not sure how that happened - in DOS you could copy things to the framebuffer. There were libraries like Allegro which came with a million features including sound/UI/sprite rendering/animation/effects etc. out of the box.
But anyways copying a sprite to a screen is not hard even if you don't use a single piece of foreign code - you can read in a BMP file and just copy it row-by-row to the screen.
I'm talking about things that were long before DOS even existed.
At that time you didn't even have the tools to cut sprites from image in the first place. That's why it took a lot of time (and I was 12 years old and my dad was pretty far away from an engineer, that didn't help).
were you trying to say you've been coding *for* 40 years? that "old" in "40 years old" confuses me a lot
or are you 60 years of age now, starting at 40 and have been coding long enough to see editors progress?
I'm 53, started at 10. At that time, being able to edit a line of code without re-typing it completely was "cool" :-) Then, on apple 2, we had GPLE (global program line editor) then Assembler toolkit which had an editor. Then I moved to PC. First I used GWBasic (it had an editor) then Turbo Pascal, then multi-edit, then emacs, then Visual Studio, then Eclipse, then Word (became a manager :-)), then back to emacs and VSCode (coding again!) and a bit of Kate.
I'm pretty sure they are not a native English speaker. Many languages use 'since 40 years' to mean what we say as 'for 40 years'.
Or maybe "since <<I was>> 40 years old"?
I think it’s an unfortunate typo…”old” => “ago”?
yeah, typed too fast. I was talking about 40 years ago. Apple 2+ to be specific.
The author is writing like Java was outlawed or something. There are tons of shitty enterprise Java jobs out there for those who want them. Personally, I worked one of those jobs a decade ago, and the article's description of the "golden age" didn't bring back good memories.
It's easy enough to avoid the NPM circus as well. Just don't put JavaScript on your resume and don't get anywhere near frontend development.
Things don't always get worse. Sometimes they get better.
TypeScript recently invited people to try their new compiler which is 7-10x faster. [1]
VS Code is popular, but personally I write TypeScript in Vim, which is definitely faster and less resource-intensive than Eclipse. But thanks to VS Code's invention of the Language Server Protocol and its subsequent adoption in many editors, I can get 'compile the code as you type' functionality. [2]
And then there's runtime speed. Java used to have legendarily slow startup times, and they're still an issue today. JavaScript's modern runtimes are optimized to start fast. On the other hand, Java still holds the crown for throughput, so it's a mixed bag. But if you want even better throughput without sacrificing too much usability, today we have Rust, as well as a vastly improved C++. (Though both of those languages have terrible compile times.)
[1] https://devblogs.microsoft.com/typescript/progress-on-typesc...
[2] To be fair, a memory usage comparison should compare Eclipse not to Vim itself, but to the whole [Vim + coc.nvim + TypeScript compiler] stack, of which most of the memory usage comes from the TypeScript compiler. I'm not sure how that compares to Eclipse. But I'm more concerned about typing latency, where I _do_ only care about Vim itself because all the LSP stuff is asynchronous.
> We also saw the rise of React, which is possibly the greatest tragedy to ever befall front-end programming (and I say this as a recovering React fan).
Amen. Github (just to cite one example) has become much less usable since they switched to React. And it's clearly not a site that needs React, since it worked fine for 17 years without it.
I am still a happy programmer after all these years using only node, express, postgres and sublime. I try not to listen to the sirens singing on the rocky shores...
Postgres and Sublime user here. Life is pretty good!
> Where did it all go wrong?
Just landscape changed significantly comparing to 2010.
Before you didn't have current smartphones and tablets. On desktop you could just support windows only (today probably have to macOS as well). On browser you didn't have to support Safari. You didn't have to worry much about screen DPI, aspect ratio, landscape vs portrait, small screen sizes. Your layout didn't have to be adaptive. There was not much demand for SPA. Back then there was much less people worldwide with access to internet.
Somehow this reminded me of a similar rant about devops:
It’s the Future - https://blog.paulbiggar.com/its-the-future/
And now I see that's from June 2015 -- it's over 10 years old now! Wow
I'm not sure we're really in a better place in the cloud now ... The article says
I’m going back to Heroku
and in 2025, I think people still want that
Maven was a great idea. Introduce a high barrier to entry for publishing packages. Paired with a search box operated by carrier pidgeon, this effectively meant what you were looking for didn't exist. Every time you had any kind of quirky need, you had to write it out by hand, or find someone smarter than you to do it for you, or worst of all buy it from a vendor for lots of money at horrible quality. People recite 'DSA is bad for coding challenges, when will I need to write a hash map', but once upon a time you did have to write a hash map here and there. Supply chain vulnerability is a cost, but the product was worth the cost: you can just import the darn package!
I need a map of key ranges to values with intelligent range merging, it is right there on crates.io to import, it has been there since 2016, Maven Central didn't get one until 2018. In the olden days either it was in Apache Commons or it didn't exist. Halcyon days those.
“ Once our work is done, we create a “pull request”. This is a way of emulating open-source development inside a single company, which as we know, is the only way to work. Typically, this means that the code is downloaded and built on another computer, and then several hours later, a colleague will come along and ask to change a few words. Once we change these words, the computer builds everything again, and then the next day, the same colleague will allow the code to be merged into the mainline.”
Fix this and your life will be much better, generate testable preview apps on every pr, this feedback loop is a velocity killer. Management for some reason never wants to prioritize speeding it up even though it slows down every single project so advise to just do it and not ask permission.
JavaScript is an interpreted language: write, run. No build steps required.
Building was introduced as a temporary measure, to handle cross-browser awkwardness (grunt and stuff like that). People overused it. We totally don't need it anymore. TypeScript is awesome but a major blocker to this return to a more nimbler ecosystem.
People in the 2000s discovered that mixing code with HTML tags was bad and big complexity demon mansion. By the end of the 2000s, this was fixed in the tools of that time. I consider JSX a best-practices regression. It feels like ASP.NET, but the kids don't notice because they have never seen ASP.NET.
For a while, we also saw npm as temporary. A better thing, more web-friendly, would appear. That never happened.
JavaScript could have been great.
Programming was so much better 15 years ago, except for all the parts that sucked.
I just liked programming when it contained a comprehensible amount of abstraction. Stacks have become so tall it is not even feasible for a single human to comprehend what is occurring. I also liked when standards had less surface area. Working in healthcare it has become obvious standards only ever get added, never removed. Complexity is absurd now. I'm not championing that we all become experts in bare metal assembly, but I feel for OP and a desire to at least fundamentally understand what is happening on some level.
> We run our k8s cluster in the “Cloud”. It’s a bunch of services that run on Linux, but we don’t run Linux ourselves, we run it on VMs that we rent by the hour for approximately the same cost as buying a computer outright every month. We do this because no one knows how to plug a computer in any more.
My mind struggles with this reality everyday... the "cloud" has to be the most successful rebrand of all time. In 2005: "Be very careful what data you share on the internet". In 2025: "Yeah, I just put all my shit in the cloud".
[dead]
I get it. I agree with most of this article. But also like, nothing went away.
If you pine for the days of Java and Maven, you can still do that. It’s all still there (Eclipse and NetBeans, too!)
If you don’t like using Node and NPM, that’s totally valid, don’t use them. You can spin up a new mobile app, desktop app, and even a SaaS-style web app without touching NPM. (Even on fancy modern latest-version web frameworks like Hanami or Phoenix)
If you don’t want everyone to use JS and NPM and React without thinking, be the pushback on a project at work, to not start there.
Programming with Rust and deployment and mgmt with Nix is so much better to how things used to be. Did I mention how much better my Helix works than how Neovim used to? Revision control with JJ, conflict resolution with mergiraf. My personal computers are more powerful than ever before and can get amazing stuff done super fast.
Everything is better and keeps getting better if you make good decision instead of following the lowest common denominator tech.
Java is usable now, but in 2013 it was the worst debugging experience one could have. I would rather work with PHP5 than with Java (unless I started a project from scratch). Also auto-refactoring was clearly worse, because well, Java. It was around that time that I tried Scala then Clojure, and even if debugging the JVM was still an experience (to avoid as much as possible), at least limited side effects reduced the issues.
If programming peaked, it certainly wasn't in 2010.
> it was the worst debugging experience one could have.
Hard disagree. I'm not going to argue that Java debugging was the best, however:
1. You could remote debug your code as it ran on the server.
2. You could debug code which wouldn't even compile, as long as your execution path stayed within the clean code.
3. You could then fix a section of the broken code and continue, and the debugger would backtrack and execute the code you just patched in during your debugging session.†
This is what I remember as someone who spent decades (since Java 1.0) working as a contract consultant, mainly on server side Java.
Of course this will not convince anyone who is determined to remain skeptical, but I think those are compelling capabilities.
† Now I code in Rust a lot, and I really enjoy it, but the long compile times and the inability to run broken code are two things which I really miss from those Java days. And often the modern 2025 debugger for it is unable to inspect some for the variables for some reason, a bug which I never encountered with Java.
That's how I felt at the time, it was my first job and I only had better experiences since then (and I gave it a try again in 2019 and the experience was way, way better). You're right, it probably wasn't the worst of the era, it will still be inferior than any experience a dev would have in 2025.
For the 1: not really applicable in my case. For 2: I didn't know this. For 3: yes, but it worked only for a subset of issues, and honestly much more usable with Clojure and Scala.
I primarily worked with Hadoop and ETLs, you probably won't be able to convince me to be fair.
About your †, I think that new Rust tooling like dx will eventually enable hot patching code during debugging
https://lib.rs/crates/subsecond
(Note, it was created by Dioxus, but it's usable in any Rust project)
> 2. You could debug code which wouldn't even compile, as long as your execution path stayed within the clean code.
In Java? How?
Debugging Java is a pleasure compared to debugging assembly and C, using only a terminal.
My first text editor for PHP was Komodo Edit, it was super slow and everyone jump shipped to Sublime Text, then VSCode was slower than Sublime but had incredible industry supported extensions like Git and Prettier, programming didn't peak during my PHP days, in fact the PHP frameworks sites I used are still around and incredibly slow.
I am building an AI coding tool that doesn't eat RAM, there are super lightweight alternatives to Electron.
Well i am a Java developer in 2025 and we still use maven, we also got IntelliJ which is miles better than eclipse and the company where I am does hire testers.
The world is not worse, you just ended up stuck in the wrong tech stack with the wrong company.
I do agree that the JS ecosystem is terrible tho, and i was a full time js dev before (now i only do some frontend from time to time) we already have a dedicated frontend team.
> Funnily enough, everything ran at about the same speed as it does now.
I've often thought about how certain properties of humans impacts the tech we make and accept.
For instance, to a human, something happening in a couple of seconds is quick, and in several seconds is fairly quick. Hence, build steps etc tend to creep up to those sorts of numbers.
MY GOD THIS IS GOLD. Nothing but the truth here.
In this respect I’m liking vibe coding. I can tell it use html css and js only and make me a frontend.
That obviously has severe limitations but ideal if you don’t like the front end framework scene and want to put all your logic in backend. And there I find it a bit easier to navigate
RIP guys in corporate that have things imposed on them
Javascript wins by keeping the costs down. Companies today want to do more with less, which is how it should be and you are still free to choose from a myriad of technologies. When you pair this setup with LLMs, it's actually the best it has ever been IMO.
If the author doesn't want to work with NPM and the JavaScript ecosystem he could just get a job writing Spring/Boot, which makes up probably 90% of the jobs at large enterprise companies. I don't agree that this world has disappeared...
Defining peak programming as entreprise Java using Eclipse on SVN is border delusionnal imo.
> And here’s the funny thing: it never broke, because the person who built it did it well, because it wasn’t taxed within an inch of its life, and because we were keeping an eye on it.
Sure, if you say so buddy...
I think I’m lucky, because for me it’s the other way. In 2009 I started my first real programming job writing c++ in vim. For the last 5 years I’ve been writing rust in helix and things have never been better.
> I love writing JavaScript, and I’m glad I can run it on the server. But this doesn’t mean I think it’s a good idea to use it for everything.
"Javascript" programming peaked.
Programming used to be about finding the best way to communicate with the device. Now the device is trying to figure out the best way to communicate with you.
Now it’s about how the device can be programmed to spy and manipulate you so the company can extract more value for the shareholders.
I meant, it used to be more low level, less abstracted. A long time ago.
A promo for you, short-term gains for the shareholders, and enshittification for the customer.
In other words you have competitive advantage because your cloud costs will be 10x less.
This is exactly what 10 years of experience did for you. Why complain?
There's something to this. I recently shipped a music curation site and deliberately avoided React/Next/etc - just HTML, CSS, vanilla JS. The cognitive load difference is stark. The 'peak' might be less about capability and more about us rediscovering that simpler tools often suffice.
Same. I build stuff for local businesses in my area with nothing but boring old HTML, PHP, CSS and JS. I guess my shit isn't "web scale" but it works, and it works consistently, with minimal downtime, and it worked during both Amazon and Cloudflare's latest outages.
I don't need my software to eat the world, I'm perfectly content with it just solving someone's problems.
It's all about picking the right tools for the job. The "cognitive load" might be larger in a vanilla project compared to React when your interface is more complex and interactive.
It's incredible how different the programming in 2025 can be if you work in a different kind of company.
When I started programming we wrote code on a C64 in a freezing cold basement, with no disk drive. And we liked it...
Honestly, the person should spend their time of fixing their shit instead of writing blog posts.
I find intellij a great IDE, modern frameworks are fun to use, ai helps me doing things i don't want to do or things i just need (like generate a good README.md for the other people).
Containers are great and mine build fast.
My Startup has a ha setup with self healing tx to k8s and everything is in code so i don't need to worry to backup some random config files.
Hardware has never been that cheap. NVMs, RAM and Compute. A modern laptop today has a brilliant display, quite, can run everything, long batterytime.
Traffic? No brainer.
Websphere was a monster with shitty features. I remember when finally all the JEE Servers had a startup time of just a few seconds instead of minutes. RAM got finally cheap enough that you were able to run eclipse, webserver etc. locally.
Java was verbose, a lot more verbose than today.
JQuery was everywere.
Ew
truthnuke
> The most popular is “VS Code”, which needs only a few gigabytes of RAM to render the text.
> We used Eclipse, which was a bit like VS Code.
This made me laugh. You can't possibly be a serious person if you think Eclipse was better in any way shape or form than VS Code.
I don't have a great memory, but one thing I can absolutely still remember with 100% clarity is how bloated and memory hungry Eclipse was. It was almost unusable.
Some of us are still out here, writing maven projects in Java with Eclipse. It works great.
Me, a young, but old fart at heart, writing firmware in C and applications in C++ (just for Qt!) that see everything wrong with the programming world today VS the junior that keep asking why we don't do the thing in javascript so we can have it on mobile as well (we do, we just use a different framework 'cause react won't ever cut it for our needs. It just takes a bit of what is called "effort" to make things look the same on all platforms) and wants emails lists to plan going out for a drink instead of, you know, asking. We're all in the same small office. Same stuff about deploying, we need github (no we don't. private git server), we need aws, woah what is this npm attack you're talking about?
At times it seems he's learning, but then he leans back into GPT and it feels like a lost cause. Yo bro it's crazy, i just deleted 2k lines of code, as if it was normal, with me raising eyebrows asking how many modules were outright deleted and never needed to be there in the first place.
Problem is, GPT and company will happily throw a lot of puke at the project and trust me bro that's essential we plan every single possible feature first and foremost instead of just testing the basics and build on top of them, because we have literally two requirements, so it's taking two months to do something i could do in two weeks, not because i'm more experienced, but because we should be doing what i'm telling to do, and not discuss whatever bullcrap the artificial manager is suggesting, which i would love to have the power to outright ban from our network.
Me and the junior have more or less the same age, just very different life journeys that led to programming
So js was great when jquery was the dominant library...?
how tedious must a life be if you go through it with this kind of thinking
the idea of moving from TS back to Java fills me with dread
this is going straight into my funny folder
strawman dystopia. simply choose to continue applying wise practices of old. be the effect you wish to see in the world. just because others are jumping off a cliff like lemmings does not mean you must as well
I don't do any of that shit in the first section.
Wait until he discovers vercel and nextjs.
these tools are so useless these days. All you need is Claude and esbuild, and you can make practically anything.
I'm enjoying some things about the programming world now, especially compared to my professional start circa 1997.
I started on C++ on Windows, using MFC, and also using Visual Basic 5.0 when it came out. VB made my eyes bleed, but a lot of people are nostalgic about it. Visual C++ did not have many fans, but it had a lot of users. I got the first taste of the Microsoft treadmill during those days, where they would get you to use a new thing, and then in a few months they hardly used it anymore, and they were promoting the next new thing. As soon as you got comfortable with MFC, they were pushing ATL, and then .NET, etc. Really, the people who were happy with what they had and never upgraded were better off.
I narrowly missed the big-manual days of programming, where it was unlikely you had online resources to help you through it. The Turbo Pascal folks and the early Mac folks remember that well. Instead, we had the big online help file (CHM) and search engines like Altavista. Code examples were few and far between. We often spent a lot of time just figuring out how to make the right incantations to get things to do what we wanted. There was a happy path, like with MFC if you make the same exact application over and over again. And then there is the difficult path, where you want it to be a little innovative.
I came across Squeak Smalltalk and used that a lot for my own personal exploration, so I always felt like there was something missing from the world that actually came to be. Still, working alone on Squeak is only as fun as long as you don't get bored and don't need something that Squeak was too slow to handle.
Like the author, I was into pair programming (eXtreme programming, actually). I never understood its detractors. Working was pretty fun.
I never liked the MS ecosystem so I enthusiastically accepted Java. IBM offered a lot of support for Linux and there were good applications waiting to be written. It had its growing pains but quickly settled in to being very productive. In this period, Intellisense and similar technologies were becoming commonplace and the Refactoring Browser had been developed (for Smalltalk but then basically for Java). IntelliJ IDEA was released and was, honestly, revolutionary. The previous IDEs were just not serious until they caught up with the developer support in IDEA.
I figured out that being a professional programmer is not for me, because I don't enjoy working on projects, and I went back to school, eventually becoming a veterinarian. So my professional career kind of ends there.
I enjoy programming, but as a casual programmer it is hard to work on something and come back to it every few months. Things do seem to rot. What compiled before doesn't now. Library use changes radically. If you started a React project before hooks, you know what I mean. Sure, you can still do it without hooks, but nobody does so you're on your own.
What AI does is it makes exploration and problem solving, as well as understanding what I did a few months ago so much easier. I don't have anyone to pair-program with. But the AI makes it easier to be the programmer who's not in the driver seat. I like that, and I think it could lead to good things in the field. The big risk is that LLMs are not very good at future things. If things are out of their training window, they make lots of annoying mistakes. For example, Debian Bookworm and Debian Trixie are somewhat different, and Claude doesn't know what it's doing yet with Trixie. Claude thinks the most recent version of Python is 3.11 or something. With LLMs you have to be comfortable working on yesterday's code. But for most of us, that's OK.
old man yells at cloud
This feels very much like the tired "the modern internet sucks - the old web with old websites was better!" trope that appears on here regularly.
You can still code the old way just like you can still put up your old website. No one is forcing you to use AI or VS Code or even JavaScript.
Of course you.might not getting those choices at work, but that is entirely different since your paid to do a job that benefits your employer, not paid to do something you enjoy.
Have fun.