Vibe coding is boring

For apps that I want to ship to the world, for this website, for apps that are using an interesting tech stack, I will be driving development, because I like it, and I have enough experience to have opinions on how they should be built.

But for the apps where I just care about the final output, that’s what vibe coding is for, I suppose. I don’t ever want to rely on it so much that I lose my own skills, but it is nice getting those results faster if I truly don’t care how something works (which is rare, but I have a few projects in the pile that are finally built now, so yay). But yeah. It’s not fun. It’s just another tool in the tool belt. And it’s really boring.

This is the way we think about things that we ship. I care about the stuff that goes on the blog, so I will not use AI to write the words that go on the website.

The website though, is a different matter. I care about the technologies involved, the stack, but I don’t know enough that I can build it myself. I do care about the end product. So, AI tools are a good match here. Sure the repo may be a mess, but it works as it should. It looks as it should. And that odd enough for now.