3 ms·
This is interesting because I started using continue specifically because it doesn't just do tab completion. I have normal Github Copilot turned on again as wel
by fzzzy 3y ago
This is interesting because I started using continue specifically because it doesn't just do tab completion. I have normal Github Copilot turned on again as well now after having it off for a while and the tab completion does seem to be better than it was a few months ago. Still, explicitly asking continue to write a diff has a higher 'this is correct' rate for me because I can describe what I want in detail.
Tab Completion seems fine for cases where I add one new line and the next two lines are just incredibly obvious. I am going to experiment with writing a little comment first to see if it primes the tab completion to do something non-obvious.
- imrehg 3y agoMaybe it depends on the work people are doing. I am doing a lot of data engineering where I can be often tabbing through while adjusting bits that are off, or doing Python portion by portion, and depending on the complexity it does go from "finish this string I'm writing" to few lines worth of code. I'm often surprised that how quickly the model discovers reasonable patterns (even across files as well, that's often necessary to be correct). With the diffs I find that by the time I describe things in a way it has a chance of working, I might have just written the whole thing myself. Especially as the diffs are often need correctly. With tabs that correction is part of a fast feedback look, with diffs it's so far a slower loop and just more awkward. Of course, with changes to workflows one or the other can shine and if there's an interface that's faster than typing the instructions out that might just supercharge things for the diff/chat type too.