logoalt Hacker News

trueno • yesterday at 11:52 AM • 4 replies • view on HN

it doesn't worry me too much tbh. This is really just cutting corners and going this route leaves you with some kind of additive ship of theseus piece of software you don't understand and require your frontier model to work with, which just... becomes more additive and gross. right now we're in some proverbial heyday of everyone seeing how absolutely grand of a thing they can make with frontier models. over time i expect some old design philosophies to take hold with people who use LLM's successfully and find a place again paired with developers who understand why such layered methodologies are important... because this whole AI thing wasn't the silver bullet CEO's and crazy execs thought it was. They will eventually get sick of the support burden of badly designed stuff. i anticipate a bit of pendulum swinging back towards "still using AI, but we need smart people to do it because it's expensive and we want it done right". Right now a lot of companies are being extremely reckless imo and they haven't fully realized/felt the cost implications of trainwreck software yet.


Replies

LPisGood • yesterday at 1:56 PM

What if those “cost implications” are just asking Opus 6.7 to fix whatever issue cropped up?

➕ show 3 replies
huijzer • yesterday at 8:37 PM

> haven't fully realized/felt the cost implications of trainwreck software yet

As long as the API is private or not dependent on by automated systems and you have good test coverage, you can get away with bad code IMO since you can always refactor. If it looks stupid but it works (and can be refactored/fixed/improved later if needed) it aint stupid.

➕ show 1 reply
agile-gift0262 • yesterday at 4:29 PM

IMO the fundamental principles and "conflicts" are still the same, but many have forgotten about them with all the hype and sense of speed. The industry will slowly rediscover them.

swat535 • yesterday at 4:45 PM

Support burden? When did companies care about customer support or system maintenance?

They already did the bare minimum allocation to both despite engineering screaming at them.

I highly doubt executives are going to accept slower release and sale cycles in order to provide better support.

If anything, I expect this trend to accelerate. I’m imagining the opposite, a plethora of AI slop with increasingly burned-out engineers.

➕ show 2 replies