←back to thread

183 points WolfOliver | 1 comments | | HN request time: 0.22s | source
Show context
MorehouseJ09 ◴[] No.45067492[source]
“If it takes longer to explain to the system all the things you want to do and all the details of what you want to do, then all you have is just programming by another name,”

I think this is going to make the difference between junior and senior engineers even more drastic than it is today. It's really hard to know what/how to even describe real problems to these tools, and the people who invest the most in their tooling now, are going to be most successful. It's hard for someone who hasn't designed a large codebase already to do this in an ai native way where they don't have the experience of abstracting at the right level and things like that.

Today's equivalent, I've often found some of the best engineers I know have insane setups with nvim or emacs. They invest in their tool chain, and are now bringing AI into.

replies(3): >>45067904 #>>45071016 #>>45071192 #
1. sublinear ◴[] No.45071192[source]
> some of the best engineers I know have insane setups with nvim or emacs. They invest in their tool chain, and are now bringing AI into.

I find this likely, but totally irrelevant to their success now and in the future. AI tools are as much of a trivial choice as any other text editor features. The resulting time spent and code quality are the same regardless of personal preferences.