r/programmer • u/der_gopher • 9d ago
Article The future of Software Engineering is boring
https://packagemain.tech/p/the-future-of-software-engineering11
u/Deep-Emotion-6279 9d ago
Isn’t point 2 just admitting that it doesn’t actually work? You get a short term boost in feature delivery by racking up tech debt that then slows you down even with AI.
The conclusion to the piece should be that the future is cleaning up the mess caused by rapid rollout of this technology.
3
u/secondgamedev 9d ago
For my company we still do a lot of outsourcing and the tech debt for outsource increased more then just internal team (still have tech debt because of all the business promises). But now with internal team + outsource + AI we have way more features but also way more tech debt!
1
u/tcpukl 8d ago
Outsourcing doesn't care about tech debt.
1
u/secondgamedev 8d ago
Well if we complain just like AI they will fix it, but still need to tell them what I want fixed just like AI but with people
1
u/Fit-Notice-1248 8d ago
Tell them exactly what you need and how to do it and still come back with it all being wrong and messed up.
1
u/Serializedrequests 4d ago
It's such fallacious thinking. False dilemma, black & white, etc.
My perspective: I have always been very conscious that when the client is paying you, you put their interests first even if they're boring. Fun coding has always been the exception to the rule.
1
u/Deep-Emotion-6279 4d ago
I’m sorry, wtf? Where did I mention fun?
I’m referring to the point in the piece that talks about the long-term maintainability of large code bases.
How is that a false dilemma? It’s a pretty real fucking dilemma if you can no longer maintain your code, and it’s so complex even the AI is starting to struggle.
My perspective: when a customer hits an issue that impacts several hundred thousand of their customers, they tend to be pretty keen for you to explain what went wrong and why.
1
u/Serializedrequests 4d ago
The original article mentions fun. I was agreeing with you. Articles are treating AI coding like it's all one thing or all another thing.
0
u/ComfortableCan67 8d ago
Do you use LLMs for coding? I've been programming for years before LLMs and now many years with LLMs (agentic development). I'm not sure about the technical debt you're referring to?
I'd really like to meet an engineer who can code better than frontier LLMs because I'm not sure if they exist. I understand where this comes from, but the idea that LLMs produce 'slop' code with vulnerabilities simply isn't true anymore. Maybe someone with really basic prompts is going to have results that cut corners, but that's part of the task, telling an LLM how you want the work done.Look at the most recent PHP incident: this is old, human written code that's been around for years, and AI found critical vulnerabilities in it, when people glossed over this fact for years. If anything the opposite is true: AI is going to continue finding vulnerabilities in systems that human programmers have accepted for decades. That's not to say that I think humans programmers don't have a place, someone who knows how to code is the best orchestrator of agents, which often requires lots of microdecisions and alignment to human and business values.
3
u/Deep-Emotion-6279 8d ago
> Do you use LLMs for coding?
Yeah.
> I’m not sure about the technical debt you’re referring to?
Hmm, perhaps the same tech debt the article was talking about? The code base becoming so large and complex that even frontier LLMs have trouble wading through it.
I don’t know why you started talking about vulnerabilities, I never mentioned that. I don’t think the article did either.
1
u/tesseraphim 8d ago
Ok...so then the problem isn't the code? It's that we get double the functionality, thus we get double the debt?
And the amount of functionality is too much for the team of current size to keep conceptual control over?
Or are you telling me if you gave the humans time to write the doubling of functionality, it would somehow be less maintenance than the same amount written by an LLM?
1
u/Deep-Emotion-6279 8d ago
> Ok…so then the problem isn’t the code?
Tech debt is made of code so, yes, the code is the issue.
> It’s that we get double the functionality, thus we get double the debt?
In my experience this is not how tech debt works. It doesn’t scale linearly with features added. It also doesn’t need to go up. You could add two features and half the debt, maintain it at the same level, double it, quadruple it, and so on.
Also, in my experience, LLM aren’t really great from this perspective.
Yeah I do think that a group of experienced devs could add the same features with less maintenance burden at the end. Again this comes from my experience and the devs that I work with.
1
u/QuarkOfTheMatter 5d ago
This is what im finding as well, many who comment are either larping around and have used one of the free models from google or the starter plans from some of the other companies years or months ago or they are firmly in the anti-ai camp and refuse to actually see the latest capabilities just out of their own fears of becoming obsolete at their jobs. And this group of people assume their limited free tier or 5+ month old experience is the actual capability of the public frontier models. Take OpenAI's Astra on Extra High, or Anthropics Opus 5.5 or Fable 5.2 on Extra High and it will just do high quality work as long as you let it.
1
u/ComfortableCan67 5d ago
Yup, I think it's either straight up denial or not knowing/understanding the capabilities of modern tools. It's sad really, I'm fearful too, but the dumbest thing we could do as a society is continue to mock and sneer at the capabilities of AI. I had a prof in 2020 who didn't think that AI would be able to automate simple parts of coding like solving little puzzles in C, and now in 2026, AI can solve millennium math problems with ease. Now imagine what it can do in another 6 years... It's quite terrifying really, and the public and government needs to be aware of what's coming so we can prepare.
1
u/QuarkOfTheMatter 4d ago
and the public and government needs to be aware of what's coming so we can prepare.
Gov is hopeless, people in charge are way beyond retirement age and in some cases think "Cloud" means there is something actually floating somewhere. Good luck trying to explain Agentic Ai to that crowd. And as far as the public, some are very on board while others are clearly in the "its a statistical parrot" camp or just outright in denial stages of their life.
1
u/ComfortableCan67 4d ago
Yeah, I don't live in the states so a bit different from my perspective, but I have 0 faith in this current administration to do anything about it, though the midterm results could help. Luckily, an AI catastrophe would be pretty bad for business, so if these AI companies are interested in keeping this going, eventually the only choice will be to slow down, or suffer the consequences.
1
u/Deep-Emotion-6279 4d ago
5.5 is the first decent model. But the tech debt issue is still there in terms of code base complexity. It can get the code working but it still makes dumb decisions in terms of abstractions, encapsulation etc.
It also misses a lot of potential mixed mode issues. So you do need to hold its hand quite a bit to navigate it through.
1
u/QuarkOfTheMatter 4d ago
Opus 5.1 and Fable 5.1 handled things just fine. On open AI's side Astra has been a power house.
It also misses a lot of potential mixed mode issues. So you do need to hold its hand quite a bit to navigate it through.
Most of the time if there is a thing it misses, you can do a post implementation review and correction session where can have it add that particular pattern to its memory so it handles it better in the future. If you dont have these type of "Lets review why you failed, and recommend how to avoid this failure in the future" type of sessions with your preferred AI tool then how can it ever get better for your use case?
1
4
u/digitaljestin 9d ago
Yep. There's still work to be done, but it's not work I have any interest in doing.
2
u/ADDSquirell69 9d ago
This room boring
1
u/dashingThroughSnow12 8d ago
Yup. Seeing the same article posted seven times on various subreddits is also boring.
3
u/SadSongsMakeMeGlad 9d ago
We are still figuring out how to work with agents, because their capability is constantly moving, but my experience has shown me that you choose your own level of involvement, based on what the product needs. Sometimes you work as a designer, sometimes a software architect, but the point is you decide how much to delegate to the agent. If you want to fully control the code and patterns, you can do that.
I feel like these types of viewpoints just haven’t figured out a healthy approach to developing with agents. If you’re just typing what you want and walking away and expecting to ship what comes out, then yeah you’re in for a bad time, because that’s not how it works. You’ve got to be in there, helping to build the system.
Anecdotally, I’ve never made better software than I do today working with a frontier model. It has a consistency of design and architecture that I could rarely justify spending the time on before. The UI/UX is also much more polished and feature-complete. There is a lot to be excited about, don’t listen to the people who haven’t figured it out yet.
1
u/AnotherYadaYada 8d ago
I coudn't imagine just checking the work of AI and letting it do the part of the job that I signed up to do. Was a programmer a long time ago, I loved coding, figuring things out, optimising. If I was close to retirement, maybe, but not if I was just entering the field. Strange how things changed so quickly.
1
u/Alternative_Win_6638 6d ago
Before you give up on SWE, you're missing a crucial point. In every engineering discipline other than software, engineers have always done the design, planning, handoff to subcontractors, and validation of the work. Did anyone ever consider mechanical engineering boring, or call mechanical engineers caretakers, just because they hand off the implementation to another party? Or should software engineers adapt to the way engineering really needs to work? I talk about this in my video: https://youtu.be/Qd-gsgiXGD4
1
u/Alternative_Win_6638 6d ago
Before you give up on SWE, you're missing a crucial point. In every engineering discipline other than software, engineers have always done the design, planning, handoff to subcontractors, and validation of the work. Did anyone ever consider mechanical engineering boring, or call mechanical engineers caretakers, just because they hand off the implementation to another party? Or should software engineers adapt to the way engineering really needs to work? I talk about this in my video: https://youtu.be/Qd-gsgiXGD4
1
u/DragonfruitGrand5683 4d ago
Think about it this way. In the 1960s you built the machine physically before you programmed on it, that was serious science. Output was basic numbers
Then programming became a seperate thing, you only made the compiler, or used someone elses. Output became operating systems. But for scientists that was boring.
Now you don't do the language, you build from parts. It's no longer programming, it's prompts. But your output can be pretty much anything.
So you have to evolve every decade or two.
0
u/GreatLab8898 8d ago
The past of Coding was fucking Boring. I never enjoyed the actual part of the Coding. Just the Engineering, Planning and Problemsolving of it.
1
u/Forward_Problem_8982 8d ago
Good news for you then. For others, coding is the best part and a method to solve problems.
-1
u/kyngston 9d ago
we used to solve moving data between registers with assembly code. now we just write high level descriptions of the code and compilers write the stuff that actually runs.
i don’t see people terribly bent out of shape about that anymore
4
u/Krom2040 9d ago
One of the most common, most out-of-touch perspectives on AI use in software engineering.
The point of basically every other tool ever devised to build software is to have the ability to clearly and succinctly express the process for what you wanted to accomplish. It was finding the right level of abstraction for the goal, but still ultimately a completely deterministic process with predictable characteristics.
That is fundamentally different from asking AI to do the work and hoping it gets it right. It’s more akin to a CTO having the bright idea to outsource work to Bangalore and calling that software engineering.
1
u/Adn0nnymous 8d ago
go download clang and run “clang++ write me a to-do app” and if it does, THEN you’ll have a real fucking argument.
1
u/kyngston 8d ago
you saying you’re going to miss writing to do apps?
1
u/Adn0nnymous 8d ago
no, i’m saying the abstractions of a compiler and the abstractions of an AI agent are completely incomparable.
1
u/kyngston 8d ago
“due to language abstraction, we are now able to code at a higher level of abstraction leaving boilerplate implementation details to the new tools”
what am i referring to?
0
u/blindered 9d ago
The thing is, when SE gets too easy, there won't be a market anymore.
1
u/nonikhannna 9d ago
The How always matters. I see people vibe coding and burning through tokens like crazy. That's not maintainable just like tech debt.
A layer that makes all this manageable is the market and where engineering will live.
4
u/BabarOnWheels 8d ago
This is a great analogy: