[burnstek]

50 here. Years ago I completely stopped coding, becoming tired of the never ending rat race of keeping up with the latest bizarre web stacks, frameworks for everything, node for this, npm for that, Angular, React, Vue, whatever - as if solving business problems just became too boring for software developers, so we decided to spend our cycles on the new hotness at every turn.

Tools like Claude Code are the ultimate cheat code for me and have breathed new life into my desire to create. I know more than enough about architecture and coding to understand the plumbing and effectively debug, yet I don't have to know or care about implementation details. It's almost an unfair unlock.

It'll also be good to see leetcode die.

[kitd]

Tools like Claude Code are the ultimate cheat code for me and have breathed new life into my desire to create

I'm in my 60s and retiring this summer. I feel the opposite. Agents have removed most of the satisfaction and fulfilment from designing, building, testing and completing a feature or component. And if frameworks are a problem, learning to create simply and efficiently without them has its own sense of satisfaction.

Maybe it's a question of expectations. I suspect weavers felt the same with the arrival of mechanised looms in the industrial revolution. And it may be that future coders learn to get their fulfilment otherwise using agents.

I can absolutely see the attraction to business of agents and they may well make projects viable that weren't previously. But for this Luddite, they have removed the joy.

[LogicFailsMe]

OldAF. I have more ideas than I have time to code up prototypes. Claude code has changed all that, And given it cannot improve the performance of optimized code I've written so far, it's like having a never tiring eager junior engineer to work out how to make use of frameworks and APIs to deploy my code.

A year ago, cursor was flummoxed by simple things Claude code navigates with ease. But there are still corner cases where it hallucinates on the strangest seemingly obvious things. I'm working on getting it to write code to make what's going on in front of its face more visible to it currently.

I guess it's a question of where you find joy in life. I find no joy in frameworks and APIs. I find it entirely in doing the impossible out of sample things for which these agents are not competitive yet.

I will even say IMO AI coding agents are the coolest thing I've seen since I saw the first cut of cuda 20 years ago. And I expect the same level of belligerence and resistance to it that I saw deployed against cuda. People hate change by and large.

[Bewelge]

Can you elaborate on "resistance against cuda"? What were people clinging to instead?

[MachineBurning]

IMO it was mostly that people didn't want to rewrite (and maintain) their code for a new proprietary programming model they were unfamiliar with. People also didn't want to invest in hardware that could only run code written in CUDA.

Lots of people wanted (and Intel tried to sell, somewhat succesfully) something they could just plug-and-play and just run the parallel implementations they'd already written for supercomputes using x86. It seemed easier. Why invest all of this effort into CUDA when Intel are going to come and make your current code work just as fast as this strange CUDA stuff in a year or two.

Deep learning is quite different from the earlier uses of CUDA. Those use cases were often massive, often old, FORTRAN programs where to get things running well you had to write many separate kernels targeting each bit. And it all had to be on there to avoid expensive copies between GPU and CPU, and early CUDA was a lot less programmable than it is now, with huge performance penalties for relatively small "mistakes". Also many of your key contributers are scientists rather than profressional programmers who see programming as getting in the way of doing what they acutally want to do. They don't want to spend time completely rewriting their applications and optimizing CUDA kernels, they want to keep on with their incremental modifications to existing codebases.

Then deep learning came along and researchers were already using frameworks (Lua Torch, Caffe, Theano). The framework authors only had to support the few operations required to get Convnets working very fast on GPUs, and it was minimal effort for researchers to run. It grew a lot from there, but going from "nothing" to "most people can run their Convnet research" on GPUs was much eaiser for these frameworks than it was for any large traditional HPC scientific application.

[Bewelge]

Thanks!

It seems funny though: The advantages of GPGPU are so obvious and unambiguous compared to AI. But then again, with every new technology you probably also had management pushing to use technology_a for <enter something inappropriate for technology_a>.

Like in a few decades when the way we work with AI has matured and become completely normal it might be hard to imagine why people nowadays questioned its use. But they won't know about the million stupid uses of AI we're confronted with every day :)

[alsetmusic]

> The advantages of GPGPU are so obvious and unambiguous

I remember being a bit surprised when I started reading about GPUs being tasked with processes that weren't what we'd previously understood to be their role (way before I heard of CUDA). For some reason that I don't recall, I was thinking about that moment in tech just the other day.

