Ooh, unemployment! How exciting! I love Microsoft now.
Seriously who the hell are they trying to sell this to?
Are they just that desperate to keep the hype train going?
Business owners. People that don’t want to spend money on annoying stuff like wages.
CEOs are convinced that if they can get rid of those pesky expensive engineers that idea people will magically make things work.
AI is the promise of slaves 2.0
The circlejerk of tech bros and busidiots who haven’t built a damn thing in their lives.
retail suckers and losers who buy into the AI crap to keep the “bubble from bursting overnight”
There are entire media agencies that only do vibe coding. And that might be enough for a one-off event but many of them „develop“ long term solutions without knowing the code or it‘s vulnerabilities so it‘s safe to say their existence will be short lived.
Copilot, turn on the gas stove without the pilot. Copilot, in 3 hours light the pilot.
My Windows automatically read these instructions from my screen and I died!
You forgot to follow it up with “copilot: open windows” then.
Username checks out
Copilot keeps finishing my code for me in near real time… it completely disrupts my train of thought and my productivity dropped tremendously. I finally disabled it.
I LIKE writing code, stop trying to take the stuff away that I WANT to do and instead take away the stuff I HATE doing.
What I don’t want AI to do:
- write code for me
- write fixes for me
What I want it to do:
- find bugs and tell me about them (but still don’t fix them)
They do have ones that will review your prs. That’s pretty neat
Yeah, I just wrote a blog post comment about how I enjoy using Copilot. But that’s when I explicitly ask it a question or give it a task. The auto complete is wrong more often than it’s right.
Probably doesn’t help that if it was tedious, boilerplate code I would have already explicitly asked it.
I like auto complete because I’m a terrible speller I’d write “int countOfCommplixThang”, but auto complete guesses “int countComplexThing” Sometimes it even comes up with a better name than I would
That old autocomplete is great. It’s specifically the AI autocomplete that’s less useful.
The AI is doing it though. I type “in [tab]” and I get the whole line. Sometimes I don’t even have to type anything.
I’ve never been able to get an AI promt to write useful code though.
I wish I could get it to stop finishing comments for me. It’s like some jackass is trying to complete my sentence for me but gets it completely wrong every time and it breaks my train of thought.
What they forget to mention is that you then spend the rest of the week to fix the bugs it introduced and to explain why your code deleted the production database…
yes but all the code will be wrong and you will spend your entire day chasing stupid mistakes and hallucinations in the code. I’d rather just write the code myself thanks.
Yeah! I can make my own stupid mistakes and hallucinations, thank you very much!
I had a bit of a breakthrough with some personal growth with my code today.
I learned a bit more about entity framework that my company is using for a project, and was able to create a database table, query it, add/delete/update, normal CRUD stuff.
I normally work mostly on front end code, so it was rewarding to learn a new skill and see the data all the way from the database to the UI and back - all my code. I felt great after doing a code review this afternoon to make sure I wasn’t missing anything, and we talked about some refactoring to make it better.
AI will never give you that.
No, but it can help a capable developer to have more of those moments, as one can use LLMs and coding agents to (a) help explain the relationships in a complicated codebase succinctly and (b) help to quickly figure out why one’s code doesn’t work as expected (from simple bugs to calling out one’s own fundamental misunderstandings), giving one more time to focus on what matters to oneself.
AI can help you be more agile in getting out a PoC but vibe coding always ends up eating itself and you either aren’t capable enough to fix it (because you are a vibe coder) or you spend more time on the back 9, trying to clean up the code so you don’t have so many hacks and redundancy because the AI was too literal or hallucinated fake libraries that return null or its context window expired and it wrote 5 different versions of the same function
Eh, I’ve enjoyed writing a SQL query and having AI translate it to Linq. I’ve had at least one work directly, very clear on what it’s doing, just with Linq’s odd syntax. The other query was more complicated and wasn’t something that translated well to Linq. I may have had to split that into two Linq queries.
Then again, I wouldn’t count translating psuedocode (or SQL) as really vibe coding. To me “vibe coding” means you’re not really looking at the code it produces.
It’s a changing world, and there is going to be an ever increasing amount of AI slop out there, and even more potential programmers who won’t make the leap due to the crutch.
At the same time, there are always people who want to and will learn in spite of the available crutches the latest tech revolution brings.
There will also be many good engineers who will exploit the tech for all its worth while applying appropriate rigour, increasing their real productivity and value manyfold.
And there will be many non-programmers who can achieve much more in their respective fields, because AI tools can bridge gaps for them.
Hopefully we won’t irreversibly destroy ourselves and our planet while we’re at it. 🙈
Wow, well it’s absolutely terrible at A. B is worth a shot, but it’s 50/50 to bullshit you in my experience.
Yeah - there’s definitely a GIGO factor. Throwing it at a undocumented codebase with poor and inconsistent function & variable names isn’t likely to yield great revelations. But it can probably still tell you why changing input X didn’t result in a change to output Y (with 50k lines of code in-between), saving you a bunch of debugging time.
TBH, it’s not really that great at that. Is average at best and grossly misleading and flat out wrong at worst. It may bring slight speedups for average development on boring legacy enterprise code, but anything really novel and interesting? Detrimental.
Most code on the planet is boring legacy code, though. Novel and interesting is typically a small fraction of a codebase, and it will often be more in the design than the code itself. Anything that can help us make boring code more digestible is welcome. Plenty of other pitfalls along the way though.
Fair enough, that’s true. I guess my gripe is with the narrow use case and the debugging and/or prompt/context tuning to get what you want. I still feel that if you don’t get what you want on the first try, it’s faster to write it yourself than spending time “debugging” the input and maybe get a 60% chance on correct output, which in most cases, still needs debugging. And god forbid, a framework is rewritten.
I just wished it was a bit better before we hit the plateau of diminishing returns.
Hah, yeah. Vibe coding and prompt engineering seem like a huge fad right now, although I don’t think it’s going to die out, just the hype.
The most successful vibe projects in the next few years are likely to be the least innovative technically, following well trodden paths (and generating lots of throwaway code).
I suppose we’ll see more and more curated collections of AI-friendly design documents and best-practice code samples to enable vibe coding for varied use-cases, and this will be the perceived value add for various tools in the short term. The spec driven development trend seems to have value, adding semantic layers for humans and AI alike.
help explain the relationships in a complicated codebase succinctly
It will offer an explanation, one that sounds consistent, but it’s a crap shoot as to whether or not it accurately described the code, and no easy of knowing of the description is good or bad without reviewing it for yourself.
I do try to use the code review feature, though that can declare bug based on bad assumptions often as well. It’s been wrong more times than it caught something for me.
I was finished with Windows before Microshit finished Copilot.
“Microsoft Says Copilot” is like a Two Sentence horror story for me now.
Love how they’re pretending that an LLM is useful for any task that needs precision.
Because you won’t have time to drink that coffee if you put this code into production
Writing code is the reward for doing the thinking. If the LLM does it then software engineering is no fun.
It’s like painting - once you’ve finally finished the prep, which is 90% of the effort, actually getting to paint is the reward
What a great way to frame it, I love this! I typically spend something like 60-80% of time available for a given task thinking through approaches and trade-offs, etc. Usually there comes a point when the way forward becomes clear, even obvious.
After that? Bliss. I’m snapping together a LEGO set I designed, composed of pieces I picked (maybe made one or two new ones!), and luxuriating in how it all feels, when put together.
Actually it won’t be finishing anything because code is disposable now and nobody cares what trivial app somebody can churn out
So why don’t they use it to unfuck Windows 11… before I finish my coffee?
best they can do is put more AI
I already finished my coffee too. :-/ Though I suppose I could throw on another pot while we wait.
I’ve finished several coffees since you posted this… pretty sure win11 is still fucked
It was the AI that messed it up to begin with lol. Vibe coding has often required coders having to go back and spend even more time fixing it then if they just did it themselves.
If you want it done before you finish your coffee, better tell it to start from scratch
And it will leave you debugging strange code for two weeks afterward.
where are my penguin boys at. 🐧
seriously people. the majority of you don’t have to put up with this, you know that right?
Just enjoying this popcorn.
