// a snapshot of what i actually use day-to-day. inspired by uses.tech.
// the ones i actually pick by default, not just "have used once"
i build to scratch real itches. most of my side projects start with me or someone around me hitting a friction in day-to-day life — a clunky form, missing info, a workflow that should've been an app. i sit with the problem long enough to see what's actually missing, then build the smallest thing that fixes it. real frictions > hypothetical features.
boring tech, until it isn't. i pick what ships fastest with the least surprise — flutter for mobile because it's predictable, supabase for backend because it gets me to v1 in a weekend, go when the requirements outgrow the prototype. that said, i'm actively expanding the toolbox: currently learning react / react native so "mobile" doesn't only mean flutter for me.
i lean on ai pair-programming heavily (claude, copilot, codex). it's not magic — it's a faster typist who occasionally hallucinates. you still need to know what you're building.