It wasn't always obvious that the earth rotated around the sun. Or that using a mouse would be a standard for computing. Knowledge is built. We're pretty lucky to stand atop the giants who came before us.

I didn't know about CUDA until however many years ago. Definitely didn't know how early it began. Definitely didn't know there was pushback when it was introduced. Interesting stuff.

[LogicFailsMe]

I'm dealing with someone in 2026 insisting that everything has to be written in Python and rely on entirely torch.compile for acceleration rather than any bespoke GPU kernels. Times change, people don't.

[LogicFailsMe]

The completely low information and amateur hour aspect of what our HPC Welfare Queens were pushing above was that a couple hours invested into coding Intel's Xeon Phi alternative to GPUs demonstrated the folly of their BS "recompile and run" strategy and any attempt to code the thing exposed how much better a design CUDA was than their series of APIs of The Month that followed*. And I was all but blacklisted by the HPC community over standing up to this and insisting on CUDA or I walk, my favorite quote was "You lack vision and you probably wouldn't have backed the Apollo program or Lewis and Clark." Good times, good times...

*But TBF Xeon Phi was not a complete disaster for if you coded it in assembler you could squeeze out Fermi class GPU performance. Good luck getting the "recompile and run" crowd to do that though as they segued from that to relying on compiler directives going forward and that's how NVDA got a decade+ headstart that should never have happened, but did. Today a lot of these sorts are insisting that because of autograd, everything should be written in Python and compiled with an autograd DSL like torch. I am so glad I am close to retirement on that front. I already trust coding agents more than I trust this mindset.

[actionfromafar]

Phi was cool, I think it could have been leveraged into something great. Imagine all consumer CPUs coming with 512 little pentiums in them or something like that.

[LogicFailsMe]

In the beginning, valid claims of 100x to 1,000x for genuine workloads due to HW level advances enabled by CUDA were denied stating that this ignored CPU and memory copy overhead, or it was only being measure relative to single core code etc. No amount of evidence to the contrary was sufficient for a lot of people who should have known better. And even if they believed the speedups, they were the same ones saying Intel would destroy them with their roadmap. I was there. I rolled my eyes every single time but then AI happened and most of them (but not all of them) denied ever spouting such gibberish.

