3 ms·
Sometimes you're just sketching in a notebook, or working on a shell script, a Makefile, something you don't do often enough to have the syntax and idiosyncrasi
by reubenmorais 2y ago
Sometimes you're just sketching in a notebook, or working on a shell script, a Makefile, something you don't do often enough to have the syntax and idiosyncrasies at the tip of your fingers. Sometimes you're doing something very mechanistic but not easy to automate, like converting some filtering logic from one DSL to another. Sometimes there's just a lot of typing required to do something conceptually very simple. I find Copilot very useful in these side quests, but when I'm working on the hard stuff, the core functionality, it often just outputs nonsense that takes more time to review/fix than it would take to just write it myself. So it takes some learning of when to use it and when to ignore it but I've come around to appreciate it at times.
- ljm 2y agoCopilot for me basically seems like semantic copy/paste. I’m doing some refactoring and make the same style change in a couple of files, then copilot kicks in and understands enough to suggest a legit completion for me. I only use it sparingly though because it can too easily become a crutch where you start to feel a bit lost without it.