Live data from Hacker News

Software Engineering fundamentals matter more

rhonabwy.com

51–60 of 266 posts

Re: Software Engineering fundamentals matter more

#52
post #48

AI generated code is like IKEA furniture. IKEA furniture embodies many elements of good cabinet making but skips many nonessential elements. And does this more consistently than cabinet makers who can be bored, incompetent, depressed, burnt out, resentful, tired, having a bad day. In the future AI code inevitably will embody most good software engineering practices. And will do this more consistently than software en…

Having not been formally verified, almost all software today feels cheap. Maybe an AI can change that at some point.

Yay let’s lock ourselves into the formal verification toolsets, so that we can never use new language features again.

Re: Software Engineering fundamentals matter more

#53
post #41

The article says what many here like to hear, but in my opinion the core arguments are false. > Making software debuggable, maintainable, layered, and composable – that’s still quite a trick Not really. I have been working on a mobile app for months, and I stopped even glancing at the code about two months ago. 150k LOC, around half of that in tests, and the AI still has no problem maintaining the code on my behalf.…

Prompt injection. Solved. But accidentally breaking systems is not an issue either, obviously. Even though the system prompt asks for safety rails, and other prompts wouldn't accidentally violate that. https://www.abc.net.au/news/2026-08-10/ai-assistant-hacks-gy...

Alignment of the latest models is questionable, yes. That's a different topic.

For this particular gym incident, supposedly Opus 4.6 was used in OpenClaw, predating the current safety guardrails of Fable and co.

Re: Software Engineering fundamentals matter more

#54
post #33

Earlier quoted context omitted.

How do you expect us to take your views on LLM code quality and durability seriously when a) you don’t even look at the code and b) you’ve only been doing this for two months?

I've been working on the app for four months, and I am clearly not talking about code quality. I am talking about product quality and maintainability. Both are more than adequate. I know this because I have worked on it for an estimated 300 hours. Has the author practiced a similar approach for even a week? I doubt it.

I work on my project for 2 years now and using an LLM always came back to bite me. Learning how something works is needed, slow and painful - but pain is gain.

If this works for you - awesome. Until it doesn't.

As always there is 0 code or link. All talk.

Re: Software Engineering fundamentals matter more

#55
post #48

Earlier quoted context omitted.

Having not been formally verified, almost all software today feels cheap. Maybe an AI can change that at some point.

Yay let’s lock ourselves into the formal verification toolsets, so that we can never use new language features again.

OR new languages and frameworks ever again, since they'll slow down code generation due to lack of training, and from LLM generation standpoint this is a terrible thing to trade off.

Re: Software Engineering fundamentals matter more

#56
post #54

Earlier quoted context omitted.

I've been working on the app for four months, and I am clearly not talking about code quality. I am talking about product quality and maintainability. Both are more than adequate. I know this because I have worked on it for an estimated 300 hours. Has the author practiced a similar approach for even a week? I doubt it.

I work on my project for 2 years now and using an LLM always came back to bite me. Learning how something works is needed, slow and painful - but pain is gain. If this works for you - awesome. Until it doesn't. As always there is 0 code or link. All talk.

And when do you expect my approach will stop to work? The core features are complete and the codebase is already sizable.

I will not publish my app on GitHub for free. It's a paid app, and I am putting in the hours not for your approval, but for commercial gain.

I also do not think it wise to link my HN account to my real name and expose my opinions and comments to my employer and colleagues.

Re: Software Engineering fundamentals matter more

#57

AI generated code is like IKEA furniture. IKEA furniture embodies many elements of good cabinet making but skips many nonessential elements. And does this more consistently than cabinet makers who can be bored, incompetent, depressed, burnt out, resentful, tired, having a bad day. In the future AI code inevitably will embody most good software engineering practices. And will do this more consistently than software en…

The problem with this analogy (actually one of many) is that most people can make do with a cabinet that is literally identical to everyone else's. IKEA is great for that.

If you want software that is literally identical to what someone else is using then you don't need AI. You need a license to that software! That is just the traditional software model.

AI gives software that is bespoke with hundreds of decisions made, hidden from you, in the background. If it's a throwaway script, that's fine (and I don't mean to undersell this - this is a huge application). If you want a larger program that is going to form part of your business process then it will need at least some level of supervision from an actual expert.

Re: Software Engineering fundamentals matter more

#58

AI generated code is like IKEA furniture. IKEA furniture embodies many elements of good cabinet making but skips many nonessential elements. And does this more consistently than cabinet makers who can be bored, incompetent, depressed, burnt out, resentful, tired, having a bad day. In the future AI code inevitably will embody most good software engineering practices. And will do this more consistently than software en…

Ikea cabinet is pleasant to look at, and its design makes sense.

Re: Software Engineering fundamentals matter more

#59
post #48

AI generated code is like IKEA furniture. IKEA furniture embodies many elements of good cabinet making but skips many nonessential elements. And does this more consistently than cabinet makers who can be bored, incompetent, depressed, burnt out, resentful, tired, having a bad day. In the future AI code inevitably will embody most good software engineering practices. And will do this more consistently than software en…

Having not been formally verified, almost all software today feels cheap. Maybe an AI can change that at some point.

By Dijkstra's standards, we've been vibe coding for an entire century!

I had similar thoughts recently, that now that machines are good at writing proofs, this could help with their reliability in software development.

Then I had a funny incident where an LLM implemented a feature completely backwards. Plenty of tests were supplied which demonstrated that the completely broken feature was correctly implemented.

I realized that formal verification would not have helped here, if I had left the task to the machine. It would simply have written a mathematical proof of the correctness of the incorrect feature!

Apparently this is an issue for humans as well, called the "spec gap" or something like that.

Re: Software Engineering fundamentals matter more

#60

The article says what many here like to hear, but in my opinion the core arguments are false. > Making software debuggable, maintainable, layered, and composable – that’s still quite a trick Not really. I have been working on a mobile app for months, and I stopped even glancing at the code about two months ago. 150k LOC, around half of that in tests, and the AI still has no problem maintaining the code on my behalf.…

I tried this recently and the results were total banana cakes. They couldn't even make changes to Pong without breaking it.
Post reply on HN