Won't name names anymore, it really doesn't matter. But I feel the same way about people still characterizing LLMs as stochastic parrots and glorified autocomplete as I feel about certain CPU luminaries (won't name names) continuing to state that GPUs are bad because they were designed for gaming. Neither sorts are keeping up with how fast things change.

[ACCount37]

The divide seems to come down to: do you enjoy the "micro" of getting bits of code to work and fit together neatly, or the "macro" of building systems that work?

If it's the former, you hate AI agents. If it's the latter, you love AI agents.

[ThrowawayR2]

I'd say that the divide seems to come down to whether you want to be a manager or a hacker. Skimming the posts in this submission, many of the most enamored with LLMs seem to be project managers, people managers, principal+ engineers who don't code much anymore, and other not hands-on people who are less concerned with quality or technical elegance than getting some kind of result.

Bear in mind also that the inputs to train LLMs on future languages and frameworks necessarily have to come from the hacker types. Somebody has to get their hands dirty, the "micro" of the parent post, to write a high quality corpus of code in the new tech so that LLMs have a basis to work from to emit their results.

[Difwif]

I think it's pretty obvious what category you see yourself in.

I don't think you're a hacker. I think you enjoy writing code (good for you). Some of us just enjoy making the computer execute our ideas - like a digital magician. I've also gotten very good at the code writing and debugging part. I've even enjoyed it for long periods of time but there's times where I can't execute my ideas because they're bigger than what I can reasonably do by myself. Then my job becomes pitching, hiring, and managing humans. Now I write code to write code and no project seems too big.

But I'm looking forward to collapsing the many layers of abstraction we've created to move bits and control devices. It was always about what we could do with the computers for me.

[theshrike79]

I want to "hack" at a different level.

What I want to do is create bespoke components that I can use to create a larger solution to solve a problem I have.

What I don't want to do is spend 45 minutes wrangling JSON to a struct so that I can get the damn component working =)

A quick example: I wanted a component that could see if I have new replies on HN using the Algol API. ~10 minutes of wall clock time with Claude, maybe a minute of my time. Just reading through the API spec is 15 minutes. Not my idea of fun.

[raw_anon_1111]

“Technical excellence” has never been about whether you are using a for loop or while loop. It’s architecture, whether you are solving the right problem, scalability, etc

[guitarlimeo]

Performance critical applications (game engines etc) don't agree with that

[raw_anon_1111]

Most people aren’t writing game engines. Hell most people at BigTech aren’t worried about scalability. They are building on top of scalable internal frameworks - not code frameworks things like Google Borg.

The reason your login is slow is not because someone didn’t use the right algorithm.

Most game developers are just using other company’s engines.

While yes you need to learn how the architecture, the code isn’t the gating factor.

One example is the Amazon Prime Video team using AWS Step functions when they shouldn’t have and it led to inefficiencies. This was a public article that I can’t find right now.

(And before someone from Amazon Retail chimes in and says much of Amazon Retail doesn’t run on AWS and uses the legacy CDO infrastructure - yes I know. I am a former AWS employee).

[kubanczyk]

> do you enjoy the "micro" of getting bits of code to work and fit together neatly, or the "macro" of building systems that work?

These are not toys. I want to make money. The customers want feature after feature, in a steady stream. It's bad business if the third or fourth feature takes ages. The longer stream, the better financially.

That the code "works" on any level is elementary, Watson, what must "work" is that stream of new features/pivots/redesigns/fixes flowing.

[kristofferR]

That is an amazing summary. It might not seem that amazing, but I feel like I've read pages about this, but nothing has expressed as elegantly and succinctly.

[arcanemachiner]

I do love the former, but it's been nice to take a break from that and work at a higher level of abstraction.

[nineteen999]

Same. After 40+ years of typing code on a keyboard, my hands aren't as nimble as they were, a little pain sometimes builds up (whether it's arthritis or carpal tunnel or something, I'm not sure). Being able to have large amounts of code written with much less input is a godsend - and it's been great to learn and see what models like Claude can really do, if you can remain organized and focussed on the API's/interfaces.

[fragmede]

Do you have WisprFlow or similar STT setup? It's a real Star Trek moment vocally telling my computer what to build, and then to have it build it.

[nineteen999]

I tried WisprFlow after you mentioned it and after spending ages clicking through all the dialogs only to find it didn't work out of the box with my terminal (I use Claude cli almost exclusively). Could have been something wrong with my terminal I guess, since I wrote my own.

[teaearlgraycold]

I enjoy both. There’s still plenty of micro to do even in web dev if you have high standards. Read Claude’s output and you’ll find issues. Code organization, style, edge cases, etc.

But the important thing is getting solutions to users. Claude makes that easier.

[0x20cowboy]

Maybe have a play with them a bit more. LLMs are quite good at coding, but terrible at software engineering. You hear people talk about “guiding them” which is what I think they are getting at. You still need to know what you are doing or you’ll just drive off a cliff eventually.

At the moment I am trying to fix a vibe coded application and while each individual function is ok, the overall application is a dog’s breakfast of spaghetti which is causing many problems.

If you derive all your pleasure from actually typing the code then you’re probably toast, but if you like building whole systems (that run on production infrastructure) there is still heaps of work to do.

[bGl2YW5j]

I very much agree! It feels like it's going to be exceptionally challenging in the coming years to convince non-technical people of the value of true SWE; by that I mean, SWE is not just coding, it's everything around that too.

[cheema33]

I am in my 50s. I agree with what others have said about your happy place. For me, it is not APIs and fine details of operator overloading. I love solving problems. So much so that I hope I never retire. Tools like Claude Code give me wings.

The need for assembly programmers diminished over the decades. A similar thing will happen here.

[fragmede]

Or retire and realize the beach forever is not your version of retirement, and get back to it. I spent a week in the Philippines on the beach before getting bored of that and pulling out a laptop and digging into some Linux thing with Claude code, and then now I'm torn between which app to work on to launch.

[zmmmmm]

> Agents have removed most of the satisfaction and fulfilment from designing, building, testing and completing a feature or component

I highly recommend not using these tools in their "agentic" modes. Stay in control. Tell them exactly what to write, direct the architecture explicitly.

You still get the tremendous benefit of being unlocked from learning tedious syntax and overcoming arcane infra bottlenecks that suck the joy out of the process for me, but you get freed from the tedious and soul crushing parts.

[fragmede]

But then you don't get the same gains in output that agentic modes get you. It just goes off and does stuff, sometimes for hours if you get the loop tuned right.

Obviously you should do whatever you want, however you want to do it, and not just do whatever some Internet rando tells you to do, but glorified autocomplete is so 1 year ago. Everyone knows the $20/month plans aren't going to last, time will tell if the $100/month ones do. The satisfaction is now in completing a component and getting to polish it in a way you never had time for before. And then totally crushing the next one in record time. To each their own, of course, but personally, what's been lost with agentic mode has been replaced by quantity and quality.

[zmmmmm]

Yes I'm not recommending "glorified autocomplete". Just shortening the cycle. Give it tasks that would involve maybe a couple of hundred lines of code at a time. I find this captures both the rewarding aspects and gets a lot of the productivity gain - and I'll argue a lot of the remainder of that "productivity gain" sits in somewhat debatable territory : how well all this code holds up that has been developed without oversight is going to be something we only really find out in a few years.

[schnitsel]

You will maybe like this platform: https://solve.it.com/

Their tag line: "Don't outsource your thinking to AI. Instead, use AI to become a better problem solver, clearer thinker, and more elegant coder."

I have followed the course myself and it reignited my passion. During the course I built a cool side project from scratch, small steps, no vibe coding using the course's principals. It was really satisfying, I felt in control again while learning new things.

[darkwater]

> I'm in my 60s and retiring this summer.

Congrats! I'm in that age where I'm envying more the ones like you than the 20-something :)

