The “fun” for me has never been “coding” and on the enterprise dev side that has been a commodity for a decade.

If you look at the leveling guidelines for any tech company “codez real gud” will only get you to a mid level ticket taker.

▲

catgary 2 hours ago | parent [-]

And even then - I still read the code it generates, and if I see a better way of doing something I just step in, write a partial solution, and then sketch out how the complete solution should work.

▲

raw_anon_1111 2 hours ago | parent [-]

Unless the solution is going to be more secure, faster, more stable etc, why does it matter?

Will the end user care? “Does it make the beer taste better”?

	▲	dijksterhuis 10 minutes ago \| parent [-]
		in a word, maintainability > maintainability is inversely proportional to the amount of time it takes a developer to make a change and the risk that change will break something https://softwareengineering.stackexchange.com/a/134863 i could be wrong, but i'm pretty sure that end-users get upset when a change takes a long time or it ends up breaking something for them. just because people are finding that agents or whatever are speeding changes up now doesn't necessarily mean they won't encounter a slow-down later when the codebase becomes an un-maintainable mess. technical debt is always a thing, even with machines doing the work (the agent/machine still has to parse a codebase to make changes).