Vibe coding's hardest part isn't the code. It's the jargon.

Draft: Zain's voice pass pending. Adapted from a LinkedIn post; he reviews before this publishes.

The first time I opened Cursor and then Claude Code, the code itself wasn't what stopped me. It was the vocabulary around it: Deploy. Commit. Push. Pull. Dense documentation that assumes you already speak the language. As a designer, I didn't.

So I started building unjargon — a tool that explains dev terminology through analogies designers already understand. Not "what is a commit" in Git's own terms, but "a commit is saving a version of your Figma file with a note on what changed."

What actually happened once the jargon cleared

• Raised my first pull request.
• Worked with real code, not a prototype pretending to be one.
• Connected a live database for the first time.

None of those were about learning to code faster. They were about removing the one barrier that had nothing to do with logic and everything to do with unfamiliar words.

The takeaway

"Vibe coding" gets sold as effortless. It isn't — the tools got easier, but the language didn't. If you're a designer circling the edge of this the way I was, the fix isn't a coding bootcamp. It's a translator.