[chamomeal]

I’m kinda in both camps. I can make multiple times more proof-of-concepts than ever before, which is awesome. Especially for internal work tools. But then I rely on it too much, and I don’t really know how the thing works, and it makes it hard to get excited about adding to it

[monkey26]

50s here. I love building and designing software to solve problems. For years now I haven’t liked the actual coding part. AI has given me a super power.

[tech_tuna]

I have mixed feelings but echo your sentiments a bit. On the one hand, I can get a lot more done and feel "unchained" so to speak. I have long hated doing frontend development and now it doesn't matter and I love that. However, I don't feel satisfaction from solving problems the same way I used to. I had one long session with Claude a few weeks ago and I told Claude I was done for the night at which point it fired back with "Sounds good, look at how much you accomplished." and I responded with you mean "look at how much you accomplished, I just told you what to do."

It is still weird to me that I talk to a remote Python app but that's how we write code nowadays. Still, I felt almost mocked when Claude plauded my "accomplishments".

So I'd say that I am definitely more productive than I used to be but I enjoy the work less on one level. But on another level, I feel like I can build a lot more and tackle problems I wouldn't have tackled in the past. It's a mixed blessing. It's also a WIP, I expect that the way we write code will change even more, over the next few years.

I love it, I hate it, it's the Brave New World of software development.

[throwaway12345t]

Scale the Lego pieces more and it’s the same. Bigger projects have more moving parts and require the same thinking.

[boringg]

Id agree it splits both ways. I think in the short run it can be super fun but once you expand your thoughts to the long run it takes the steam out of rediscovered joy of discovery and creation.

Its almost like it reignites novelty at things that were to administratively heavy to figure out. Im not sure if its fleeting or lasting.

[bartread]

Same age, same situation.

I got completely fed up of continually having to learn new incantations to do the same shit I’ve been doing for decades without enough of a value add on top. I know what I want to build, and I know how to architect and structure it, but it’s simply not a good investment of my increasingly limited time to learn the umpteenth way to type code in simply to display text, data, and images on the web - especially when I know that knowledge will be useful for maybe, if I’m lucky, a handful of years before I have to relearn it again for some other opinionated framework.

It’s just not interesting and I’ve become increasingly resentful of and uninterested in wasting time on it.

Claude, on the other hand, is a massive force multiplier that enables me to focus on the parts of software development I do enjoy: solving the problems without the bother of having to type it all in (like, in days of old, I’d already solved the problem before my fingers touched the keyboard but the time-consuming bit was always typing it all in, testing and debugging - all of that is now faster but especially the typing part), focussing on use cases and user experience.

And I don’t ever have to deal directly with CSS or Tailwind: I simply describe the way I want things to look and that’s how the end up looking.

It’s - so far at any rate - the ultimate in declarative programming. It’s awesome, and it means I can really focus on the quality of the solution, which I’m a big fan of.

[SoftTalker]

Will be 60 this year, and have felt the same for years already. You get to a point where you look ahead and realize you've got maybe another 10-20 decent years left if you're lucky and for me, more and more, I don't want to spend it running on this treadmill.

