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.
Drift · calendar · Pomodoro · OAuth · Supabase
The unfinished first app that taught me what software actually is.
← All projectsWhat it is
A drag-and-drop time management calendar where you slot predefined tasks — work blocks, exercise, focus sessions — into whatever time slots fit your day. The centerpiece is a Pomodoro timer that stays visible on screen no matter where you go in the app.
The idea was a time-management calendar where you have predefined tasks — work blocks, exercise, focus sessions — and you slide them into whatever time slots fit your day. The Pomodoro timer was the actual value: it stays on screen regardless of where you go in the app. I've always found that a visible countdown keeps me from reaching for my phone. Todoist's timer disappears when you switch tabs. Drift's wouldn't.
It's unfinished. But the build taught me more than the idea did. A calendar event has to be stored somewhere — that meant learning Supabase and database state for the first time. Logging in through Google meant working through OAuth from scratch. My method was to iterate while taking notes off apps I actually used: Todoist, Apple Reminders, Apple Calendar, Google Calendar — cataloguing every interaction I take for granted but now had to code myself.
That process changed how I look at products. Before Drift, I used Google Calendar without thinking about it. After Drift, I couldn't stop noticing every button, every widget, every animation — and the cost each one has in code. Things you take for granted every day require coding for each interaction and UI element. None of it just happens.
That's the useful shift: I stopped seeing apps as products and started seeing them as systems of specified decisions. Knowing that, you build and prompt differently.