System · 2026
vs-pod
A personal development environment I could actually live in — not another dashboard of widgets.
- Role
- Design and engineering
- Status
- building
- Year
- 2026
- Stack
- Next.js, TypeScript, Firebase
vs-pod
vs-pod started as frustration with how scattered my own tools had become. I wanted one place for the work I was doing, without turning it into a second job to maintain.
Problem
My notes, experiments, and local tools lived in different places. Switching context was more expensive than the work itself.
Why
I wanted a personal operating surface that felt like a workshop, not a productivity product.
What was difficult
The hard part was restraint. Every feature I added made it feel more like software I would eventually abandon.
Decisions
Local-first where it mattered. No gamification. A small set of objects instead of a taxonomy of everything.
Architecture
A focused Next.js surface with a thin data layer. The point was a usable system, not a platform.
What exists
A working environment I still open. The public writing around it is part of the product, not a launch post.
Lessons
Personal tools fail when they try to impress their owner. They work when they disappear into the day.
Related
- Chess analyzer
A chess analysis tool built so I could see my own games clearly — without borrowing someone else’s interface.
- iamevs
This site. A personal digital studio rather than a portfolio template with my name on it.