Computers do not feature at all in my ideal retirement. Maybe a phone or tablet so I can do the minimal email and bill paying.

[burnstek]

Yeah dude. Amen. In my 20's I could literally code a side project all day into the evening (sometimes overnight) and it was absolute serendipity. Coding in and of itself was a vibe. Then, life happened, more life happened, and eventually software development just became a career instead of a passion. Coding became a means to an end.

"Resentful" is a perfect way of putting it - I may just be old and grumpy now, but I think it's sad what we as a community have done to the process of web development. It's such a circle jerk. Node in my view is the worst thing that ever happened to building web applications.

Enter Claude Cowork. I've spent the past few days building an app that would have taken me weeks of time in the past. It's using a framework I've never built with, and I don't have to learn the intricacies. Shipping this to Vercel and hosting the database on Supabase is incredibly easy and it's very exciting. The only drawback so far is the unsettling fear of the unknown regarding leaking secrets and whatnot, so I'm going to have to manually audit the finished project before deploying.

And here I thought my days of "side projects" were completely over.

[suzzer99]

I'm 56 and still coding full-time. My least favorite part of the job has always been trying to learn some brand new tech, googling with 47 tabs open, and you don't even know enough to ask the right questions yet. Turns out you were stuck on something so beginner that Stack Overflow didn't even have a post on it. ChatGPT has made that part of the job soooooo much less painful. But I'm not ready to let Claude run wild yet. I still want to understand everything I'm pasting.

[YZF]

There is a lot more Claude Code can do for you that an AI chat bot can't because it a) has tool access b) has access to your source code.

- Root cause and fix failures.

- Run any code "what if scenario".

- Performance optimizations.

- Refactor.

There's no reason why you shouldn't (and you should) read all the code and understand it after Claude does any work for you but the experience vs. the "old" SO model of looking for some technical detail is very different.

[matsemann]

You know you could just choose a framework and stick with it? The way you look down on "the whole profession" for what's basically a straw man and your own decision is a bit bizarre. Especially coupled with the fact that tech has never moved so fast as right now, being on top of the AI-game is a target changing a hundred times faster than frontend frameworks back in the days.

[fragmede]

You could, but then you'd still be stuck doing PHP templates with embedded hand written JavaScript and that madness, or maybe Django or RoR. Or cgi-bin and Perl. Technology evolves as an industry and the only guarantee is that you have to keep learning new things to stay relevant in this industry.

[Cpoll]

You don't always have the option. AngularJS, for example, EOLed in 2021.

[NewsaHackO]

It is a huge stretch to call transitioning from angularjs to angular learning a new framework.

[taejavu]

At the time that’s precisely how it felt though. So much so that I personally felt it wasn’t worth it relearning everything. Had shipped several projects with AngularJS at my very first dev job, and have never written a line of Angular v2+

[kzzzznot]

It confuses me when people talk about frameworks as being totally different. They solve the same problems, slightly differently. It’s not a big lift to learn a new one if you are familiar with one or two already.

[taejavu]

That might be generally true for frontend frameworks these days, because they’ve all converged around the same ideas. But in the mid 2010s, Backbone was very different from jQuery, which was very different from Knockout, Ember, ReactJS etc. certain frameworks embraced certain programming paradigms, others embraced others.

Some of my colleagues didn’t make the jump. Those that were the most into AngularJS back then are still writing Angular apps today.

[alsetmusic]

> You know you could just choose a framework and stick with it? The way you look down on "the whole profession" for what's basically a straw man and your own decision is a bit bizarre.

I'm only in my forties. I've been nostalgic for the days when I'd stay up all night exploring new frontiers (for me) in tech for a number of years. I could not disagree more with your take on this.

Someone said they value their time before death and you're pretty dismissive. Priorities change. Values change. Conditions change.

> Especially coupled with the fact that tech has never moved so fast as right now, being on top of the AI-game is a target changing a hundred times faster than frontend frameworks back in the days.

I mean, isn't that what people in this thread have been saying about frameworks? How many hours have been lost relearning how to solve a problem that has already been solved? It's like when I tried to fix a date-time issue on Windows as a Mac / Linux user. I knew NTP was the answer but I had to search the web to find out where to turn it on. Stuff like that is pretty frustrating and I didn't even have to do it every five to ten years.

[raw_anon_1111]

Yes if I actually did web development I’m sure I could still be using JQuery.

