A
New Way of Building
Over the last year there's been a new
term in the product teams, marketing departments and developer forums: vibe
coding. This is not a phrase that was coined in some corporate roadmap or a
software release note, but rather it is a phrase that was used by people. The
phrase wasn't coined in some corporate roadmap or software release note, its a
phrase used by people. It came from the human method of working which is to
start with the building of things as it is done today; with a conversational
prompt to provide working code instead of typing each line. Vibe coding is a
change that marketers who formerly thought that coding was a locked door for
engineers and techies who have been coding for years will have to understand
instead of ignoring.
What
Vibe Coding Actually Means
Vibe coding is essentially Natural
Language Programming (NLP) using large language models (LLMs) to generate
software. A person describes what he would like the program to do; the model
writes the program line by line; he provides the model with feedback on the
program; the model changes the program; he provides feedback again; the program
is changed again; and so on, until the program matches the intended outcome.
What's interesting is the informal nature of this process captured in this
term. There is a more flexible approach to the planning, with trial and error,
rather than a blueprint that is adhered to from the beginning. It is by no
means a poor job. That it's a different workflow and the individual controlling
the flow more involved in assessing and improving the situation than in typing
raw syntax.
Why
It Matters for Marketers
It's an important change for marketers
as it makes it easier to go from idea to test. Campaign landing pages,
interactive calculators, basic dashboards and internal tools, which used to
need someone with a developer ticket and a few weeks’ wait, are now able to be
prototyped by anyone on the marketing team. Now a campaign manager doesn't have
to wait for engineering bandwidth to test this hypothesis that an interactive
quiz can help drive conversions. They can tell stakeholders a day later what
the quiz is, create a working version of it, and show it to stakeholders within
the day. It doesn't mean that complex or production systems will skip the need
for complex or production developers, but it does mean that different people
will be involved in building and testing other systems in the early stages.
A
Note of Caution for Marketing Teams
However, users of vibe coding should
not assume that code generated by the coding should necessarily be trusted.
While a prompt that results in a functional looking webpage may indicate
security, accessibility and performance capabilities, it is not a reliable
indicator. Before any of these come in contact with a customer's information,
or implemented on a scale, marketing teams trying them out, should consult with
technical teams. The worth of vibe coding is that it provides marketers with almost
as fast iterations and reduces internal instruments friction, as opposed to
completely avoiding engineering management.
The
View from the Engineering Side
There are other factors to take into
account when tech professionals are concerned. It's tempting for many
developers to take a skeptical look at vibe coding, and for some reason, that's
not a bad approach. Conversational prompting can create subtle bugs,
inconsistent architecture and security holes which are not apparent at first
glance from the code. Remember, a senior engineer reviewing AI-generated code
should treat the code as he or she would do when reviewing a pull request from
a junior engineer, and perhaps more so because the AI model might not always be
aware of a codebase's broader context, its requirements, or the requirements
for long term maintenance.
Where
the Technique Genuinely Helps
On the other hand, if someone is
working with software on a daily basis and doesn't use any vibe coding that
would be a bad idea. It is a very useful technique in certain situations:
quickly creating a prototype, when you are playing with a new API, when you
need to create boilerplate code that you will later customize, or to create the
initial version of a script, which is then further developed by a human.
Readily used tools can eventually become an effective and quick collaborator
for experienced developers, but only if they learn to use them effectively.
They still look at the generated code, line by line, they still test it
thoroughly, and they still use the architectural thinking that you can't get a
model to do everything by itself. Vibe coding is most useful for professionals
who have a good amount of knowledge about what good code looks like; those
people can "catch" what vibe is missing with such knowledge.
Vibe
Coding Market
As I was investigating the path of this
tendency, I stumbled upon an eye-catching projection that gives the size of
this change perspective. According to a report by Roots Analysis the global vibe-coding market
is expected to increase from USD 2.96 billion in 2025 to USD 325 billion by
2040, at a compound annual growth rate (CAGR) of 36.79% for the forecast period
of 2025-2040. That's a growth curve that is more than a passing interest in a
new development style. It believes that an AI-powered, conversational coding
process will become more ubiquitous than it is today and will be used across
industry, not just by hobbyists or early adopters. It's a clear example that
marketers and tech people should engage with the vibe-coding norm and best
practices before they solidify to avoid the possibility of it becoming a
forgettable flash in the pan.
The
Cultural Shift Inside Organizations
A cultural element should also be taken
into account. Software development is becoming more accessible thanks to vibe
coding, and it's altering expectations from as far as the organizations
themselves are concerned. Non-technical people are beginning to take it for
granted that it is easy and inexpensive to build, due in part to the fact that
it is in some cases. This sets up opportunity and conflict. Product and
engineering leaders might have to deal with a greater number of requests from
colleagues who created a functioning prototype on a weekend and have high
expectations of having the product ready for production by the end of the week.
Having to manage these expectations, requires clear communication of the
difference between a demo that functions in an isolated fashion versus a system
that needs to scale, integrate with existing systems, and stand up in real
world scenarios.
Principles
for Responsible Adoption
When considering the implementation of
vibe coding, there are some principles that tend to make the difference between
a successful and a chaotic implementation. Teams that take AI-generated code
and don't stop there are less likely to suffer from the worst-case scenarios.
Even if the original draft is written by a team, those teams that have a code
review system discover issues early on before they can make their way to
customers. And teams that invest effort into training technical and
non-technical team members on the benefits and drawbacks of such tools are more
likely to reap greater rewards in the long-term, rather than experiencing a
cycle of enthusiasm and frustration.
The
Bottom Line
Vibe coding isn't a fad or the complete replacement of software development. It is a new dimension in people's interaction with code, a dimension that makes it possible to involve more people in the early phases of developing an artefact yet based on a deep level of experienced judgment to see through the development and make it usable. Marketers get a quicker development process from ideation to prototype. Tech users get a tool they can use to speed up some aspects of their job and so long as they apply the same diligence as they do to any other code source. The ability to know when this technique works, and when it doesn't, will distinguish those teams that apply the technique effectively, from those that just follow the fad.