Who I
Am.
Backend Architect · Distributed Systems
Background
I treat backend development as an engineering discipline. My career started building layers for high-load systems, where I learned that millions of small decisions accumulate into either clean, maintainable code or compounding technical debt.
Over the last five years, I've focused on mastering the scaffolding of modern web applications. From Go microservices processing millions of social media events daily, to distributed storage systems with peer discovery and encrypted node-to-node communication. I believe technical debt is optional. I believe software that is as maintainable as it is functional is the only acceptable kind.
I started in mechatronics engineering at NUST, which gave me a systems thinker's instinct before I ever wrote a line of Go. That cross-disciplinary background shapes how I approach distributed systems, from first principles, not patterns borrowed from a textbook.
Technical Arsenal
Refined through 5+ years of production systems engineering.
Core Runtime
Go is my production language of choice
Data Persistence
SQLite-backed local state for distributed nodes
Infrastructure
Production-grade cloud pipeline engineering
Distributed Systems
Peer discovery, replication, and node sync
Testing
Every layer covered, including chaos/sim tests
Domain Experience
Blockchain protocol & governance module work
How I
Think.
In architecture, a structural line that exists only to decorate is a failure of design. The same is true in software. I build systems where boundaries are defined by function, not by arbitrary separators.
Every abstraction should earn its place. Every interface should be honest about what it does. Complexity that cannot be justified by a concrete constraint is noise, and noise compounds.
System Integrity Score
99.9%
Across production Go microservices