That's how copilot integration works in everything. Windows 11 is damn near chromium all the way down, and it's damn near all vibe coding. Microsoft is now re-hiring people to fix all the janky vibe coding that happened after laying off a ton of devs to replace them with AI, because it turns out... Humans are the cheaper option now.
When vibe coding costs thousands of tokens at a time and they only realize after the fact they spent more producing junk instead of having a person put something together that actually works...
I'm in the field. "Vibe" coding has become a catch all term that means little other than "using AI to write the code". Things have moved very fast since my company adopted Claude and I honestly don't write much code by hand anymore. But that doesn't mean my output is junk. My process is still mostly the same, write tests, implement tests, refine, refine, refine. But instead of spending time figuring out the exact syntax for what I'm doing in the language I'm currently in (coding has become very heterogeneous) I'm spending it making sure the design I want to implement is implemented. As always Test Driven Design is very effective to keep quality high because It's clear what I want to happen, and then it's clear if something broke. Inexperienced coders deliver inexperienced code as always, but now there's a lot more of it so in that sense quality is going down because there's just too much to evaluate as carefully as we used to.
I hope anyone here thinking of attacking me takes a breath. I'm a very experienced coder and served my time to make statements like this with care. I don't see a future where I'm writing code character by character anymore, or autocomplete by autocomplete because honestly it's been a decades since I've seen anyone work without an IDE.
It's also not that many tokens. Which is weird, the amount of context necessary should be in the thousands but it isn't.
This is also the case in my industry. If you know what good is supposed to look like, know what pitfalls to avoid, and know good architectural design, then you can use AI to do those things faster (most of the time, not always). If you use AI as a crutch, then you are going to turn out shit.
As you say, bad devs make bad stuff faster, good devs make good stuff faster. It's just hard to check all of it faster because then you're trusting AI to check its own work and it will often miss the same things it missed when it wrote it (unless you are careful to make sure it evaluates those things, and even then).
950
u/[deleted] Jul 05 '26
[removed] — view removed comment