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.

Augment · semantic graph · canvas · documents

Your thoughts as a graph, because brains don't think in straight lines.

← All projects

What it is

A canvas-based mind map tool where the map gets built for you as you talk through your thoughts or upload documents. Whether or not you structure your thinking first — the AI helps to do the mapping and you get a human-legible graph of how your ideas connect.

Prelude: Get ready. This is gonna be a lot. It's the product idea I'm by far the most interested in, and my story reflects that.

The original motivation was the same as Workbench: make people understand their own thinking before they hand it to AI. My version of working through a hard problem is to keep breaking it down — What is the problem? What do I need to know about it? How do I solve it? What's the end goal? If I can't solve it, why can't I? Then I keep going. If you mapped that out, you'd get a massive tree—one root node, way too many branches—because of how many follow-up questions I ask myself. That's how I actually think about hard problems. Mapping that out is what Augment is trying to do.

The idea kept evolving. First it was a study tool — look at any serious Obsidian vault and you'll see the same instinct: people connect primary concepts to sources and related material non-linearly, building a knowledge graph out of what they know. I connected with a friend, Kevin, a student from UC Berkeley who's probably going to be my co-founder on this. He came at it from a STEM angle: in applied mathematics you have a ton of concepts that feel totally siloed — definitions, theorems, proofs — until you realize most of them are built on top of each other or quietly relate. A textbook won't show you that. A map that surfaces those relationships doesn't just help you study; it helps you see how the field is actually structured.

Then I thought: why not apply it to project management? When you're building something from scratch, or any project for that matter, figuring out your critical path is genuinely hard — what's essential, what's a branch you can do later, what's a dependency you haven't named yet. The idea: brain dump the whole project into Augment and it builds an initial map. Keep talking to it as the project develops and the map grows with you. You end up with a clearer picture of what's blocking everything else, what can wait, and what you thought was important but actually isn't. Then the simplest version of all this clicked: if everyone already takes notes linearly — top to bottom in a Google Doc, the way we were all taught — why couldn't you just turn those notes into a graph? There's a couple high quality repos that've applied this thinking to codebases, but nothing more student/general focused.

The honest question is still: who cares, and why does it actually matter? The concept has a real adoption barrier. Most people don't think non-linearly, or at least they don't think they do, because they were taught to go top to bottom. I don't even fully utilize non-linear thinking myself. But the connection I keep coming back to is that neural networks and transformers — the backbone of every LLM — work exactly this way: self-attention looks at how everything relates to everything else, not in sequence. The most important tools right now are built on non-linear reasoning. Figuring out how to make that accessible is the actual problem worth solving.

No wireframe yet. Still need to understand semantic graphing and vector databases from the ground up before the execution makes any sense.

Augment concept wireframe TBD