Vibe coders, why are we doing this?

@codingai

50.0K followers · usually 1.4K views a post

Views

99.0K

Likes

4.9K

Comments

161

Shares

442

Why it worked

The video uses a provocative hook that challenges a popular trend in the developer community, positioning the creator as an expert offering a more professional, efficient alternative.

Summary

The creator critiques the common practice of using multiple disparate services for a software stack, suggesting instead that developers consolidate their infrastructure on a single cloud platform. He explains how using 'infrastructure as code' with AI can simplify management and improve professional development practices.

Structure

1Critique of the 'vibe coder' stack
2Explanation of why multiple touch points are problematic
3Recommendation to use a single cloud provider
4Introduction to infrastructure as code
5Final takeaway on professional engineering standards

On-screen text

Vibe coders This is wrong! Claude for coding. Supabase for backend. Vercel for deploying. Namecheap for domain. Stripe for payments. GitHub for version control. Resend for emails. Clerk for auth. Cloudflare for DNS. Posthog for analytics. Sentry for error tracking. Upstash for Redis. Pinecone for vector DB. You can literally launch a startup from your laptop and Internet. It's not that deep bro. Infra as Code

Original caption

The "Vercel + Supabase + Stripe + Claude API" stack is not a stack — it's a Frankenstein. Big-tech move: pick ONE cloud, draw your system, snapshot it, let Claude write the infrastructure-as-code. One bill. One account. One way to think about it. #vibecoding #aws #claudecode #softwareengineering #infrastructureascode #buildinpublic

More from @codingai

Their other posts in the index, biggest breakout first.

Transcript

Vibe coders, why are we doing this? You're giving yourself so many touch points and it's just harder to manage. Ask your software engineer friends, would you do it like this? No way. What I would recommend instead is looking into one of the cloud platforms, AWS, Google Cloud, or Azure. I would stick with one cloud provider, then take a snapshot of this and tell your AI, I need all these things in Azure. Your AI will write a single file for you. It's called infrastructure as code and then boom, you're set up in your account. No more dependency mess. And now you're thinking like a real software engineer.