Vibe coding boosts your services

Vibe Coding: Level up

Even today, social networks are buzzing with “AI yes / AI no” debates for code production.
Personally, I made my decision a few months ago: rather than fighting it, I decided to embrace vibe coding 100%.
In short: working hand in hand with AI, without denying my development fundamentals.

New Reflexes to Master

Switching to vibe coding mode means learning new skills:

The art of prompting: saying just enough for AI to understand exactly where I want to go.
Solid tooling¹: linters, type-checkers, Prettier: no freedom is the key.
Always being able to go back²: stash, commits, file copies: no question of losing a single line.
Implementation / refactoring rhythm: alternating without getting stuck in one or the other.

Result? A factor of x1.4 to x3 on my dev speed, depending on project size. The bigger it gets, the more the boost levels off…
(and AI, let’s be honest, remains lost when it comes to aesthetics or pixel-semi-perfect integration.)

Automation: From Myth to Daily Life

We all started by dreaming of the magic tool that would do the job for us.
Often, it ends up as a shaky script, abandoned in a “to finish” folder.
With experience, I had understood that “doing the task by hand is faster”.

Then, this weekend, revelation: what if the combination of AI + upgraded skills finally changed the game?

Spoiler alert: yes.

Moving to Action: Creative Chaos

Weekend challenge: transform SEO verification (titles, descriptions, hreflang, h1-h6 hierarchy, 404s, etc.) into a simple formality for my clients’ content sites (L to XL), with a custom Chrome extension.

Crawl all internal pages.
Analyze on each page: metadata, 404 errors, over- or under-sized tags…

In half a day, I deliver a functional first draft… and a big mess:
a single 2,000+ line JS file.

I breathe, I refactor: TypeScript modules, separate crawl logic, unit tests, vite packaging³.
Cherry on top: the Vibe Coding Fixing Report.
A markdown report ready to be corrected, assisted by AI.
The chore transforms into a clean-up sprint.

Gaining Impact, Opening the Field

I don’t plan to commercialize the extension; the objective was elsewhere:
Immediate added value for my clients:

Integrated SEO quality control.
New horizons: if I can automate this, I can automate many other pain points.

Efficiency and quality rise, which allows my daily rate to increase a bit.
In short, vibe coding isn’t magic: it’s lab work + a bit of controlled chaos.

To be continued…

PS: I still don’t think “vibe coding” is a tool for non-coders, but it can help you discover the coder sleeping within you.

What it’s look like

Extension in action 1 Extension in action 2 Extension in action 3

Explanations for the incomprehensible stuff

Solid tooling: Imagine assistants that monitor your code permanently. Linters (like ESLint or Ruff) are automatic proofreaders that spot mistakes and bad habits. Formatters (Prettier, Black) are like assistants that automatically reformat your text – spaces, indentations, everything becomes uniform. Type checkers verify that you’re not trying to put a word where you need a number, avoiding silly bugs. ↩
Going back: Think of Google Docs with an ultra-powerful version history. Stash is like temporarily setting aside your modifications to work on something else, then retrieving them later. Commit is like taking a photo of your work at a given moment – you can always go back to any previous “photo” if something goes wrong. ↩
Pro refactoring: It’s going from a messy apartment to a tidy apartment with dedicated rooms. Modules break down code into specialized “rooms” – one for collecting data, one for analyzing it, etc. Unit tests are like automatic quality controls that verify each piece works well. Packaging takes all the necessary little bits of code and creates an optimized version for the machine. ↩