NGL I'd argue there's a certain appeal to "use AI to prototype a feature as fast as possible and focus your engineer hours on building a comprehensive testing and fuzzing plan" followed by a "remove and review everything that can be cut without breaking the tests" cleanup pass.

▲

fwlr 19 hours ago | parent | next [-]

I do see the appeal, it’s easy to imagine that workflow working, and working well - but it’s hard to how it avoids this fate: https://youtu.be/QEzhxP-pdos

▲

Cyberdog 19 hours ago | parent | prev [-]

The “cleanup pass” never happens, though. It’ll just be new feature on top of new feature until it’s too large to refactor.

	▲	dymk 17 hours ago \| parent \| next [-]
		You're describing a problem that's plagued corporate software development for decades. You just get to the "unmaintainable ball of mud" stage faster now. Every few days I spent a while on codebase architecture improvements after landing a slew of features.
	▲	colordrops 18 hours ago \| parent \| prev [-]
		Except it does. It's not some law of physics. I've done exactly this on multiple projects, both personal and corporate.