QC workshop — Brandon Werner, developer
I build practical software, developer tools, and playful products — and I care enough to test the awkward parts.
Full-stack product work, honest documentation, and quality checks that actually run. This site is the build floor for that process.
SEC. 01 / Work
The strongest builds first: real captures of what each product looks like today, with honest statuses and verified links.
Case 01 / Game / full-stack product
A mobile-first browser game with an old-school MMO influence and a blue-collar science-fiction world.
activeInspection notes
Fig. 1 — Mobile capture
Checking the equipment loadout at the crash site
More shots
Case 02 / Family product / full-stack application
A family park passport for discovering parks, recording private visits, and earning server-controlled adventure progress.
activeInspection notes
Fig. 2 — Desktop capture
The interactive Bellingham park atlas
More shots
Case 03 / Game
A playful incremental game about hiring developers and generating lines of code — an early Vite + React client prototype with a live deployment.
prototypeInspection notes
Fig. 3 — Desktop capture
Mid-game state: 286 LOC and three developers
More shots
Supporting work
Fig. 4 — Terminal output
Real Alibaba token-plan request: 41 cookies reduced to one required cookie
Developer tool / security-minded automation
A CLI that imports a copied cURL request, verifies the endpoint, and experimentally reduces authentication material to the smallest working cookie subset.
open sourceFig. 5 — Desktop capture
Browsing local thread history in Jippity
Developer experience
Linux helpers and examples that make the Codex desktop workflow easier to launch, diagnose, demonstrate, and recover.
open sourceSEC. 02 / Bench
ProvisionalThe next builds on the bench — planned and honest, not an automatic feed.
Bench 01
The typed catalog from the backlog: slugs, statuses, verified links, and screenshots for every documented project.
Bench 02
Keep the five project captures current and honest as the products evolve; capture new builds when they ship.
Bench 03
The build notebook for decisions, failures, and fixes, plus focused case-study pages.
SEC. 03 / Notebook
ProvisionalA build notebook of decisions, failures, and fixes — short technical notes, not a content mill.
Note 01 — pending
Note 02 — pending
Note — Field notes are repository-owned markdown; the first entries ship with the notebook build.
SEC. 04 / Person
ProvisionalI'm Brandon Werner. I build practical software, developer tools, and playful products — and I treat quality checks as part of the work, not an afterthought.
I'm making the move into professional development from a full-time non-development career. This site is where that process becomes visible: real projects, real statuses, and the awkward parts documented instead of hidden.
Note — The full About section and verified contact paths land in a later build.
01
One issue, one branch, one reviewable draft pull request. No merge without a second pair of eyes.
02
Focused unit tests and real browser journeys on every branch — the checks run or they do not ship.
03
Live, active, prototype, open source, archived. No invented metrics, user counts, or testimonials.
04
Docker and Coolify deployments with per-pull-request previews, over magic dashboards.
SEC. 05 / Contact
ProvisionalReach me through a path that actually works — nothing here is invented.
More paths — pending
Additional contact paths will be added once verified.