Personal projects - ship it or it doesn't exist

Twelve years of side-builds as the substrate of taste - the prototype is the argument, not the pitch.

This is one of twelve themes in the wiki. It names a belief that formed in lockdown 2020 and has not changed since: the prototype is the argument. The pitch is not. You are likely here because you saw "ship-the-prototype" in the belief graph and want the origin story, or because you came from second brain or agent-first and noticed those pages both cite open-source GitHub releases as a deliberate act - not an afterthought. This page is where that instinct lives.

The theme covers twelve years and 52 projects. Three things follow: how the belief formed, what the project lineage looks like now, and how the belief refined when AI made iteration near-zero cost.

The moment

May 19, 2020. One phrase in a LinkedIn post: "No longer 'just an idea!' :)"

That phrase names a prior identity and walks away from it. The "just an idea" person pitches. The prototype person ships. The prototype is not a deliverable - it is the evidence.

The context: lockdown, no dev budget, a product idea that needed a mobile app to prove it. Rather than waiting for a team, I pulled up a Flutter/Dart course. Three weeks later the app existed. The constraint became a capability. The workaround became a habit.

Before that post, ideas were sufficient arguments. After it, shipping was the only argument that counted.

How the pattern runs

The behavior predates the belief. The early habit formed through projects that shipped and still failed: artifacts that existed, ideas that proved insufficient, companies that archived. The lesson: shipping is necessary but not sufficient. That gap is where belief.idea-validation-3-pillars later grew - it did not suppress the shipping habit. It supplemented it.

From 2020 onward, the tools rotated every two to three years. Flutter/Dart for mobile minis (2020). Python and Streamlit for personal-brand work (2023). Ollama and local LLMs for the off-grid setup (2024). CrewAI and agentic orchestration for multi-agent experiments (2024). Vanilla HTML and Claude Code with kg.json (2026). The stack changed; the pattern did not: identify a gap, acquire what closes it, build the smallest thing that proves the point, post the link.

The full lineage is at projects/index.html: 52 projects, 41 lineage edges, 58 tech nodes across 10 years.

What the top tier looks like

Four projects are the clearest expressions of the belief - shipped, open-sourced, on GitHub.

Shararat - Vapi Build Challenge (2025). Hackathon-shipped voice AI multi-agent project. No day-job context: a personal build, a public challenge, a link at the end. Ship-the-prototype applied outside the day job, in a constrained format.

second-brain v1 (2026). Wiki plus kg.json plus /enter v3. Plain markdown, git, open source, MIT, free forever. Four months of private use before the public launch, then one clean announcement with a paste-prompt in the post body. The belief made operational: see second brain.

luna-monitor / Claude Code Resource Monitor (2026). Open-source dev tool for tracking Claude Code resource usage. Built and made public immediately. The same instinct as open-sourcing: if it is useful to me, it is useful to someone else. help-market-flourish is the belief; this is one data point.

ai-resume (2025). Open-source AI-powered resume tool built on the agamarora.com substrate. The personal site as lab surface: ship something real, make the code public, done.

Below the top tier: a learning-tinkering category that closes gaps without pretending to be products. Flutter/Dart minis (2020), LLM comparator with Groq and Streamlit (2024), Pi-based Python scripts. Each closed a learning gap, each got posted. None were trying to become companies.

V2 Games India (2014-2016) is a different category entirely. Co-founded startup, studio head role, analytics and business work. It belongs in career reflection, not here.

The loop

Build, post, teach, learn, build again. Posting is not distribution - it is the closing step that converts a personal build into a reusable artifact with feedback attached. The loop does not close until someone else can learn from it.

The pattern holds: the Ollama keyboard-shortcut came with a tutorial video. The LLM comparator came with a Streamlit-share link. The second-brain v1 launch came with a paste-prompt in the post body. Open-source IS the posting step for code: same instinct, different surface.

Not every build gets posted. The second-brain ran privately for four months before any public post. Day-job enterprise work is intentionally under-shared. The loop applies to personal builds. The boundary is real.

When the belief refined

2020: any prototype beats no prototype. Reid Hoffman's "if you're not embarrassed by the first version, you launched too late" was borrowed authority for the position.

By 2026 the belief had refined, with a specific trigger. belief.spec-over-sprint (2026-04-09): "When you've specced every pixel, a generative tool gives you a worse version of what you already decided. Invest in the spec, not the iteration speed."

Pre-LLM, the binding constraint was existence - ship the thing or the idea stays theoretical. Post-LLM, the binding constraint moved upstream to quality-of-spec, because the model amplifies whatever you put in front of it. Same verb (ship), tighter upstream constraint (spec first). The ship-fast belief is listed as superseded in the ontology. The shipping cadence did not change. The preparation upstream of it did.

Between December 2025 and April 2026, three projects shipped: /buddy, second-brain v1 private, second-brain v1 public. The cadence held.

Where to go from here

Three exits, depending on what you came for.

If you want the belief in its starkest form - the ship-the-prototype conviction with its 2020 crystallization point and its 2026 refinement - read spec-first-taste. The builder trilogy (Spec > Sprint / Taste > Execution / Context > Prompt) is the current version of the same instinct, upgraded.

If you want the loop's posting dimension - where build-post-teach-learn is analyzed as platform strategy rather than personal practice - read linkedin as instrument. The same posts that close the loop there are the evidence records here.

If you want the open-source instinct in the broader frame - why making things public is the same move as shipping them - read career reflection for the help-market-flourish evidence with 2026 open-source data.