Nick T
@nt
working with cursor was like working with a really good junior dev working with claude code is like working with a really good mid (2-3y of experience) dev. now even mid-tier devs are doomed.
5 replies
0 recast
23 reactions
kia
@kia.eth
why do devs prefer CLI over IDEs like what's the attraction of claude code over cursor. is it just more performant or the product form factor is desired? cc: @christopher also brought this up once but i didn't fully understand
4 replies
0 recast
4 reactions
christopher
@christopher
Ultimately seeing the code won't change too much about the end result or outcome I'm looking to achieve. I would rather write all my tests first then write the code. Then force AI to fight the test suite to make sure everything passes while I get a matcha.
0 reply
0 recast
2 reactions
7858
@7858.eth
It’s just better objectively. I prefer the IDE UX by a mile but I use Claude code nonetheless because it’s more effective
0 reply
0 recast
5 reactions
Nick T
@nt
two differerent questions: > why do devs prefer claude code? - it does more end to end. it can implement more complicated features with fewer mistakes and less need for hand holding. > why do devs prefer CLI over IDEs (or let's say more broadly UI) - I don't speak for all devs, but probably because CLIs can be composed programmatically with bash scripts and usually allow for more customisation. this doesn't really apply to claude code though. I'm not sure why they made it a CLI, but I personally don't mind it because I use a tonne of CLI tools already and it doesn't spook me.
1 reply
0 recast
3 reactions
jtgi
@jtgi
Claude code is a better agent. It completes correctly at a higher rate. cli easy to integrate into any automated workflow.
0 reply
0 recast
2 reactions
