Hacker News Reader

It's your code review process (with or without agents). If you don't hold this fort, the battle is lost, and the repo is going to devolve.

View on HN

What I'm getting at was covered in an article yesterday about the end of abstraction. There's an argument being made for layer-free software, where everything is one big blob of code, created and understood only by an LLM. The software is modified only by re-prompting.

There are a lot of people edging around this concept, but it's not solid yet.

Can you point to any place/post making this argument? I'm an active lurker here, and have not seen anyone arguing for layer-free/blob-of-code type of workflow.

The fact that some teams find themselves there is simply a realization of what I stated - inactive maintainership by not taking code reviews seriously.

I saw that go by on YC two days ago, and it scrolled off fast enough I can't find it. They were talking specifically about AI tools, as in avoiding harnesses and letting the LLM do more of the job.

Reply on news.ycombinator.com