Intranets Today

“I coded with Vibe Coding AI for two weeks. Here’s the honest tea.”

I’m Kayla, and I build little apps for folks who don’t like boring tools. I tried Vibe Coding AI inside VS Code and my browser for two weeks. It felt like pairing with a chatty junior dev who reads docs fast, but sometimes guesses. Helpful? Yes. Perfect? Not quite. Let me explain.
If the term “vibe coding” is new to you, that quick primer lays out the philosophy in a few sentences.
If you’d like the full diary-style breakdown (with every late-night aha! and face-palm moment), I posted it over on I coded with Vibe Coding AI for two weeks—here’s the honest tea.

What this thing is (and how it fits)

Vibe Coding AI sits in VS Code as a side panel and a little inline helper. It can:

  • Chat about your code with context
  • Write snippets as you type
  • Explain errors in plain words
  • Draft tests, docs, and even Git commits

It also runs in the browser, which helped when I reviewed a repo on GitHub. I liked the split view: code left, help right. Felt tidy.
For more on how Vibe compares to other assistants you can run straight from your editor, check out my desk-side rundown, The best AI for Vibe Coding (from my desk, tea in hand).

You know what? Setup was simple. Sign in. Pick the folder. Done. No weird YAML dance.

Real work I shipped with it

If you’re curious how a CTO-level perspective differs from mine, there’s a fun leadership spin in I tried Vibe Coding AI CEO for a week—here’s how it felt.

1) A tiny Flask API (with a CORS snag)

I had to spin up a “hello” API for a dashboard. I asked, “Make Flask app with /api/hello that returns JSON.” Vibe gave me:

  • app.py with a route
  • A quick test using pytest
  • A basic Dockerfile and a .dockerignore

It even explained how to run it:

  • pip install flask pytest
  • flask run

I hit a CORS error from my React front end. Vibe saw the error in the terminal and said, “Add flask-cors.” It gave me:

from flask_cors import CORS
CORS(app)

It worked. Took 12 minutes, coffee included. I smiled. Simple wins feel big on a Monday.

2) A React table that didn’t fight me

A client needed a table with a sticky header, sort on click, and keyboard nav. I asked, “React component with sticky header, Tailwind, sort by name and date.” Vibe drafted a clean component, used useState for sort state, and added aria-sort for screen readers. Nice touch.

Bug time: on mobile, the header clipped. Vibe guessed the fix with overflow-x-auto and top: 0 sticky styles. I still had to tweak the z-index. No big deal. The speed boost was real.

3) The regex that cooks phones (the numbers, not the gadget)

I’m bad at regex when I’m sleepy. I asked for a pattern that grabs US phone numbers and strips weird stuff. Vibe gave:

/(+1[-.s]?)?(?d{3})?[-.s]?d{3}[-.s]?d{4}/

It also showed a replace flow that keeps only digits. I dropped it into a Node script. Done. My brain said “thanks, friend.”

4) SQL: fast-ish, but trust, then verify

I had a Postgres query on events. I needed counts per day for last 30 days. Vibe wrote:

SELECT date_trunc('day', created_at) AS day, count(*)
FROM events
WHERE created_at >= now() – interval '30 days'
GROUP BY 1
ORDER BY 1;

It worked. Then it said to add an index on created_at. Fine. But it hinted at a partial index that didn’t fit our data. I ran EXPLAIN ANALYZE and caught the miss. Lesson: test the advice. Use Vibe like a helper, not a judge.

5) Jest tests that I actually kept

I had a date helper: formatDate(date, tz). I asked for Jest tests with edge cases. Vibe wrote cases for:

  • Null input
  • DST shifts
  • Bad tz strings
  • Snapshot for a stable date

It mocked the clock with jest.setSystemTime. I liked that. One test failed on Windows CI due to locale. Vibe suggested to pass an explicit locale param. Good save.

6) PR polish and commit notes

My favorite bit? I let Vibe read a PR and write a summary. It called out a silent API change in a TypeScript type. That note saved a support ticket later. It also writes commit messages that aren’t cringe:

  • feat(api): add /api/hello with CORS and tests
    Short. Clear. Ship it.

(If tooling is your jam, I’ve also shared the hit-list of add-ons I keep pinned in my day-to-day setup in The best Vibe Coding tools I actually use.)

Where it tripped

  • Context amnesia: On big repos, it forgot file history. I had to say, “Use src/api/user.ts and src/db/index.ts.” Long chats got fuzzy.
  • Confident guesses: It invented a config key that didn’t exist for Webpack. Looked right. Wasn’t. I caught it fast, but still.
  • Rate slowdowns: Around late afternoon, replies felt laggy. Not always, but enough to notice.
  • Privacy nerves: It sends code to the cloud. I masked secrets and skipped private keys. That’s on me, but worth saying.

Little joys that kept me using it

  • Quick fix hints inline. ESLint errors became one-click fixes with a tiny note that taught me why.
  • Comments and docstrings. Short, tidy, and not too stiff.
  • Error explains. It turned scary stack traces into 1-2 lines I could act on.
  • Prompt templates. “Write tests,” “Explain this,” “Refactor for clarity.” Like buttons for my tired brain.

For devs who prefer to learn by copying real, working snippets, I compiled a walk-through with copy-paste-ready code in The Vibe Coding Guide: my hands-on take with real snippets.

If you’re the kind of maker who loves showing off wins with slick screen-grabs, you might also dig Sexy Snaps—it’s a quick read on turning ordinary screenshots into scroll-stopping visuals while keeping your private bits (code or otherwise) safely blurred.

Tips that made it better

  • Be blunt. “File: src/utils/date.ts. Add Jest tests for DST.” Short beats cute.
  • Paste small chunks. Big blobs confuse it.
  • Ask why and how to test. Not just “write code.”
  • Keep your own notes. I used TODOs in the file so it stayed on track.
  • Run the code. Always. Trust, but verify.

For a broader look at how AI coding assistants fit within company intranets and developer workflows, check out Intranets Today and skim IBM’s industry take on vibe coding for a big-picture view.

Who I’d hand this to

  • New devs who want guard rails and good habits
  • Solo devs who need speed on boilerplate and tests
  • Busy seniors who hate writing commit messages and docs but care about quality

If you lead a team, pair it with code review rules. It will help folks ship faster, but someone still needs taste.

(I also jotted down the mindset and flow-state tweaks that keep me productive in My take on Vibe Coding tools—what actually keeps me in flow.)

The verdict (and my gut)

Vibe Coding AI saved me hours on setup, tests, and slog work. It also tried to sound sure when it wasn’t. That’s fine. People do that too. I’d give it an 8/10 for day-to-day dev, higher if they fix the context drift.

Would I keep it? Yeah. For quick tasks, test stubs, and PR notes, it’s gold. For core logic, I still slow down, write it clean, and ask Vibe to review my draft. That mix felt right.

And yes—late at night, with my fan humming and a cold chai on the desk, it felt like I wasn’t coding alone. Funny how much that matters.

If, after closing the laptop, you’re craving some actual human conversation and you happen to be near south Georgia, you can hop onto [Doublelist Valdosta](https://onenightaffair.com/doublelist-valdosta

zielkeguptill