Writing code, IMO, is mostly the typing. AKA the syntax and whatever libraries/platforms you’re using. They are incidental to creating a software solution to whatever problems. It requires rigor, but it’s not particularly difficult.

Abstractions, logic, and reasoning is not helped by AI tools. Yes they can give you a ready-made solution, but you’ll need to exercise judgement to see if it really fits the problem. And doing the latter can be as hard as just doing it yourself.

▲

blanched 6 hours ago | parent [-]

I would agree with that. Whenever I’ve delegated more than what feels like ~80% to the agent (“vibe coding”, I suppose) is when it starts feeling bloated, messy, and bug-prone.

On the flip side, having a design written ahead of time, ideally with reviews by peers and AI and as little as possible AI “content”, seems to almost always go well.

Obviously very subjective!

▲

skydhash 4 hours ago | parent [-]

I don’t disagree with you, when building with Xcode or Android studio, kinda like 90 percent of the code is generated or copied from examples in the doc. Same with HTML when using a CSS framework. I learned vim, just to be efficient with copypasting :) So far for me to throw shades to anyone using tools.

My arguments is more about throwing slop at fellow collaborators, not ensuring correctness of the code, and various claims that try to justify those behaviors. “The agent wrote it” is no more of an excuse than “It was the accepted answer on Stack Oveflow”.

	▲	blanched 4 hours ago \| parent [-]
		Oh for sure, I think we’re on the same page. I wasn’t trying to change your mind on anything, just adding my two cents :)