Vibe coding is cool — and in my eyes, a blessing and a curse at the same time.
It’s impressive how quickly tools can come into being today. I’ve done it myself several times over the past few months: idea → prompt → it works. Well, it’s usually not quite that simple — still: thanks to AI, I can do things that would have been out of reach for me before.
And that’s also the curse: if everyone can build small tools themselves — which is genuinely cool and often useful — who thinks about the structure and the big picture?
Vibe coding reminds me a bit of the much-loved Excel tools in companies. The simple development platform that lets anyone quickly build a small helpful tool. AI takes that to a whole new level. The basic problem remains: who takes care of the glue between the tools and the information? The information architecture that holds the whole thing together?
I believe that information architecture — if it was ever unimportant — is becoming more important than ever right now:
- Because it is the digital glue that holds the company together.
- And because, incidentally, it is what makes many AI-powered applications possible in the first place — where data and information are garbage, not even an AI agent can save much.
Vibe coding democratizes tool building — and that is exactly where both the blessing and the curse lie. The easier it becomes for everyone to create their own tools, the more important an information architecture becomes that holds those tools and their data together.