undefined | Better HN

0 pointswtetzner4mo ago0 comments

> It's strange to me when articles like this describe the 'pain of writing code'.

I find it strange to compare the comment sections for AI articles with those about vim/emacs etc.

In the vim/emacs comments, people always state that typing in code hardly takes any time, and thinking hard is where they spend their time, so it's not worth learning to type fast. Then in the AI comments, they say that with AI writing the code, they are free'd up to spend more time thinking and less time coding. If writing the code was the easy part in the first place, and wasn't even worth learning to type faster, then how much value can AI be adding?

Now, these might be disjoint sets of people, but I suspect (with no evidence of course) there's a fairly large overlap between them.

0 comments

3 comments · 3 top-level

falkensmaize4mo ago

What I never understand is that people seem to think the conception of the idea and the syntactical nitty gritty of the code are completely independent domains. When I think about “how software works” I am at some level thinking about how the code works too, not just high level architecture. So if I no longer concern myself with the code, I really lose a lot of understanding about how the software works too.

geetee4mo ago

Writing the code is where I discover the complexity I missed while planning. I don't truly understand my creation until I've gone through a few iterations of this. Maybe I'm just bad at planning.

thwarted4mo ago

At first I thought you were referring to the debates over using vim or using emacs, but I think you mean to refer to the discussions about learning to use/switching to powerful editors like vim or emacs. If you learn and use a sharp, powerful editor and learn to type fast, the "burden" of editing and typing goes away.

1 more reply

j / k navigate · click thread line to collapse