Lately, I’ve been thinking a lot about something I’ll call “vibe coding.”
You know that feeling... you have an idea, you open up your editor, maybe pull in some AI help, and just start building based on momentum rather than a fully thought-out plan.

Sometimes it works incredibly well. Other times… not so much.

Here’s how I’m currently thinking about the pros and cons.

Pros

1. Getting unstuck quickly - When you have an idea but don’t know where to start, vibe coding is honestly one of the best ways to break through that wall.
   Instead of overthinking architecture, you just start. Momentum builds fast, and suddenly you have something tangible.
2. Quick solutions - Not everything needs to be a perfectly engineered system.
   If you’re solving a one-off problem, building a small tool, or automating something simple, vibe coding is often the fastest path from idea → working solution.

Cons

1. It can make you lazy - Let’s be honest... when things come together quickly, it’s easy to skip the deeper thinking. You might avoid planning, documentation, or even understanding what’s happening under the hood.
2. Messy code - What starts as “just a quick project” has a funny way of sticking around. Vibe-coded projects can turn into spaghetti fast, unclear structure, inconsistent patterns, and code that’s hard to maintain or scale.

So... is vibe coding good or bad? I don't think it's either. I think of it as a tool. Used intentionally, it can be powerful... Used carelessly, it can cost you more time later.

Let me know what you think, I am curious how others are approaching this. Do you lean into vibe coding or do you avoid it?