Comment by efitz
21 hours ago
Cline and Roo Code (my favorite Cline fork) are fantastic and run as normal VS Code extensions.
Occasionally they lose their connection to the terminal in VSCode, but I’ve got no other integration complaints.
And I really prefer the bring-your-own-key model as opposed to letting the IDE be my middleman.
Using cline for a bit made me realize cursor was doomed. Everything is just a gpt/anthropic wrapper of fancy prompts.
I can do most of what I want with cline, and I've gone back from large changes to just small changes and been moving much quicker. Large refactors/changes start to deviate from what you actually want to accomplish unless you have written a dissertation, and even then they fail.
I agree with all you’ve said but with regards to writing a dissertation for larger changes : have you tried letting it first right a plan for you as markdown (just keep this file uncommitted) and then let it build a checklist of things to do?
I find just referencing this file over and over works wonders and it respects items that were already checked off really well.
I can get a lot done really fast this way in small enough chunks so i know every bit of code and how it works (tweaking manually of course where needed).
But I can blow through some tickets way faster than before this way.