[switchbak]

“yet I don't have to know or care about implementation details”

Implementation details can very much matter though. I see this attitude from my managers that now submit huge PRs, and it is becoming a big problem.

I definitely agree that these tools allow one with an in-depth developer background to cover territory that was too much work previously. But plop me into a Haskell codebase, and I guarantee I’d cause all kinds of problems even with the best intentions and newest models. But the ramp up for learning these things has collapsed dramatically, and that’s very cool.

I still don’t want to have to learn all the pitfalls of those frameworks though. Hopefully we will converge on a smaller number, even if it’s on tooling that isn’t my favourite.

[waffletower]

Merges can become more fraught with multiple engineers vibe coding on the same codebase. However, LLMs will become delegates for that too.

[switchbak]

Conflicts are the least of our worries, and yes llms can handle that well. I’m taking about the things you can’t easily handle, the complexity that slowly overwhelms a codebase with no easy way out except a rewrite.

And a rewrite of a non-trivial application, even with the AI goodness, is still a big proposition and full of all kinds of risk. If you have a trivial application, you probably don’t have much protecting you from someone else vibing up a competing replacement either.

[jitbit]

Turning 50 this year.

Coding has never _stopped_ being a passion for me, but my increasingly limited time becomes an issue.

And Claude code (and cursor) saves me So. Much. Time.

I only have 10-20 active years ahead of me, so this is really, really important. Young ppl don’t get it.

[corysama]

Same same. When I was a young, single nerd I would happily spend a weekend coding in my cave.

Now I do fun code on a laptop on the sofa with my family. I’m only typing in tiny breaks between socializing and I’m still getting lots of fun stuff done.

[jitbit]

Exactly brother, mind if I hug you.

I can play with my 7yo, or help the 11yo with his homework, or go for a run!! - while LLM is cooking a well-spec'ed agentic task. This sounds embarrassing, but LLMs have made our lives healthier, unbelievable.

PS. Not to mention all the "boring" sh*t that I used to postpone/stretch indefinitely, like writng docs or polishing copy for my website... No more stress, no procrastination, just let the LLM do it.

[theshrike79]

I've had ideas while walking with the dogs, whipped out Claude on my phone, switched to my "research" -repo (shoutout @simonw) and told it to test if the idea is viable

Phone goes back in my pocket and I'll have something to read when I get back home. Literal game changer.

Before those ideas just flowed through my brain and either out the other ear or got filed into "don't have time anyway shrug" and never completed or even tried.

[mlrtime]

>I only have 10-20 active years ahead of me, so this is really, really important. Young ppl don’t get it.

10-20 years of coding/technology or living?

Young ppl rarely get life experience/choices, youth is wasted on the young, 1000x for my own.

[game_the0ry]

> It'll also be good to see leetcode die.

Agreed. Leetcode caused more harm than good.

[chrisweekly]

Still causing it!

[newsoftheday]

> yet I don't have to know or care about implementation details

Where do I even begin...yes, you should care about implementation details unless you're only going to write stuff you run locally for your own amusement.

[aklein]

until you learn to trust the system and free mental capacity for more useful thinking. at some point compilers became better at assembly instructions than humans. seems inevitable this will happen here. caring about the details and knowing the details are two different things.

[leptons]

LLMs lie constantly. There should be no trust in that system. And no I don't think they will "get better".

[theshrike79]

How do they "lie constantly"? We are specifically talking about code here, not LLMs writing legal documents.

[leptons]

I've had the LLM "lie" to me about the code it wrote many times. But "lie" and "hallucinate" are incorrect anthropomorphisms commonly used to describe LLM output. The more appropriate term would be garbage.

[theshrike79]

Just a basic sanity check: did the LLM have the tools to check its output for lies, hallucinations and garbage? Could it compile, run tests, linters etc and still managed to produce something that doesn't work?

[newsoftheday]

Compilers are deterministic tools. AI is not deterministic. It will tell you this if you ask it. AI then, is not a tool. It is an aide. It is not a tool like a compiler, IDE, editor, etc.

[rileymat2]

> Angular, React, Vue, whatever - as if solving business problems just became too boring for software developers, so we decided to spend our cycles on the new hotness at every turn.

They often do solve business problems around responsive design, security and ux.

Currently working maintenance with one foot in a real legacy system and the other foot in modern systems the difference is immense.

[sean2]

