vibecoding.com

cloudflare

Why I bought vibecoding .com for a big idea | Dharmesh Shah posted on the topic | LinkedIn

Why did I pay six figures for VibeCoding .com? There are generally 3 reasons I buy an ultra-premium domain name: 1) I am working on a project and I try to find the absolute best domain I can for *that* project. 2) I have a "someday..." idea and buy a domain to add to the collection of projects I'll probably never get to, but hope springs eternal (entrepreneurs out there, you know the feeling). Let they who have not bought such a domain leave the first snark comment. 3) There is an idea/concept that I think could be really big and I find the definitive domain name for that idea. In the case of vibecoding .com, it fell into the 3rd bucket. Vibe Coding as a concept is taking off -- and I'm a daily beneficiary (I spent most of this weekend vibe coding a couple of new agents). Though this was originally on a whim, I do now have an idea of what could be done. It was inspired by Jason M. Lemkin and his adventures in vibe coding. Here's the thing: There are two kinds of folks (broadly) that will do vibe coding. Some will be like Jason. Smart, determined and curious -- but not professional developers. They are business builders with an idea. Then there are people like me: Professional software developers (I've been writing code for 30+ years) that use vibe coding as a way to get leverage. Not just for the 20% bump that simple "autocomplete inside an IDE" gives you, but the 10x - 20x leverage that agentic approaches to building software products gives you. In any case, the non-devs are going to have is that vibe coding will be super-exciting in the beginning. You get the thrill of something working and the further thrill that comes from *others* getting value out of something you built. But, here's the thing. There's a decent chance that somewhere along the way, the AI will take a wrong turn. Sometimes so subtle that even a pro developer might not see it if they're not paying attention. This "one wrong turn" happens again. The product still works. And maybe you backtrack a little to get on the right/better path, but eventually, you're going to hit a dead-end. This is the deciding moment. Do you find a way to push through, spending hours and hours meandering through the dark woods of a code base you didn't write? Or do you trash what you have, and start fresh with a cleaner approach now that you have a better sense of things? So here's the idea: A Community for Vibe Coders. The free version of the community lets you browse and learn from other people. But, the paid version lets you post your question/issue (maybe even your GitHub repo) and get professional help. And here's the kicker: The professional developers that are there get paid. It's a marketplace. What do you think? Note: I did not coin the term vibe coding. Andrej Karpathy gets full credit for that. I'm a huge fan of his (along with millions of others). Andrej: If you ever want the domain for a project you have in mind, hit me up. | 207 comments on LinkedIn

Not available

13 hours, 31 minutes ago