Vibe coding - benefits and concerns

In a recent Tech for Good in Sport community exchange, the topic of VIBE CODING came up. Some no-code entrepreneurs were using it to ideate and visualise their MVPs, much to the surprise of a developer in the room... ⤵️

It sparked a conversation about how ideas and solutions are now being imagined, built and tested.

And what is now possible for entrepreneurs with non-technical backgrounds. 💡

** So what is VIBE CODING?

It’s building digital products by describing what you want and using AI or no-code tools to rapidly turn that intent into something tangible.

We’re seeing the use tools like Cursor, Replit, Lovable and Base44 to rapidly prototype platforms, dashboards, online communities, and products.

What do are vibe coders saying about the benefits?

✅ Speed to prototype.
✅ Lower cost of experimentation.
✅ More diverse (non-technical) founders able to bring to life ideas.
✅ Clearer comms between technical and non-technical teams (that then stress-test and strengthen it!)

In our world of sports innovation, women's sport, sports tech, and tech4good in sport, this feels like a breakthrough!

I've come across amazing things lately that have been created - or at least STARTED - this way.

But then, what are the concerns?

These are concerns felt both close to home (my other half is a developer and IT specialist of 15+ years!) and in conversations with sports tech entrepreneurs:

❓ Surface-level products that are not robust.
❓Security and data governance risks.
❓Undervaluing of deep technical expertise.

So, my (current) feeling about vibe coding....

Seeing what's possible definitely inspires me to experiment and grow into these no-code and prompt skills.

I also think that vibe coding is becoming a powerful "readiness" tool and is democratizing the possibility of bringing to life ideas and help test assumptions and articulate the value before taking it any further.

The vibe coding entrepreneurs from the Tech for Good in Sport reported that they still require strong technical architecture and ethical data practices, which really stuck with me and is a message that they should continue to share as part of their 'design process'.