I'm a 28-year-old engineer building products, automation tools, and digital experiences at the intersection of AI and everyday craft. I work mostly across React, Node, and React Native — but I care more about the problem than the stack.
I'm drawn to problems that sit in the seams between disciplines — where good engineering meets good product instinct.
I started writing code as a teenager because I wanted to change how something worked, not because someone told me to. That instinct hasn't really gone away.
Today I split my time between client work and side projects — IPTV infrastructure for a few thousand users, Discord bots that automate gnarly community workflows, React Native apps for inventory and routine, and a slow-burning RPG system I keep refining.
I think a lot about the boring middle layer: the schemas, the queues, the retry logic, the telemetry — the stuff that decides whether a product survives its first thousand users. AI sits on top of that, not under it.
Outside of code: long walks, a dangerous amount of coffee, and trying (failing) to keep up with a steady stream of weekend ideas.
Six independent projects, picked from the longer list. Each one solved a real problem for a real person — most often, me.
An AI-native day planner that watches your calendar, inbox and tasks, then proposes a calm shape for the day. Not a chatbot — a quiet assistant.
IPTV infrastructure I run for a small community: HLS proxying, EPG normalization, per-tenant auth, and a small dashboard. Survives Sunday-night football traffic.
A Discord bot used by a few mid-size servers to auto-triage reports, escalate by tone, and quietly archive resolved threads. Handles ~40k events/day.
A React Native inventory app for a friend's small wine shop. Barcode scanning, offline-first sync, low-stock nudges. Replaced a mess of spreadsheets.
A long-running RPG systems experiment: deterministic combat, modular character sheets, and a tiny scripting language. Mostly a sandbox for systems thinking.
A personal automation hub: cron jobs, webhook routing, GPT-driven summarizers and a tidy dashboard. Replaces three Zapier accounts for the price of nothing.
Skills age fast; taste doesn't. I'm fluent in the boxes below — but happy to reach outside them when the problem asks for it.
A snapshot — updated when reality changes.
Most AI assistants want to chat. I want one that just shapes the day: surfaces what matters, hides what doesn't, and gets out of the way. Quiet by design.
Short notes from the workbench — usually about the boring middle layer of a product, or what AI gets wrong about being useful.
I'm open to full-time roles, contract work, and the occasional weekend collaboration with people who care about the details.