Ideas
Projects that live in my head — some already in code, some still one sentence. Status field included so I can't lie to myself.
Every idea I keep coming back to gets a note here. The rule: one note per idea, a status at the top, and the reason it should exist before any talk of the stack.
| Status | Meaning |
|---|---|
| Shipping | It exists, people can use it, I maintain it. |
| Building | Code exists and runs; not finished. |
| Designing | I know the shape of it; nothing runs yet. |
| Seed | One paragraph. Might be a bad idea. |
The list
Before any launch, the first real user found Botxona by asking ChatGPT where to deploy a bot. Her bot worked — it just couldn't find its database.
Status — live. An AI presentation generator for students in Uzbekistan. It isn't really the product: it's a cheap way to build an audience for Botxona and everything after it.
Status — live, in production testing. Telegram bot hosting for Uzbekistan: drop in a zip, it gets checked, it runs. Payment in so'm, the panel in Uzbek, and a free tier for people who don't write code.
One nginx in front of every project on the box, generated from one YAML file. No app terminates its own TLS.
Status — shipped. The camera filter module behind dona.uz live-shopping streams — face-tracked beauty filters written natively in Kotlin and Swift, behind one JS component.
Projects that live in my head — some already in code, some still one sentence. Status field included so I can't lie to myself.
Status — designing. An Uzbek-native explainer engine: you ask a question and get back a narrated, animated lesson where the pointer moves with the words. The whole thing rests on one unsolved problem.
Paused at Phase 0. Open-source gamified learning — the part worth keeping is the data model.
Status — live, 200+ users from a single ad. A voice-pairing Telegram Mini App. The topic framing is a mask I made up; the real bets are a channel of my own and a server that finally does something.
Status — shipped, open source. A way to put your Yandex Music playlist on a portfolio: no hosted service, no token anybody has to hand over, just a scheduled job in your own repo.
The filter I try to apply
- Would I use it this week? If not, it’s a portfolio piece, not an idea.
- What’s the smallest version that’s still useful on its own?
- What do I learn by building it that I can’t learn by reading? See Skills.
Stub. Seeds go here as one-liners before they earn their own note.
comments