Developer and refugee from Reddit

  • 1 Post
  • 79 Comments
Joined 2 years ago
cake
Cake day: July 2nd, 2023

help-circle






  • I don’t think that comparison is apt. Unlike with music, there are objectively inefficient and badly-executed ways for a program to function, and if you’re only “vibing,” you’re not going to know the difference between such code and clean, efficient code.

    Case in point: Typescript. Typescript is a language built on top of JavaScript with the intent of bringing strong and static type-checking sanity to it. Using Copilot, it’s possible to create a Typescript application without actually knowing the language. However, what you’ll end up with will almost certainly be full of the any type, which turns off type-checking and negates the benefits of using Typescript in the first place. Your code will be much harder to maintain and fix bugs in. And you won’t know that, because you’re not a Typescript developer, you’re a Copilot “developer.”

    I’m not trying to downplay the benefits of using Copilot. Like I said, it’s something I use myself, and it’s a really helpful tool in the developer toolbox. But it’s not the only tool in the toolbox for anyone but “vibe coders.”


  • I’m of two minds on this.

    On the one hand, I find tools like Copilot integrated into VS Code to be useful for taking some of the drudgery out of coding. Case in point: If I need to create a new schema for an ORM, having Copilot generate it according to my specifications is speedy and helpful. It will be more complete and thorough than the first draft I’d come up with on my own.

    On the other, the actual code produced by Copilot is always rife with errors and bloat, it’s never DRY, and if you’re not already a competent developer and try to “vibe” your way to usablility, what you’ll end up with will frankly suck, even if you get it into a state where it technically “works.”

    Leaning into the microwave analogy, it’s the difference between being a chef who happens to have a microwave as one of their kitchen tools, and being a “chef” who only knows how to follow microwave instructions on prepackaged meals. “Vibe coders” aren’t coders at all and have no real grasp of what they’re creating or why it’s not as good as what real coders build, even if both make use of the same tools.








  • But it still manages to fuck it up.

    I’ve been experimenting with using Claude’s Sonnet model in Copilot in agent mode for my job, and one of the things that’s become abundantly clear is that it has certain types of behavior that are heavily represented in the model, so it assumes you want that behavior even if you explicitly tell it you don’t.

    Say you’re working in a yarn workspaces project, and you instruct Copilot to build and test a new dashboard using an instruction file. You’ll need to include explicit and repeated reminders all throughout the file to use yarn, not NPM, because even though yarn is very popular today, there are so many older examples of using NPM in its model that it’s just going to assume that’s what you actually want - thereby fucking up your codebase.

    I’ve also had lots of cases where I tell it I don’t want it to edit any code, just to analyze and explain something that’s there and how to update it… and then I have to stop it from editing code anyway, because halfway through it forgot that I didn’t want edits, just explanations.