News for hackers. Stuff that matters.
Re:Software is breaking down at a systemic level by Fr0styMatt88 on Monday November 16, 2026 @01:53PM (#50521374)
Part of it is the hype cycle too. Everywhere you look online, all the easy examples are people one-shotting this and that. Strangely it seems like the 'standard' way for people on YT to 'test' a model is to just one-shot some random game idea. It's meaningless, but it creates this unconscious expectation (even amongst experienced devs who might not be as experienced in AI use) that the models _should_ be able to derive exactly what's needed from a one-shot.

That's fundamentally impossible though -- if the information isn't there, the model is just going to move toward the average and fill in the blanks.

On another note, I'm also not sure where I stand yet on the thing I see where software devs end up falling down the rabbit hole of building little mini software factories, with agents reviewing agents, coordinating agents and having agents cosplay human roles -- essentially 'orchestration porn'. I'm yet to dive into that rabbit hole (I likely will at some point, so I'm not judging), but from the outside it looks like you end up worsening your understanding of the system, while spending tokens unnecessarily and creating a closed-loop mini model collapse.

I've actually run into the situation at work where I've asked people whether the libraries they've made can do a particular thing and sometimes the answer has been "I don't know" (I'm talking just _features_, not even low-level architecture). At that point, something has gone wrong.

Re:Software is breaking down at a systemic level by AlienRobot on Monday November 16, 2026 @02:02PM (#50521483)
I think the correct way to solve this problem is completely at odds with AI.

Write less code. Reuse things that have already been written and thus were already reviewed and tested by someone else. Do not reinvent the wheel. KISS.

With AI everyone is implemented a dozen libraries from scratch in their project instead of using something someone else made. Why use a library for 2D geometry when ChatGPT can write one in 10 minutes?

Re:Software is breaking down at a systemic level by cmiles74 on Monday November 16, 2026 @02:11PM (#50521615)
I have to think part of this is model training, encouraging the model to code-up something new instead of looking for library code that can fit in the project. One of the things I ask Claude repeatedly is something like "can Spring do this already, or is someone working on this already?"

More tokens, more money.

Re:Software is breaking down at a systemic level by ModernMech on Monday November 16, 2026 @03:37PM (#50522899)
> it creates this unconscious expectation (even amongst experienced devs who might not be as experienced in AI use) that the models _should_ be able to derive exactly what's needed from a one-shot.

It also creates an expectation that anything done with AI as part of the process was done in one shot, and therefore the person had no meaningful impact on the output.

Re:Software is breaking down at a systemic level by Fr0styMatt88 on Monday November 16, 2026 @04:20PM (#50523463)
Oh this so much.

I saw a Reddit post of someone asking essentially “I’ve spent the last 7-8 months working with Claude on a game, am I really making something?” and I just wanted to reply “of course you f****ng are, don’t let people tell you otherwise!”

Re:Software is breaking down at a systemic level by ModernMech on Monday November 16, 2026 @04:30PM (#50523567)
For this reason, I keep a "how it started / how it's going" log for everything I work with, to show how it looked after the first prompt, versus how it ended up after extensive work. Just to make clear how my input actually mattered to the output.