Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AI can code, but it can't build software

bytesauna.com

Post reply on HN
Print view View original

181–185 of 185 posts

Re: AI can code, but it can't build software

#181

Post by latentsea »

pjmlp wrote: post #132
latentsea wrote: post #96

Earlier quoted context omitted.

I think C# is really going to shine in the LLM coding era. You can write Roslyn Analyzers to fail the build on arbitrary conditions after inspecting the AST. LLMs are great at helping you write these too. If you get a solid architecture well defined you can then use these as guardrails to constrain development to only happen in the manner you intend. You can then get LLMs to implement features and guarantee the code…

As someone whose C# is one of the main work ecosystems, I highly doubt it. What I am seeing it that LLMs will push current programming languages down the stack, like now you're enjoying C# => MSIL => Machine code. On my line of work I already can imagine the other side of the tunnel, more low-code/no-code tooling, orchestration agents, and much (much) less manually writing C#, Java and TypeScript.

I don't disagree with your take. My take on your take is that via what I'm suggesting I can envision that the low-code/no-code tooling can be expanded to produce a wider variety of more flexible programs with robust, consistent C# code underpinning them.

Re: AI can code, but it can't build software

#183

Post by adncors »

simonw wrote: post #4

This is a good headline. LLMs are remarkably good at writing code. Writing code isn't the same thing as delivering working software. A human expert needs to identify the need for software, decide what the software should do, figure out what's feasible to deliver, build the first version (AI can help a bunch here), evaluate what they've built, show it to users, talk to them about whether it's fit for purpose, iterate…

what if the real paradigm shift isn't about replacing engineers in building durable systems, but about making software so cheap and disposable that the concept of "technical debt" becomes irrelevant for a new class of "single-use" or ultra-short-lifespan applications?

Re: AI can code, but it can't build software

#184

Post by somebehemoth »

theshrike79 wrote: post #163
somebehemoth wrote: post #149

Earlier quoted context omitted.

Can you please explain? Are you saying all software development outside of the web is "niche"?

Niche as in for every one systems programmer there are dozens of people writing API Glue. By hours of work spent and lines of code produced the latter is in a whole different scale than systems programmers (which is a very badly designed term anyway).

Non web programming is not niche by any definition of the word niche.

Re: AI can code, but it can't build software

#185

Post by KurSix »

latentsea wrote: post #179
KurSix wrote: post #146

Earlier quoted context omitted.

Linters are great at catching specific pattern violations, but they’re useless against bad decomposition or a poorly chosen abstraction. An LLM can generate code that passes all 100 linters and still ends up being a logical mess - with business logic in the wrong layer and completely unmaintainable.

With Roslyn Analyzers and things like ArchUnit I've found its possible to actually write linters that enforce a predetermined architecture with established patterns such as enforcing usage of particular base or framework level classes in specific layers/locations. I agree with the assessment LLMs aren't great at novel architectural work. I'm merely reporting my experience that using LLMs to write analysers that enfor…

This approach is perfect for mature projects with a well-established architecture. But it could be counterproductive in the early R&D stages when the architecture is still fluid and the team is constantly experimenting. The rigid constraints of the analyzers might stifle creativity. So it's a powerful tool, but for the right stage of a project's lifecycle
Post reply on HN