Vibe Coding and the Quiet Erosion of Craft

In the rush of excitement around AI-assisted development, a new pattern has emerged in the engineering world: vibe coding. It’s the habit of throwing half-formed ideas at an AI, getting back functional code, tweaking it a bit, and shipping. Fast, convenient, efficient, and undeniably powerful.

But as more developers lean into this new workflow, one question keeps echoing in my mind:

What happens to our sense of style when the machine does the crafting?

We often talk about software development as if it's purely technical, a matter of logic, syntax, and architecture. But anyone who has spent real time building things knows the truth: coding is a craft.

It’s closer to writing, painting, or even singing than we admit. And like every craft, it carries something deeply human.

Where style comes from
When you’re learning any craft, everything feels structured at first. You follow patterns, learn the rules, and practice under the guidance of masters and mentors. Whatever the craft, the early stages of learning are all about imitation.

You imitate. You repeat. You absorb.

And then, with time, something shifts.

As you grow, you stop simply following the established way of doing things, and you start expressing something of your own. You develop taste, small but intentional decisions about patterns, flow, and emphasis. Your work starts to carry your fingerprint; the choices you make become recognizably yours.

That’s true in every craft, and coding is no different.

When I was starting as a developer, I could identify my mentors’ code just by reading it. It wasn’t just correct; it had character. It had a rhythm, a consistency, a tone. The architecture reflected their priorities. The comments reflected their thinking. Even the variable names hinted at their voice.

This individuality, this style, isn’t decoration. It’s how a craft grows. Different approaches collide, influence each other, and eventually blend into new norms. That’s how entire industries move forward.

What Happens When All Code Starts Looking the Same?

AI tools are incredible, game-changing even. But if we're not careful, they can flatten the craft.

When thousands of developers rely on the same model to write their code, we risk generating a homogeneous output. Same conventions. Same structure. Same patterns.

Imagine if every song had the same melody.
If every novel used the same voice.
If every painting had the same brushstroke.

What would we learn from?
What would we be inspired by?
Where would creativity evolve from?

If AI becomes the default author, we may lose the subtle differences that spark innovation. Code becomes not an expression of thought, but an output of probability.

And then… what do beginners even study? What do they model themselves after? Where do they find their taste?

Style and Taste matter

Your taste, that intuition for what “feels right", is shaped by the hours you spend wrestling with a problem. Fixing bugs, refactoring code, overthinking names, and obsessing over tiny details no one else sees.

That process is not wasted time.
It’s the shaping of your style.
It’s the formation of your craft.

If we skip that journey entirely and let AI fill in the gaps, we risk becoming mechanics instead of creators, implementers instead of thinkers.

AI is a tool, a powerful one. But tools were made to extend craft, not erase it.

I believe you can use AI to accelerate repetitive work, explore new patterns and learn unfamiliar concepts

But don’t outsource your taste.

Don’t skip the uncomfortable parts.
Don’t avoid the mistakes that shape your intuition.
Don’t give up the voice you develop through practice.

Craft survives when the creator stays present.

The future of coding still needs humans with style. The beauty of software comes from the fact that real people make it. People with experiences, with instincts, with imperfections that lead to innovation.

AI can help us build faster. But only we can build with soul.

So maybe the real challenge of this era is not whether AI will replace us but whether we will allow it to replace our individuality.

Because coding is not just problem-solving.
It is creation.
It’s a craft.
And crafts are meant to be honed, not outsourced.