BUILD. SHIP.
REPEAT.
I got into backend development the unconventional way — no CS degree, no bootcamp, just a lot of late nights figuring out why my APIs kept falling over. That turned into a real interest in distributed systems, and now into a payment ledger I'm building in Go with Kafka and gRPC underneath it. I'm final-year, self-taught, and looking for a team that builds things meant to survive contact with real traffic.
BUILDS THE WHOLE THING
Next.js frontend, Node backend, Postgres underneath. I don't hand off — I ship it.
AGENTS THAT REMEMBER
Built chat systems with Letta and Mem0 for persistent memory. Gemini, LangChain, RAG — hands-on. not buzzwords.
READS SYSTEM DESIGN FOR FUN
CAP theorem, quorum writes, throughput vs latency tradeoffs. Yeah, actually for fun.
GO + gRPC + Kafka
Building a distributed payment ledger right now. This is the stuff I actually want to work on.
DEVLOG
BUILDING IN PUBLIC.
DOCUMENTED.
Notes from building a distributed payment ledger — the decisions, the breakage, and what I learned.
Why I Chose Quorum Writes Over Simple Replication
Exploring the delicate balance between consistency and availability in a distributed payment ledger — and why 'just add a replica' wasn't good enough for money.
Kafka vs Direct DB Writes for the Ledger
Why I put an event log between the API and the database, and what it cost me in latency to get durability I could actually trust.
Debugging a gRPC Deadlock at 2am
A postmortem on a connection pool starvation bug that took three days to find and about ten minutes to fix once I actually found it.
CAP Theorem Tradeoffs I Actually Hit
Textbook CAP theorem is an abstract triangle on a whiteboard. Building a ledger made it a concrete, uncomfortable decision I had to make in code.
SELECTED
WORKS
Zharnyx
WiWiBot
Let's Build Something
Open to internships, full-time backend roles, and interesting problems. Reach out if you're hiring or just want to talk systems.