01
Build the thing that annoyed me
Every project here started as a small irritation. A screenshot tool that wanted an account. A directory full of dead links. The bar for starting is low on purpose.
I'm a Business Analyst by day. Requirements, process, and the genuinely difficult work of getting people to agree on what a thing needs to do before anyone builds it. By night I build small open source tools, mostly around AI and developer workflow, usually because something annoyed me enough to fix it.
Unfolding Dimensions is where that second half lives. Nothing here is a product with a roadmap. It's a workshop.
01
Every project here started as a small irritation. A screenshot tool that wanted an account. A directory full of dead links. The bar for starting is low on purpose.
02
If something can run on your machine without an account or an upload, it should. Most of these ship with no backend at all. That's a feature, not a shortcut.
03
A README that documents a flag which doesn't exist is worse than no README. I'd rather ship a smaller true description than a generous vague one.
04
Side projects die in the refactor before the first release. Ship it rough, use it, then make it good. In that order.
Building cool ideas is more relaxing than you think.
Utkarsh Benjwal