Youthful 40 here, had to comment on this:

>> tired of the never ending rat race of keeping up with the latest bizarre web stacks, frameworks

Instead of just keeping up with the latest development frameworks, I also now have to keep up with the latest AI frameworks. I spent a week at my $ job just installing plugins, requesting permissions, debugging issues with the agents, before I went back to writing code myself (plumbing between the latest frameworks) because I'm expected to get stuff done in addition to managing agents that were supposedly going to do my work for me.

My personal agentic AI coding setup never fully materialized while I have been chasing the latest crazes and I am back to handwriting my personal code too (with AI chat help) until I manage to stick to a particular setup.

Anyway, I feel like the rat race just opened yet another front. And I bet I'll still be expected to leetcode in my next technical interview (still was in 2025) in addition to leetprompting or whatever the next segment on interviews will be.

[ransom1538]

You truly speak for many. I don't have the energy to center a div anymore, and to be honest, that time was thrown away [excluding money, a pretty big exclusion]. I am sure my boss's "Uber for cats" will work, I just like using AI at this point. I can iterate on 15 "Uber for cats" with 200 centered divs, spitting out documentation and excellent objects all day.

But the real talk we need to have is... "Uber for cats"

[Frost1x]

Not nearly your age but I agree with your sentiments entirely. I mainly focused on using computing not for business purposes but scientific purposes and how we can forward science using compute and technology and I’ve felt much the same way for some time. The new layers and layers of abstraction added little in the way of productivity to getting to the root problems I wanted to and there have always only been so many hours in the day and dollars in the sponsoring agency’s purse to pursue new innovative work.

Now a lot can be cast off to LLMs to focus on the problem space and the innovative computing use around them. It’s been exciting to not worry about arbitrary idiosyncrasies and machete through jungles of technical minutia to get to the clearing. I still have to deal with them but less of them. And I don’t have to commit nearly as much in the technical space to memory to address problems, I can often focus on higher level architectural decisions or new approaches to problems. It’s been quite enjoyable as well.

[robofanatic]

> with the latest bizarre web stacks, frameworks for everything, node for this, npm for that, Angular, React, Vue, whatever - as if solving business problems just became too boring for software developers, so we decided to spend our cycles on the new hotness at every turn

I kinda feel the same way when I visit Home Depot once a year

[sph]

> Years ago I completely stopped coding, becoming tired of the never ending rat race of keeping up with the latest bizarre web stacks, frameworks for everything, node for this, npm for that, Angular, React, Vue, whatever

Have you tried Claude? No, Opus? No, not that version, it's two weeks old, positively ancient lol. Oh wait, now OpenClaw is the cool thing around the block.

My dude, the rat race just became a rat sprint. I hope you're keeping up, you're no spring chicken any more.

[techpression]

Only running one agent? You should have a distributed network of them at least, if you don’t you will get left behind! Running on the cloud? Stupid, buy hardware for tens of thousands of dollars to run it locally, own your tools. Etc etc, I haven’t seen a crazier rat race in tech ever, the JavaScript framework era is looking like the most stable of software times compared to where we are right now.

[paulkrush]

Your comment is timeless. Just replace your tech keywords with those from the past or the future.

[sph]

I’ve been around for a while. You didn’t have a game changing new framework or library every month.

[Bewelge]

I also find these things incredibly annoying. But I've been actively working in webdev the past couple of years so I was actually keeping up with stuff. And I still consider this a cheat-code.

It makes it so easy to cut through the bullshit. And I've never considered myself scared of asking "stupid" questions. But after using these AI tools I've noticed that there are actually quite a few cases where I wouldn't ask (another human) a question.

Two examples: - What the hell does React mean when they say "rendering"? Doesn't it just output HTML/a DOM tree and the browser does the actual rendering? Why do they call it rendering? - Why are the three vectors in transformer models named query, key & value? It doesn't really make sense, why do they call it that?

In both cases it turns out, the question wasn't really that stupid. But they're not the kind of question I'd have turned to Stackoverflow for.

It really is a bit like having a non-human quasi-expert on most topics at your fingertips.

[firemelt]

agree with u papa, fuck leetcode!

[heresie-dabord]

> as if solving business problems just became too boring

And yet, having customers and listening to them is the whole point.

Anything that re-ignites a person's zest for thinking and creating is a net gain.

That said, it is paradoxical that the catalyst in this case is a technology that replaces thinking.