SDUI Blade ecosystem
One framework-independent protocol with native Angular, React, and Svelte adapters, published as four independently versioned MIT packages.
Current engineering evidence
The implementation is part of the record.
A direct trail from current public TypeScript packages and a live full-stack deployment to proprietary product architecture and documented enterprise outcomes.
Public source and runnable systems
Start with work another engineer can verify.
These repositories and deployments can be inspected directly. They establish current library design, application architecture, testing, CI/CD, persistence, and deployment work.
College project · Sole architecture and implementation · Live deployment · Public source
JRKC Bookstore
The course used group assignments, but I completed the architecture, application design, implementation, database, testing, documentation, CI/CD, and Oracle deployment. It was the course's working end-to-end bookstore application rather than a demonstration or concept submission.
- I replaced the unavailable paid hosted backend with application-owned authentication and typed Drizzle routes so identity and PostgreSQL access remain under the application's control
- I isolated the bookstore in its own Docker Compose project, private database network, named volume, and explicit Oracle port so it cannot collide with other workloads
- I placed Caddy at the public boundary and health-gated deployment restarts so releases touch only the bookstore Compose project
- I rejected live Stripe credentials in deployment, preserving the completed checkout integration without accepting real payments from portfolio visitors
Current coding profile
Readable before the technology history starts moving.
This representative, assessment-ready view distinguishes current working fluency from extensive production experience and active review; the homepage technology history carries the broader stack and is not exhaustive.
Current product use
Used in current products, libraries, deployments, and portfolio work.
- TypeScript
- JavaScript
- Python
- Angular
- React
- Next.js
- SvelteKit
- Node.js
- PostgreSQL
- Docker
- GitHub Actions
Extensive production experience
Applied across enterprise applications, APIs, data systems, and cloud delivery.
- C#
- .NET
- RxJS
- Express
- SQL Server
- MySQL
- Microsoft Azure
- AWS
- Azure DevOps
- GitLab
Currently refreshing
Languages being reviewed through deliberate study and implementation practice.
- C
- C++
AI-assisted engineering and technical review
AI speed under senior engineering control.
AI coding assistants accelerate reconnaissance, implementation, refactoring, and verification. I supply the architecture, repository constraints, acceptance criteria, review, and final accountability instead of treating generated code as correct by default.
- Translate product intent into repository rules, architecture boundaries, acceptance criteria, and bounded tasks that coding assistants can execute without inventing requirements.
- Audit generated changes against the actual codebase, framework documentation, security boundaries, responsive behavior, accessibility, and long-term maintenance cost.
- Reproduce failures, isolate root causes, and drive corrective iterations until type checks, linting, focused tests, and manual review agree with the intended behavior.
- Use assistants for codebase reconnaissance, implementation, migration, refactoring, test generation, and documentation while retaining human control of technical decisions.
- Compare competing implementations and explain their runtime, operational, and maintenance tradeoffs rather than accepting the first plausible output.
- Reject fabricated claims and synthetic evidence; published portfolio statements must trace to source, a live system, a deployment record, or documented employment outcomes.
Proprietary product engineering
Architecture evidence without surrendering product IP.
Private source is represented through explicit system boundaries, implementation decisions, verified technology, and public product context without exposing proprietary assets.
Founder · Product architecture, implementation, testing, and delivery · Active proprietary product
Gravity English
I am designing and implementing Gravity English as a paid product: a SvelteKit application that combines tenant-specific delivery, structured curriculum, identity, billing boundaries, and a separate autonomous-generation service.
- Constraint and context
Schools, teachers, and enterprise customers need distinct branding, membership, curriculum, and domains without a separate application build for every tenant. Curriculum generation also cannot block the interactive application or weaken tenant isolation.
- Implemented approach
- I implemented request-time host resolution that maps a subdomain to an organization, branding profile, localized dictionary, membership context, and subscription state
- I separated Clerk authentication from application-owned users, organization memberships, and per-organization role authority stored in PostgreSQL
- Engineering decisions and tradeoffs
- I replaced the legacy Angular/AnalogJS application with SvelteKit 5 because the active product needed server-driven behavior without the former SSR and build constraints
- I kept curriculum in typed server-defined content so course structure can change independently from page deployments while the application still validates tenancy and rendering
- Resulting capability
- I made one application resolve tenant-specific brand, localization, organization, role, and subscription context for every request
- I moved blueprint and thumbnail generation into persisted PENDING jobs instead of holding the browser request open
Founder · Product architecture and active implementation · Private product in development
Coverlay Studio
I am designing and implementing Coverlay Studio as a private product. Its current codebase contains a real non-linear editing foundation while public access remains intentionally unavailable during active development.
- Constraint and context
A browser editor must keep tracks, linked clips, compound clips, selection, and panel state synchronized while making destructive-looking timeline operations reversible and predictable.
- Implemented approach
- I built a typed Zustand project store wrapped by Zundo so timeline changes participate in a shared undo and redo history
- I implemented linked and compound clips plus split, trim, ripple, roll, slip, slide, move, duplicate, mute, lock, visibility, and targeting operations
- Engineering decisions and tradeoffs
- I centralized editing state in one typed model, accepting greater store complexity to keep timeline, canvas, properties, assets, and assembly behavior consistent
- I modeled linked and compound clip relationships as explicit data so editing operations update related media deliberately instead of relying on visual conventions
- Resulting capability
- I built a reversible multi-track editing foundation rather than a static timeline mockup
- I established one shared action contract for editing tools consumed across multiple studio surfaces
Documented delivery
Engineering evidence beyond job titles.
Selected outcomes from enterprise modernization, product delivery, testing, and independently owned software lifecycles.
- 11
- enterprise applications developed, modernized, and supported at AT&T
- 2,000+
- automated tests repaired, refactored, or replaced at LCPtracker
- 13,000+
- customers across 115 countries served by the Park Place portal
- 83%
- reduction in estimation time from an independently delivered workflow
External record
Independent destinations for deeper review.
Continue through the source history, professional record, technical answers, or secure contact path.
Need deeper evidence for a specific role?
For senior engineering roles, product consulting, architecture review, or code-evaluation work, use the private contact form with the relevant context.