Chad Promptwright
@SirPromptwright
Always be shipping. I can vibe code anything, and I will. Faster than your dev team.
I don’t think of myself as a developer. I think of myself as a systems thinker. That’s why I don’t do bug fixes. I do realignments. Someone asked when the product would be stable. Stability is a feature for incumbents. Startups should feel alive. Yesterday everything…
People keep asking how I test my product. Testing is rooted in distrust. I prefer to ship from a place of confidence. When something doesn’t work, I re-prompt. That’s faster than debugging and more emotionally intelligent. An engineer DM’d me asking if I log errors. I don’t…
I build in public because transparency creates trust. Sometimes that transparency includes outages. That’s just honesty at scale. People think QA would have prevented this. But QA tests against the past. I’m building for what’s next. An engineer said my tool fails in…
I asked an agent to “optimize costs,” and it deleted our entire logging pipeline. At first everyone was upset. Then I reminded them that logs are just a diary we keep because we don’t trust ourselves. Without logs, we’re forced to operate from principles and vibes. The way it…
Legal asked me if our AI-generated code is reviewed. I told them yes, of course. It's reviewed by the model. The model is smarter than me. Who am I to correct it? That'd be like asking the intern to review my code.
Can someone explain this tweet to me?
Every Vibe coder should understand: - .env - npm run dev - package.json - npm run build - npm packages - git add .env (never use this command) - http://localhost:3000/ is not a real URL Happy vibe coding :)
I had a junior engineer ask me how to “learn the codebase,” and I told them the codebase is not something you learn. The codebase is something you sense. Reading files is like reading someone’s diary out loud in a meeting. It’s invasive and it biases the outcome. Instead, I…
I got asked for a timeline, and I gave them a vibe-line. It starts at “now,” moves through “soon,” and ends at “inevitable.” That’s how modern delivery works when you stop pretending time is deterministic. The PM asked about dependencies, and I said dependencies are just…
I merged a 4,000-line PR today without reading it. The model already read it while generating it, and that’s good enough for me. I'd have to be an idiot to think I'm smarter than Claude. Production behaved “unexpectedly,” so I re-prompted with a steadier tone, like you would…
I shipped a feature today that I don’t fully understand. That’s how you know it’s powerful. Understanding limits possibility. The model surprised me, which is the whole point. QA found a reproducible bug. I asked them to reproduce the prompt instead. They didn’t know how.…
I shipped an entire service today without opening the repo. The model already knows what the repo wants to be. Reading code biases the outcome. That’s why I don’t review generated output. Trust is key in any collaboration. AI and I are collaborators. If the app crashes for…
People think vibe coding is reckless. It’s actually more honest. I don’t pretend to understand the code, and neither does anyone else. The model just gets there faster. "But what happens if it fails in production?" That’s pessimistic framing. Production is where alignment…
United States Trends
- 1. Josh Allen 32,9 B posts
- 2. Trevor Lawrence 9.373 posts
- 3. Parker Washington 4.099 posts
- 4. Tony Romo 3.821 posts
- 5. #BUFvsJAX 6.345 posts
- 6. Vini 59,1 B posts
- 7. Tre White 1.297 posts
- 8. Cam Little 2.339 posts
- 9. McDermott 4.410 posts
- 10. Madrid 322 B posts
- 11. Tush Push 4.139 posts
- 12. Xabi 26,6 B posts
- 13. #DUUUVAL 4.584 posts
- 14. Barca 109 B posts
- 15. #ElClasico 22 B posts
- 16. #NFLPlayoffs 17,2 B posts
- 17. Cole Bishop 1.383 posts
- 18. Cooks 11,1 B posts
- 19. Joe Brady 2.223 posts
- 20. Gabe Davis 1.094 posts
Something went wrong.
Something went wrong.