Yes, there will be vibes. Yes, there will be coding.

These can be separate, or they can come together into something really unique and interesting.

I've been delving into recently with fun results with hackertuah and notes-analyzer, and my spelling game. These are some small, quick projects that came together quickly because of vibe coding.

I quipped in April about in Vibe Coding Beginnings. I had thinking about it more in depth since some friends and I were chatting about this over coffee one day. We were lamenting that LinkedIn influencers were going haywire about this “vibe coding” thing, and it was getting obnoxious. Which is true, it is getting overkilled by many online.

I agree with Simon here – publishers of these books on vibe coding are probably doing a disservice to the up-and-coming programmers, and those who just want to solve quick small problems with a computer, without having to think about the code at all.

But there is a kernel of something valuable here. I think what we’re missing is there are software engineers who know how to code who use AI, and there are folks who being brought into “software engineering” with this “Vibe Coding” thing. With the latter, the barriers are lower, the language of the noun is more welcoming which matters a lot when you’re starting out.

I think it matters who we’re talking about when we talk about vibe coding. Is it the absolute beginner who’s never programmed before? Is it the junior software engineer? The senior or more engineer? Because if you outline who the audience of this is, it changes what we’re talking about.