Software Engineering Manager Hands-on builder

I turn ambiguity into systems teams can own.

For 15+ years, I’ve led engineering teams and stayed close to the work—shaping architecture, improving delivery, and building production systems, browser games, and open-source contributions.

Explore the work View GitHub
15+years shipping software
70programs in a full dynasty sim
12hand-built stealth levels
OSSLaravel framework + docs
Scroll to work

01 / Selected work

Built close enough to the details to make the tradeoffs real.

I use side projects as a working lab for product judgment, architecture, testing, performance, and the thousand small decisions between an idea and a release.

CASE STUDY / 01 Live build
Campus Gridiron Dynasty dashboard showing a fictional college football program, ratings, matchup preview, and navigation
01 A 20-year world that has to stay legible.
Simulation
20 seasons
World
70 programs
Roster
85 players / team

Simulation system · React + TypeScript

Campus Gridiron Dynasty

A fictional college-football world with recruiting, coaching movement, awards, budgets, bowls, playoffs, and twenty seasons of consequences.

Open the dynasty View source
01

Frame

Make a deep simulation readable at a glance.

A dynasty only works when thousands of moving parts still resolve into a clear next decision. The interface keeps the week, program, matchup, and long-term arc in view without flattening the depth.

02

Build

Connect the systems so choices carry forward.

Seventy programs, 85-player rosters, recruiting classes, hidden traits, coaching changes, budgets, rankings, awards, bowls, and an eight-team playoff all evolve inside one persistent save.

03

Verify

Test the long loop, not just the happy path.

Simulation-heavy tests run alongside repeatable browser smoke checks across Chromium, WebKit, and an iPhone profile—forcing playoffs, awards, recruiting, and multiple seasons so regressions surface before release.

02 / More systems

Different surfaces. Same ownership.

Shadow Circuit stealth level with patrol enemies, light cones, keycards, and terminals Playable / 12 levels

Three.js stealth game

2026

Shadow Circuit

Read patrol sightlines, collect gated objectives, and clear twelve dark sci-fi levels. Built with level validation, desktop and mobile controls, browser smoke tests, and repeatable screenshot tooling.

  • Three.js
  • TypeScript
  • Vite
Play Source
Tecmo Presents title card with the pixel-art rabbit mascot Native C / work in progress

Systems + preservation

2026

Tecmo Basketball Native Port

A clean-room native C port workspace built from verified behavior, with strict boundaries that keep original game data and copyrighted assets outside the public repository.

  • C
  • Native
  • Tests
Source

More from the lab

Tic Tac ToeAI game ↗ Sigil BreakerFPS foundation / WIP ↗ Formula JSTypeScript ↗ All repositoriesGitHub ↗

03 / Working approach

A builder’s feedback loop.

Leadership works better when the plan stays connected to the product, the code, and the evidence.

  1. 01

    Frame the ambiguity.

    Turn a fuzzy problem into constraints, risks, decisions, and a first testable slice.

  2. 02

    Keep the system legible.

    Choose architecture and interfaces the next teammate can understand, change, and own.

  3. 03

    Validate the loop.

    Use tests, screenshots, telemetry, and real usage to replace assumptions with evidence.

  4. 04

    Ship ownership, not output.

    Release work that the team can operate, explain, maintain, and improve after launch.

04 / About

Leadership with a builder’s feedback loop.

I’m at my best when the problem is still messy: turning it into a plan, keeping the architecture understandable, and building enough myself to stay close to the tradeoffs.

I’ve spent 15+ years shipping production software and leading engineering teams. Games and experiments keep my feedback loop honest—they force product choices, performance budgets, edge cases, and release discipline into the same small space.

AI is one tool in that loop. I use it to accelerate exploration and implementation, then review, test, and reshape the result until it is work I’m prepared to maintain.

01Engineering leadershipPlans, systems, delivery
02Product-minded architectureClear tradeoffs, durable code
03Hands-on developmentTypeScript, JavaScript, APIs
04Evidence-led qualityTests, screenshots, telemetry

05 / Next

Take the work for a spin—or inspect how it was built.

Every featured project is public. Start with the source, or jump directly into the most complete simulation.

InspectGitHub ExperienceFeatured build