Hacker Neue

Preferences
jay_kyburz parent
I worry that once I've done all that I won't have time for my actual work. I also have to investigate all these new AI editors, and sign up for the API's and work out which is best, then I have to learn how to prompt properly.

I worry that messing with the AI is the equivalent of tweaking my colour schemes and choosing new fonts.

cartoonfoxes
Some of what I learned from a decade of keeping up with the perfusion of JS libraries and frameworks seems relevant to AI:

- anything with good enough adoption is good enough (unless I'm an SME to judge directly)

- build something with it before considering a switch

- they're similar enough that what I learn in one will transfer to others

- everything sucks compared with 2-3 years from now; switching between "sucks" and "sucks+" will look silly in retrospect

chii
how do you prevent lock-in when choosing?
haiku2077
If you can build, test and run your project entirely from the command line you're never locked in. Every project I've worked on in the past decade has not enforced a choice of editor, and most have been portable to 2-3 OSes.
haiku2077
> I also have to investigate all these new AI editors, and sign up for the API's and work out which is best, then I have to learn how to prompt properly.

I found this didn't take me very long. Try things in order of how popular they seem and keep notes on what you do and don't like.

I personally settled on Zed (because I genuinely like the editor even with the AI bits turned off), Copilot (because Microsoft gave me a free subscription as an active OSS dev) and Claude Sonnet (seems to be a good balance). Other people I work with like Claude Code.

This item has no comments currently.