I run FrontierPixel, a studio where I take real business problems from first conversation to production: data model, UX, integrations, deploys, and the support after launch. I'm self-taught (I built my first PC at 10 and haven't stopped taking things apart). I'm working toward an associate degree now, with a CS bachelor's after that.

The CRM and client-site backend FrontierPixel runs for its clients. Every business works in its own tenant with its own modules, branding and installable home-screen app. Leads, quotes, SMS, email, calls, follow-ups, consent records and audit history all live in one workspace.

• Autopilot: AI-drafted SMS and email replies, supervised in the composer, with guards on what can be offered and a check with staff before booking a handoff.
• Delivery pipeline: an isolated Convex backend for every preview branch, a schema-compatibility gate before every deploy, and dependency audits in CI. Merging to main is a production deploy.
• Reliability work: SMS retry and timeout handling, push alerts filtered by sender, crash-proof settings across stale tabs, and A2P 10DLC SMS consent.
• 208 merged PRs

Next.js 16 React 19 TypeScript Convex Better Auth Twilio Zoho Web Push Sentry

A local-service site that sells: an in-browser 3D shed configurator, server-side pricing, structured quote capture, live Google reviews, SEO content infrastructure, and instant handoff to the CRM.

• $196,042 in conservative quoted pipeline from 40 deduplicated, qualified opportunities in a measured two-month campaign (pipeline, not booked revenue)
• 1-second median dealer alert time across 70 production notifications
• Security hardening (CSP, intake validation), review-request flow with tracked link opens, 517 merged PRs

Next.js TypeScript Three.js Convex Zod Twilio Zoho · Case study →

A whole city's worth of game systems, built from scratch: 115 custom Lua resources and 881 merged PRs in its first three weeks.

• Economy: a stock exchange that moves on what happens in the city, prices that rise for whatever the city is short of, and businesses players buy and run
• Gameplay: walk-in heists, a music career with fame and stage names, a controller-complete inventory rebuild, and custom phone apps
• Ops: server-side cheat detection, an in-game bug reporter that attaches a screenshot and files to Discord, and a go-live script that backs up the database before every release, plus nightly backups. Every change to a third-party resource is documented with its own on/off switch.
• Open source: released ce_seats (MIT). The public site gives every update its own patch-notes page and posts it to Discord.

Lua 5.4 Qbox ox_lib MariaDB txAdmin Python JavaScript

A deterministic network simulator in C++20, with an Unreal Engine 5.8 game on top that only draws what the sim says is happening. You walk into a small office as the outside IT contractor, trace the cable, patch the jack, and end the broadcast storm.

• Models Ethernet bridging (IEEE 802.1D), VLANs (802.1Q), ARP (RFC 826), DHCP (RFC 2131), ICMP, and NAT (RFC 3022). Every protocol behaviour cites its RFC or IEEE section.
• Time is integer nanoseconds, so protocol timers tick exactly. A broadcast storm runs millions of events per simulated second.
• Every player action is a command in an ordered log, the base for replays, co-op and automation.
• The engine-free core builds and tests in seconds. Gear specs come from real vendor datasheets.

C++20 Unreal Engine 5.8 CMake Blender

Agents propose. Humans approve. Scripts execute. A credential-isolated layer between AI agents and the outside world. Agents write drafts, a human approves the exact payload in Telegram, and a deterministic executor runs only what was approved. Covers multi-account Gmail and Outlook triage, approved Trash and unsubscribe, and an SMTP state machine that fails closed. No LLM in the execution path.

TypeScript Node.js Zod grammY Microsoft Graph Linux systemd

Fixed the accessibility panel's tab and highlight state across Stories ↔ Docs navigation, with persistence behaviour and regression tests. Merged upstream.

• I own the whole thing. That runs from the schema to the deploy to the text message that didn't send at 2 a.m.
• Fail closed. I treat security, consent and failure states as features, not follow-ups.
• Prove it. Tests, CI gates, schema checks and regression checks, plus claims backed by a source: an RFC section, a datasheet, a measured number.
• AI-native, with guardrails. I run coding agents like a team. I set the architecture, write the rules and review every PR, and I build the tooling that keeps agents safe.
• Leave it readable. Small PRs, runbooks, and a written reason for every change to someone else's code.

Productizing the FrontierPixel CRM, building Network Engineer Sim's first levels, and getting Crew Empire ready for players.

Open to full-stack, backend, and game/simulation engineering roles, plus selected client work. Let's talk →