@mirak_dude Do you still take a look at your code, especially in vscode ?
Report
@moss_ab_mirande_ney yes I do, I use AI for debugging and Understanding issues, on my code and direct it to follow the algorithmic flow
Report
Terminal for anything touching more than about three files, IDE for anything I already suspect is wrong. That split isn't taste, it's about where the review happens. In the terminal the review surface is the diff, so I have to open git and actually read it. In the IDE the review happens as it types, and I've caught myself nodding along at changes I never really read. The RAM cost is real but it's the smaller one. The bigger one is that a terminal agent is much easier to leave running unsupervised, which is exactly how we ended up with adapters whose tests only checked our own output shape.
Replies
I usually prefer an app when I’m working on larger tasks. The visual context makes it easier to review changes.
Murmell
@julian_ting2 Hmm understandable, but do you struggle with computer usage, because for myself i often find that the GUI consumes so much cpu and ram
Murmell
i personally prefers the terminal version
@moss_ab_mirande_ney what is the benifit of it ?
An IDE, preferably Cursor or VS code
Murmell
@mirak_dude Do you still take a look at your code, especially in vscode ?
@moss_ab_mirande_ney yes I do, I use AI for debugging and Understanding issues, on my code and direct it to follow the algorithmic flow
Terminal for anything touching more than about three files, IDE for anything I already suspect is wrong. That split isn't taste, it's about where the review happens. In the terminal the review surface is the diff, so I have to open git and actually read it. In the IDE the review happens as it types, and I've caught myself nodding along at changes I never really read. The RAM cost is real but it's the smaller one. The bigger one is that a terminal agent is much easier to leave running unsupervised, which is exactly how we ended up with adapters whose tests only checked our own output shape.