@u0000-u2x
So basically copilot is a great excel corner-drag-fill-thing
@RickWeberEcon
Working with these LLMs is like managing a team of brilliant high school interns. They're brilliant, but they're also teenagers. Manage them wisely and they'll multiply your abilities (at least within some narrow domain). Let them walk all over you and they'll write garbage faster than you can pick it up.
@JFrameMan
copilot is the best if you're using it to make development fun. If you let it take care of filling in the boring things like lists of constants, filling out predictable arguments, filling out syntax that's easy to forget, you end up having way more fun writing out the logic that requires actual thinking. If you use it to fill in logic, even if it did it correctly 100% of the time, you're going to get disillusioned with the whole dev experience and you won't have any fun feeling confused and like you're not leveling up your skills at all.
@scottiedoesno
Having spent a few months letting copilot write bugs for me, I'm no longer worried that it's going to take my job. Also, adding copilot to cmp seems to be the better option for me since it's easier to ignore bad suggestions. Love the video, been waiting for the review!
@remrevo3944
3:43 There is actually even a better way to prevent this bug than adding the condition: Instead of using a condition you can match against the slice of self.frames (match &self.frame[..]) and then use [first, .., last] as pattern to guarantee that first and last are not the same element, while being both more readable and less error prone.
@DanielKaspo
Love this so much, been using Co-Pilot and had a few moments where I'm like "No wait, that's a bug!" The biggest difference between me and you though is that when I used Co-Pilot, it had actually wrote code for an edge-case and I created a bug by trying to correct it 😂
@jeremybuckets
You know how the worst part of your job is combing through a junior dev’s PR to make sure they aren’t going to break everything if their code gets merged? Now with CoPilot you can have that experience writing your own code too!
@myestery
Copilot has really improved my scope in terms of backend programming. All helper functions I need are auto generated, even the ones I didn't know I needed. Also in terms of translation of a requirement I copied somewhere or a json I need to manually write
@nonstopper
Co pilot has only been good for me as a small intellisense snippet engine. Its been dead wrong when I let it write more than 50 characters honestly.
@thfsilvab
Using it for a month, I really enjoy it writing boilerplate for me, but I enjoy it more when it writes unit tests for me!!! I've got some whole suit of tests entirely written by Copilot with few fixes from my part!
@AssemblyWizard
The fps function should use (n-1) for the calculation rather than n. Consider having 3 frames, one per second. So the duration difference between the first & third is 2 seconds, then you're dividing by 3.
@NNOTM
I find that it's good for rewriting existing code. E.g. a couple days ago during a Scala code review, I saw someone had a long chain of matching on Optional values, and I wrote `// instead we use a for-comprehension`, and Copilot perfectly rewrote the code as a for-comprehension.
@heroe1486
Using it for a week and I love the autocompletion so far, no amount of vim skills could save you that many key strokes, like writing arguments + types a have never been that fast, when I'm doing something obvious/easily understandable and it spots it or the pattern it's also cool, it takes some corrections but it's faster than from scratch. I still have a key mapping to toggle it tho since it can be annoying if you're focusing on doing something non trivial and it proposes you nonsense.
@sonofabippi
Massive thank you for this.
@antidotejack2771
Copilot is such a complete tool, not only writes code for you, also writes bugs for you! Freaking awesome!
@strikeeaglechase1582
I extremely rarely let copilot write multiple lines of code, but as single-line automcomplete iv found it incredible
@KeithWhittingham
My experience exactly after 4 months. My take is that you code faster in the beginning but the gain becomes less and less. Coding is much more tiring because you don't have to write the stuff that require less thought. You're always working in the hard bits. It won't replace good programmers. It will reduce the number of good programmers because beginners will rely on it.
@jordanasghar6419
The summary is my exact experience of copilot. For languages I consider myself competent in, I love copilot. It helps smooth out the boilerplate and I generally can provide it with enough context to guess what I'm up to. For languages I'm learning, I generally turn it off and debug interactively with gpt
@ricardopieper11
One other thing that Copilot is really good is generating code for an API that you're unfamiliar with. I had to do some stripe scripts to check that all invoices were generated correctly. It would take like 30 minutes of me looking at the documentation, working through all that text, instead Copilot generated the code for me in 3 minutes. But it was still important that I knew some details on how the API worked beforehand, so I had the opportunity to fix some of the bugs before they happened. If I hadn't knew the Stripe API details beforehand, maybe it would take like 10 minutes. Still better than 30.
@ThePrimeagen