> Not sure how I feel about it

A phrase I've been toying with is eyes free vs hands free coding.

The distinction is important. While I too hardly write code these days, I do continue to make smaller changes and look at what's being done. This is as opposed to the group who has decided vibing mega commits is a good idea.

▲

XCSme 7 hours ago | parent [-]

I am not doing small changes though, I add large features or refactors daily, which involve changing hundreds of files and thousands of lines, even if I wanted I couldn't review everything by hand.

▲

verdverm 7 hours ago | parent | next [-]

I have done this too, for side projects, but I see the limits. Discovering what happens when we do this was one of my intentions and why I hold my opinions.

For these projects I make regular time to look through the code and do cleanup phases.

▲

nvme0n1p1 5 hours ago | parent | prev [-]

So you're saying simultaneously, the code is "higher quality than ever", but you also haven't even looked at the code to see its quality. Classic. I think you're mistaking quantity for quality.

	▲	munksbeer 2 hours ago \| parent \| next [-]
		If a product functions correct and performance is good, and AI agents write and maintain all the code, no-one has to care about human level code quality. The concept of "code quality" was only invented to make it easier for humans to understand and change code.
	▲	XCSme 5 hours ago \| parent \| prev \| next [-]
		I mentioned before, code is definitely worse, but end product is better. High quality code doesn't always lead to a high quality product. And bad code doesn't always lead to a bad product.
	▲	verdverm 5 hours ago \| parent \| prev [-]
		I think they are saying they are using proxies for project quality, like features and test coverage