logoalt Hacker News

rsyring • yesterday at 7:47 PM • 0 replies • view on HN

> Just that it's better and faster than how we used to do it.

I think only one of those is true. It takes a lot of effort to get quality architecture and not-function-soup code (at least in Python) from LLMs. I can't imagine the pile of crap code bases these software factory type solutions are producing. Well, you can see a lot of them on GitHub I guess, so no need to imagine.

Further, one of the negative impacts I've seen from being able to go a lot of faster is that it translates to product teams being able to ship faster which is not always better. We've lost the "back pressure" we used to have in software development which forced product teams to consider, then consider again, then consider again as each new sprint requires reevaluating priorities. This resulted in a lot of requests stalling out and never being built that should have never been suggested in the first place. Or, to be more charitable, the delay gave the product team time to get over the initial excitement of a new idea and really consider if it was warranted.

Now we are building all-the-things and I think that's only better in some cases. I think it's proving worse in most other cases. Especially when you consider that every line of code that ships has liability attached to it.

That results in large bloated mess projects that no human can reasonably understand. That means we are dependent on LLMs to understand it and, the larger the code base, the more LLM tokens are required and the worse the LLMs are at understanding all the relevant parts and making wise architecture decisions. This creates a downward spiral that is harder and harder to manage and means features take longer and longer to ship (although, still maybe less time than pre-LLM dev...we'll see).