I build tools that make operational friction disappear. Product engineer, 28 years, end-to-end ownership across 40+ enterprise engagements. A different stack and problem each time, each owned solo from ambiguity to production. I build the reusable architecture that solves a whole class of problem and ship zero-to-POC in weeks.
The edge I bring to the hard ones is forensic: NTSB-style root cause analysis for systems that are broken, undocumented, and critical, where nobody can say why. That's a capability, not the identity. The destination is the tool that makes the problem disappear for good.
"If you want to cheat, cheat fair." — Moe Howard, Healthy, Wealthy and Dumb (1938)
Core technologies: TypeScript, Vue.js, React, Node, HTML5/CSS3, WCAG 2.1 AA accessibility, REST/GraphQL integration, forensic debugging, SCORM/xAPI/AICC/cmi5.
Approach: When a system fails, I map the contributing factors instead of patching the symptom. Swiss cheese analysis, reproducible debug states, the systemic fix over the quick one.
Vue.js wrapper with SCORM API emulation: save course state at any point, restore instantly, edit SCORM values directly, jump to any section. Cut testing cycles from hours to minutes for gated content. It addresses a gap commercial SCORM tools never closed: reproducible debug states and session inspection as first-class features.
Cross-domain content delivery built in 2011, five years before Rustici shipped Content Controller for the same problem. Lightweight stub packages on each client LMS, content served from central servers, transparent SCORM/AICC protocol translation. Served ~20 energy utility clients from a ~2,000-course library, 10+ years in production.
Investigated a reported course-incompletion spike framed as a tracking bug. The investigation surfaced five concurrent systemic failures: a memory cache with no auto-save, a "Congratulations You Failed" UX pattern, confusing navigation, a mobile workforce on poor WiFi, and short-burst usage fighting an hour-long desktop design. The platform was later abandoned, indirect validation of the findings.
Contributed to a React/GraphQL platform acting as a federated facade over a content controller, an enterprise LMS, a learning-record store, and a cloud identity provider. Primary work: a large-scale multi-tenant rebrand through an undocumented Material UI theming system, scoped at one week and stretched to months as interdependent style dependencies surfaced. Plus bug fixes, identity-provider troubleshooting through log analysis, and reverse-engineering LRS queries.
Open to work as a product or forward-deployed engineer: building tools, owning systems end-to-end, embedding with the teams whose problems need solving. I bring a forensic edge to the ones nobody else can untangle.
Website: pattern158.solutions LinkedIn: linkedin.com/in/pattern158
Built with AI-assisted development (Claude Code). Tools that make complex work precise.