7 ms·
Interesting article, as I feel the exact opposite. The more time I have to parse out what code does and fix bugs along with that, the less time I actually get t
by satvikpendem 3y ago
Interesting article, as I feel the exact opposite. The more time I have to parse out what code does and fix bugs along with that, the less time I actually get to code. The lack of syntax highlighting is an exercise in frustration for me, it takes me 10x longer to read and therefore understand. So too with Copilot, I can now write side projects twice as fast, if not faster. That, to me, is where the real fun occurs.
I do understand where the author is coming from though as I have friends who have similar setups, monochrome editors with no LSP. Talking to them, I believe they are ADHD or neurotic adjacent, where if the red squiggle is not dealt with immediately, they stress about or have anxiety over it, so the author must be similar. I think they can't relate to others because most others simply don't care. Hell, I'm the same way as the author about phone notifications, as I turn most off and those I don't turn off, I feel like I must deal with immediately as well lest I be anxiously thinking about them, and yet I see so many that have dozens of notifications active. But I simply don't feel the same way about code and writing, while the author does.
Anecdotally, I've been having a blast with ChatGPT Plus with GPT 4. I can ask it interesting programming questions and it provides novel insights. The other day I was thinking of how one could make a better GraphQL type interface, and ChatGPT suggested that the query language also handle local state, ie, there is no local or server side state, it's all just state. I was curious about that and asked it more, going down the rabbit hole as to how the syntax and semantics would look. Best of all, I could do it all on my phone through their app, while I was walking or doing other things. It felt like having another senior engineer who would endlessly trade ideas with you, never tiring.
- konschubert 3y agoI am fully with you. Coding is the act of solving a problem, figuring out an application design and iterating on it. I am satisfied if I fixed a bug, removed a bottleneck or have a new feature to show for at the end of the day. And if AI automates that one day, I will move on. The world has enough problems to solve, so far I see no need to work on those that can be solved by machines.
- firebaze 3y agoInteresting, I'm on the same page regarding the first paragraph of yours. And exactly because of this I dislike using Copilot, since most of the time it will provide a completion which has issues. Not necessarily bugs, but the completion does something slightly off or doesn't (or does) consider an edge case different to what is intended. This detracts me quite a bit from writing code. I don't want to supervise my junior co-developer, I want to get something done - this is why I also, like the author, enable CoPilot only selectively. On the other hand, using ChatGPT-4 (as in chat.openai.com) for creating large-ish chunks of code after discussing the general idea and refining it for a while is a god-send. YMMV, as always.
- satvikpendem 3y agoThat's true, Copilot is often hit or miss but it's mostly been a hit for me, so the additional parsing of suggestions is acceptable to me as, in aggregate, it speeds up my iteration time.
- konschubert 3y agoIf I know what I want to write, Copilot will really speed up my process of writing this. If I don't know what I want to write, ( how to structure the function, how to put the comment, etc...) then asking Copilot for suggestions is distracting. So I make sure I know what I want to write before I hit the keyboard.
- satvikpendem 3y agoIf I don't know what I want to write, I use ChatGPT instead. The combination of both tools is quite incredible for productivity.
- shrimpx 3y agoAre you using Copilot though? It's one thing to talk to GPT4 and another to use Copilot with inline autocompletions.
- satvikpendem 3y agoI use both.