()=>{}

With Vibe Coding it’s the same as with Agile: a reasonable idea gets ruined by misunderstanding, and this gets worse as the hype continues. This may happen if an idea is applied blindly, or even forcibly, and the result is far from what was anticipated. Losses instead of profits, and so on. Is it still not too late? First, let’s try to understand what Vibe Coding really is. We can find an informal definition on Wikipedia. By Vibe Coding, we mean a completely different approach to coding: a chatbot-based approach rather than an assistant-based one. The developer no longer works with the code directly, but rather develops via a series of prompts, letting the GenAI agent provide the implementation. The...

When interviewing new candidates for the software architect position, I like to start with a few awkward questions, such as “What is architecture?”, “Who is an architect?” and “What do you do?”, before waiting for the ensuing moment of disbelief and long silence. Maybe some of them will try to beat the system by using these two rectangles and a barrel. Yes, I was there too. There are perhaps two reasonably correct answers to these questions. By “correct”, I mean “simple”, because a simple question deserves a simple answer. The first is that the architect is the most senior person on the team and knows about the things and how to avoid the traps. It’s just common sense. However, this...