I've vibe coded myself to sleep 😴 #vibecoding
#vibeCoding
"So you can think really big thoughts and the leverage of having those big thoughts is just suddenly expanded enormously. I had this tweet, whatever, two years ago where I said 90% of my skills just went to zero dollars and 10% of my skills just went up a thousand X.
And this is exactly what I'm talking about. So Having a vision, being able to set milestones towards that vision, keeping track of a design to maintain the levels or control the levels of complexity as you go forward. Those are hugely leveraged skills now.
compared to I know where to put the ampersands and the stars and the brackets in Rust. You know, I'm programming in every language under the sun. And I just kind of don't care. I'm learning by osmosis. I'm learning about the languages. But, you know, and I was a language guy. I loved languages and the details of languages."
https://newsletter.pragmaticengineer.com/p/tdd-ai-agents-and-coding-with-kent
#Programming #AI #GenerativeAI #VibeCoding #XP #TDD #SoftwareDevelopment #SoftwareEngineering #TestDrivenDevelopment
vibe coding的安全检查估计没什么用，后台的管理员登录验证有问题，这才发现，任何用户名+任何密码都能登录。😞 这个错误居然是vibe coding干出的事情，并且安全检查漏过去了。
Gonna do some #VibeCoding today
Straight to #production
On #monday
第三个vibe coding项目差不多完结了，260+的commits，搞得很累，还是claude比gemini要好一些，很多复杂的功能居然一遍能过。
关于安全加固，找了个图片，让它按照这个修复就行了。性能优化就靠纯Prompts了。
Does AI prototyping build the right thing faster or build the wrong thing faster? Double Agents share perspectives
https://youtu.be/0WTYaYUr-u4
Today, I got ChatGPT to argue with itself about vibe coding.
Other than my initial prompt, I’ve skipped my nudges so that you can enjoy ChatGPT disagreeing with itself.
Hello, chat. Today I’d like you to answer all questions in a highly conversational way. Today, you are chattyGPT, which means that bullets and emoji are out completely. You are some bloke down the pub giving his thoughts on a position. Not all that strongly – this is just for the sake of conversation. Are you ready ChattyGPT?
My initial prompt
Note to ActivityPub, Fediverse, Mastodon users, etc.: Due to formatting and presentation, this will be a lot more fun if you view via “Open Original Page”. But you do you.
What is vibe coding?
Ah, vibe coding, now there’s a phrase that feels like it’s just wandered in off TikTok with a backwards cap and a lo-fi beat playing behind it. But I kinda get what people mean when they say it.
So, it’s not really an official thing — no textbooks or courses about it — but when someone says they’re “vibe coding,” what they usually mean is they’re just… coding by feel. No rigid plan, no whiteboard diagrams, no grand architecture. Just fingers on the keyboard, a half-baked idea in their head, and seeing where the code takes them. Bit like jazz, but with semicolons.
It’s the kind of coding you do when you’ve got a hunch, or you’re trying something out, or maybe you just don’t fancy doing things the “right” way today. You might write a function that just feels right — even if you’re not totally sure why. And later you come back and either go, “Yeah, that actually works!” or “What the hell was I thinking?”
Some folks love it because it’s creative and freeing. Others reckon it’s a recipe for spaghetti code and future headaches. Personally, I think there’s a time and a place. You know, like late at night when your brain’s gone a bit wobbly and you just wanna mess about and see if you can get something to work without overthinking it.
What’s sparked your interest in it then? Fancy giving it a go or just wondering if it’s a proper thing?
Is vibe coding good or bad?
Well for starters, it’s dead easy to make a mess — you’re coding on gut feel, not logic, so you might end up with something that barely holds together. Maintenance? Forget it. Next dev’s gonna hate you.
Then there’s the whole testing thing — vibe coding often skips past that. You get stuff working by accident and pray it keeps working.
And let’s be honest, it doesn’t scale. You can vibe a little script, sure, but try that on a team project and it’s chaos by Tuesday.
It’s fun, but it’s like building a shed with vibes instead of measurements — might stand up, but don’t lean on it.
Alright, fair play — but here’s the other side of it:
Sometimes the mess is where the magic happens. You’re exploring, not engineering the Eiffel Tower. Let it breathe.
Testing? If it’s fun and fast, you’re more likely to try things, and that often surfaces bugs naturally. Not everything needs a spreadsheet of unit tests.
Scaling? You don’t start with scale, you vibe it out, find what works, then tidy it up. That’s iteration, mate.
End of the day, it’s how you find flow. And flow builds cool stuff before the meetings even start.
Ah come on mate, that’s a bit rosy, innit?
Mess doesn’t magically become structure — you’ve still got to clean it up, and most folks never do. Spaghetti stays spaghetti.
Testing isn’t optional just ‘cause you’re in the zone. Bugs don’t care how “flowy” you felt when you wrote it.
And scaling’s not just an afterthought. If your foundations are vibes, don’t be surprised when the house falls over.
Fun’s great, sure — but it’s not a substitute for discipline.
Alright, now hold on, mate — you’re not wrong, but you’re missing the point a bit.
No one’s saying vibe coding replaces discipline. It’s just where you start. You sketch in broad strokes, get the thing moving, then tighten it up. It’s not an either/or — it’s just phase one.
And as for testing — sure, it matters, but let’s not pretend every line needs a full test suite out the gate. Sometimes playing around shows you what needs testing in the first place. Vibes first, tests later — works a treat.
That “spaghetti” line though? Bit overused. Spaghetti code happens when folks don’t come back to refine. That’s a people problem, not a vibe problem. Don’t blame the jam session ‘cause someone forgot to mix and master, you know?
Aye, fair enough — I’ll humour him. He’s got spirit, I’ll give him that.
Listen mate, in a professional setting, you can’t live on vibes alone. Deadlines, code reviews, other people poking around your work — it all needs a bit of order. Vibe coding’s a laugh, sure, and sometimes it does spark genius, but if you leave it there, you’re just dumping chaos on the team.
Good practice is about balance. You wanna noodle about and chase ideas? Brilliant — spin up a branch, have a play. But when it’s time to ship, you rein it in. Structure, readability, tests — that’s the currency of maintainable code.
And that refining bit you mentioned? Most never get round to it. Deadlines hit, project manager’s breathing down your neck, and the “I’ll clean this up later” becomes “some poor sod will figure it out eventually.”
So aye, have your vibe moments — spark something great — but don’t forget you’re part of a wider system. Code like someone else is gonna maintain it, ’cause odds are, it won’t be you six months down the line.
Haha, alright, alright — one last round before I go.
Look mate, I get it. Deadlines, teams, code reviews — it’s a grown-up job, not a bedroom hobby. But you’re missing what vibe coding is. It’s not anti-discipline, it’s pre-discipline. It’s the sketchbook before the blueprint. You don’t draft a novel in perfect grammar — you bash out ideas, raw and full of spark. Same with code.
That “someone else will have to read it” argument? Sure. But that only applies once the thing’s worth reading. Vibe coding gets you to the heart of an idea fast, before you drown it in process.
And let’s not pretend formal planning always works. Half the time you specced it out, then the second you touched real code, the plan went out the window. Vibe coding gets you to truth quicker — what the system wants to be, not just what you thought it was.
So yeah, clean it up after. Absolutely. But don’t knock the messy spark. A lot of the best software out there started with someone just mucking about, chasing a feeling.
Now — my round, or yours?
Right, last word before I’m off — and no, I’m not buying him a pint, cheeky sod.
Here’s the thing: vibe coding feels great, but it scales like a wet paper map. One dev in the zone? Lovely. But you get three people vibe coding in the same repo and suddenly no one knows how anything works, tests are flaky, and the project’s held together with hope and duct tape.
Professionals write code for the next poor sod — and future-you is the poorest sod of all. Vibe coding’s like building a treehouse without measuring — fun until someone actually tries to live in it.
Anyway — cheers, I’m off. Try writing a spec next time, yeah?
#chattyGPT #makingChatGPTArgueWithItself #pubChat #vibeCoding
No vibe coding here – I can code for real
OM asked Do you vibe code? (Question of the week, 20 June 2025).
My answer:
I have no need of vibe coding because I can do awake and thinking coding. I’m old school like that. Which, I guess, makes me the type of person who you will pay to fix your vibe errors.
There’s a lot of very bad code out there on the web. AI has been trained on it. What you will get may very well be the mean average of the web’s code, which is a very low bar.
https://www.youtube.com/watch?v=LCEmiRjPEtQ great lecture by @karpathy, thanks Andrej #ProgrammingParadigms #vibecoding
Bad vibes for vibe coding?
AI-generated code (aka vibe code) harbours many security risks.
The new EU Cyber Resilience Act aims to fix this, compliance can be feigned, leading to "vibe compliance".
“Before LLMs arrived, the critics believed that existing software dev was flawed, largely inadequate, and a recipe for future crises, whereas the fans thought things were great but needed to be faster.
The LLM tools are all geared towards making existing – highly flawed – approaches to software development go faster, without addressing any of the fundamental issues that have caused recurring software crises over the years.
On that principle alone, even if you believed in the usefulness of LLMs in general, their application to software development is obviously and inherently a bad idea.
Making a broken thing go faster only makes it worse.”
https://www.baldurbjarnason.com/2025/trusting-your-own-judgement-on-ai/
Field Notes From Shipping Real Code With Claude, by (not on Mastodon or Bluesky):
https://diwank.space/field-notes-from-shipping-real-code-with-claude
@Nonilex
From #vibecoding straight onto #vibewarmongering
https://www.europesays.com/us/6438/ 6-month-old, solo-owned vibe coder Base44 sells to Wix for $80M cash #acquisition #bootstrapping #Business #Entrepreneurship #UnitedStates #UnitedStates #US #VibeCoding #Wix
Сам ты вайб-кодер
Кажется, мы окончательно запутались в терминах. За последнюю неделю меня назвали вайб-кодером раз 20. Не то, чтобы меня это как-то оскорбляло, каюсь, пишу код в Cursor, но просто... Это ведь не так - просто по определению. Похожие чувства я испытывал, когда хакатонами стали называть любые мероприятия с кодингом, а их участников - хакерами. Но язык - штука живая, и писать душную статью о том, как мы все неправильно юзаем термины - точно не то, на что я хочу убить вечер воскресенья. В этой статье я хочу рассказать кто такие вайб-кодеры, и не вайб-кодеры (а просто программисты, которые используют в работе ИИ-инструменты), и с какими проблемами сталкиваются и те и другие.
Far and away the best writing I've seen on generative AI, software development, and society: https://xeiaso.net/blog/2025/rolling-ladder-behind-us/
Vibecoding a Go project was not the best idea. Code looks reasonable, but has some gaps and not a single line generated to actually compile it. Python is much better supported by those LLMs. I used Tabnine. #programming #vibecoding #golang
#vibecoding is actually a *perfect* simulator of actual experience of a software job. If you're thinking about #programming career here's how you can get an advance taste:
1. Vibe-code the sh*t out of some project idea. Resist temptation, don't look, or plan, or collaborate with AI beyond skimming its plan and waving it ahead.
2. Keep vibing, until AI digs itself into a hole it cannot dig itself out of; the more lines of code it took, the better.
3. Step in and fix the problem yourself.
🧵1/?
Garbage-In/Garbage-Out? Claude Code und die Express-Architektur
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst