So I recently heard of "vibe coding" and was skeptical.
I've been playing with it tonight.
I'm still skeptical, but intrigued.
#Tag
So I recently heard of "vibe coding" and was skeptical.
I've been playing with it tonight.
I'm still skeptical, but intrigued.
Reprise de l'image postée par @JordiCabot mais avec le #AltText (et adaptée en français)
https://fediscience.org/@JordiCabot/115281463461537273
Reprise de l'image postée par @JordiCabot mais avec le #AltText (et adaptée en français)
https://fediscience.org/@JordiCabot/115281463461537273
🚨 The nightmare scenario for anyone coding with LLMs in a serious way.
「 Siemiatkowski recently appeared on the podcast Sourcery, where he revealed his new hobby of cosplaying as an engineer, using AI tools to write code and then bringing those ideas to the desks of the people he pays to do that job. On the episode, the CEO admits he’s never coded before, but he started using the AI-powered code editor Cursor 」
👩🏻💻 AI Coding / geohot
「 That anyone uses LLMs to code is a testament to just how bad tooling and languages are. And that LLMs can replace developers at companies is a testament to how bad that company’s codebase and hiring bar is. AI will eventually replace programming jobs in the same way compilers replaced programming jobs. In the same way spreadsheets replaced accounting jobs 」
https://geohot.github.io//blog/jekyll/update/2025/09/12/ai-coding.html
"Vibe coding" is an euphemism for "automated spaghetti".
Engineering has always used all kinds of automation wherever possible, from parsers, pre-processors, assemblers, and compilers, to generators, linters, verifiers, and memory checkers. It's always been code producing code, hopefully helping to produce better code. When you follow engineering principles and develop something reliable, extensible, maintainable, and sustainable, that's still engineering, independently of whatever form of automation you used.
"Vibe coding" places an emphasis of rapid and not always orderly, reasoned, or principled design. Just getting things done fast, which only helps to create more spaghetti code, bigger attack surfaces, and accelerating unsustainable complexity.
I'm afraid we're going to see a lot more business people pretending they saved money creating code that will be impossible to fix.
There's one big complexity wall we're all gonna hit against in a year or two if they keep going down that road.
#vibecoding #code #coding #dev #webdev #software #softwaredevelopment
👻 Vibe Coding Cleanup as a Service
「 The Vibe Coding cleanup market is growing rapidly, though exact numbers are hard to pin down. What we know: Gartner predicts 75% of enterprise software engineers will use AI code assistants by 2028. If even a fraction of those projects need cleanup - and current data suggests most will - we’re looking at a massive emerging market 」
https://donado.co/en/articles/2025-09-16-vibe-coding-cleanup-as-a-service/
👩🏻💻 AI Coding / geohot
「 That anyone uses LLMs to code is a testament to just how bad tooling and languages are. And that LLMs can replace developers at companies is a testament to how bad that company’s codebase and hiring bar is. AI will eventually replace programming jobs in the same way compilers replaced programming jobs. In the same way spreadsheets replaced accounting jobs 」
https://geohot.github.io//blog/jekyll/update/2025/09/12/ai-coding.html
🙄 Amateurs Using AI to “Vibe Code” Are Now Begging Real Programmers to Fix Their Botched Software
「 "Most of these vibe coders, either they are product managers or they are sales guys, or they are small business owners, and they think that they can build something," Sohni told 404 」
https://futurism.com/vibe-code-real-programmers-fix-software
🚨 The nightmare scenario for anyone coding with LLMs in a serious way.
「 Siemiatkowski recently appeared on the podcast Sourcery, where he revealed his new hobby of cosplaying as an engineer, using AI tools to write code and then bringing those ideas to the desks of the people he pays to do that job. On the episode, the CEO admits he’s never coded before, but he started using the AI-powered code editor Cursor 」
"Vibe coding" is an euphemism for "automated spaghetti".
Engineering has always used all kinds of automation wherever possible, from parsers, pre-processors, assemblers, and compilers, to generators, linters, verifiers, and memory checkers. It's always been code producing code, hopefully helping to produce better code. When you follow engineering principles and develop something reliable, extensible, maintainable, and sustainable, that's still engineering, independently of whatever form of automation you used.
"Vibe coding" places an emphasis of rapid and not always orderly, reasoned, or principled design. Just getting things done fast, which only helps to create more spaghetti code, bigger attack surfaces, and accelerating unsustainable complexity.
I'm afraid we're going to see a lot more business people pretending they saved money creating code that will be impossible to fix.
There's one big complexity wall we're all gonna hit against in a year or two if they keep going down that road.
#vibecoding #code #coding #dev #webdev #software #softwaredevelopment
🎈 Coinbase CEO explains why he fired engineers who didn’t try AI immediately | TechCrunch
“I jumped on this call on Saturday and there were a couple people that had not done it. Some of them had a good reason, because they were just getting back from some trip or something, and some of them didn’t [have a good reason]. And they got fired.”
The Month of AI Bugs 2025 https://lobste.rs/s/cr9eqw #security #vibecoding
https://monthofaibugs.com/
The Month of AI Bugs 2025 https://lobste.rs/s/cr9eqw #security #vibecoding
https://monthofaibugs.com/
I think the Vibecoding reddit has accidentally stumbled on the best description of vibecoding:
It's "roleplay for guys [it is always guys] who want to feel like hackers without doing the hard part".
A space for Bonfire maintainers and contributors to communicate