AGENTIC SWE · ENTREPRENEURSHIP · PRODUCT MANAGEMENT

One calendar app, a lot of broken assumptions.

Vibe coding isn't one prompt and a finished product. It's a practice: knowing what you want, building it with agents, inspecting the result, and doing it again. I've been in this loop for the past two months, trying to actually understand what I'm building.

This section maps the whole thing.

Story is how it started and what I've learned.

Environment is the workflow and tools I've built around it.

Projects are the apps that came out of it.

Watched is what I'm reading right now. Everything here is still moving.

Proof of motion

What the loop produced.

Practice Volume, Product Judgment, Iteration Through Version Control.

3
Product ideas advanced
Drift, Workbench, and Augment moved from loose ideas into scoped product directions.
1
Shipped MVP
Workbench reached a working MVP with the core reflection-first assistant loop in place. Drift, soon.
80+
GitHub commits in a month
The learning showed up as repeated commits, branches, rollbacks, and rebuilds.
MANY
Repos Integrated or Watched
Implemented a LOT of tools into the workflow. Even more starred for future exploration.Constantly on top of new tools.

Story

An intern with all the knowledge in the world.

A lot of people think vibe coding is just throwing a single prompt into Lovable or Replit. I've tried both. The front end looks like AI-generated slop — a bunch of emojis, no back end, nothing that holds up once you need the app to actually do something. Same deal with Figma's AI features. While those tools have their own merit for wireframes and quick prototypes, they're cardboard houses built on shaky foundations.

Instead, I built my foundation on the stronger, SWE adjacent agent: Claude Code.

(I started at a very quick moving time — agents and agent-based productivity has made leaps and bounds in the months leading to me starting, as well as currently.)

Drift is where I first started, and where things started to click. I wanted a calendar app with a persistent Pomodoro timer, and the second I started building it I ran into all the work I didn't know existed. OAuth. Database state. Event persistence. The concept of storing something so it survives a page refresh. Every one of those felt obvious in hindsight and invisible before.

That's what agentic coding is actually about for me. AI is like an intern with all the knowledge in the world, but they're extremely stupid. If you have no clue what you're trying to do, neither will the AI. Slop in, slop out.

The loop is: know what you want, inspect what came back, and do it again until it's right.

Note 01

My introduction

I picked up Claude Code two months ago with no plan. Just an idea for a calendar app and enough curiosity to learn and try.

Note 02

Notice the hidden work

Every interaction, button, UX element, design, etc. on an app is something you need to code in. Drift made Google Calendar look like witchcraft. A timer, a saved event, a login — every one of those are things I took for granted before I started building.

Note 03

Git as a save file

Before I touch anything, risky or not, I always commit or branch. Same instinct as saving before a legendary Pokémon encounter — if I accidentally faint it, I can just roll back.

Note 04

Critique as Product Development

At Rebrandly, constantly critiquing the client was counterproductive. Yet now, that critique can become a wireframe. Same eye, but now, software is democratized.