Vibing until you make it

Written on: 2025-08-19. Last updated on: 2025-08-19.

There is a thing I forget when I was writing this post and it's that the measurement of productivity it means something totally different for us Software Engineers and Management or Executives.

Time and lines of code are fancy metrics that, used correctly, could help in a Software Project, but if you fake these numbers or play with them then there is zero value added. And that's what vibe coding and AI assistant development it's doing. You can achieve a peak of productivity but this will not be permanent and could have serious side effects

I've been reading r/vibecoding for the gossip and today someone posted this and I hope I could email some of the stories in that subreddit to all managers in the world because they are things they need to understand today.

Like it happened with no-code and low-code tools and before that with the WYSIWYG Web Builders, and before that with Software Applications like FrontPage or DreamWeaver... the hard true is that you will always need a Software Developer or Engineer to get the job done unless you're already one. And even in that case you still need help from some other Engineers because maintain Software in production environments it's not an easy task and the complexity evolves with the time and the number of users.

For us, productivity is when you deliver a feature with the lowest number of future bugs and a maintainability approach, such as documentation, code style, tests and examples. If you could do it in a range of 20% less or more of the time you estimated then that's great.

And when you work on a team, it's better to work in planned, deliverable, small features that could be delivered, tested and integrated as soon as possible. This is a lesson I learn the hard way, because I was kicked of so many good teams in the past because I couldn't do any of those things.

So for the me of the future and for the you of the present don't vibe until you make it. Make good software it's easy if you plan, build and deliver small features to be tested as quickly as you can.

So stop vibing until you make it and start making it with tools that don't make you dumb.