Built on Reliability, Not Vanity.
A backend-focused software engineer and systems hobbyist who treats software stability, predictable latency, and data integrity as non-negotiable foundations.
Why Backend & Infrastructure?
Anyone can build a sleek UI or slap together a template. But real engineering begins when thousands of concurrent users attempt to check out simultaneously, network sockets begin dropping, and database locks start stacking up.
My passion is solving what happens beneath the surface: ensuring that when an edge proxy takes a hit, the application logic degrades gracefully instead of collapsing into a cascading outage.
The “WALL-E” Mentality
RESOURCEFULNESS & HARDWARE RESPECTI built my primary homelab server—WALL-E—from repurposed bare-metal hardware. Running TrueNAS CORE, ZFS mirrored storage pools, and containerized microservices on an older machine forced me to understand resource constraints, I/O wait times, thermal budgets, and storage scrubbing at a hardware level.
Zero Silent Failures
Strict TypeScript compilation boundaries, defensive input sanitization, and structured JSON logs correlated with OpenTelemetry trace spans. No swallowed exceptions, no untracked 500 errors.
Data Integrity Above All
ACID-compliant relational transactions with row-level locks, idempotent event consumer workers, and automated snapshot backup schemes tested through regular recovery drills.
Resource & Cost Awareness
Profiling EXPLAIN ANALYZE query execution trees, eliminating N+1 ORM overhead, and tuning memory allocations before asking a founder or team to upgrade expensive cloud instances.
Request a Free System Health-Check (Audit)
Experiencing slow API responses, high server bills, or fear of downtime during peak traffic? Fill out this diagnostic intake and receive a concise 1-page action audit within 48 hours.