Principal Software Engineer @ Ayoconnect
Principal Software Engineer building scalable systems, payment infrastructure, and high-performance backend platforms.
engineering brief
Ask me about systems.
Payments, Go, architecture, and the tradeoffs behind reliable software.
→ explain instant transfers
→ review a Go pattern
→ start a conversation
Interactive systems lab / 001
A concise view of the systems, products, and engineering principles behind my work.
$ explore --mode overview
Select a domain to see the related projects, tools, and working principles.
130+ banks / 10,000+ TPS
Go, systems, practical patterns
Declarative Backend / building in public
Events, boundaries, recovery
01 / build
Reliable systems designed for real operating conditions.
02 / teach
Practical systems thinking for engineers building their foundation.
03 / share
Open-source tools, technical writing, and decisions worth documenting.
What I'm building
A small set of systems-focused projects, led by Declarative Backend — an open-source way to make backend engineering more approachable.
Flagship open-source project
Building in publicAn open-source visual backend builder that helps developers generate production-ready Go services without starting from backend code.
How I work
Start with evidence, model failure modes, and make changes that can be observed and safely rolled back.
The idea
Describe what you need. Generate editable Go code.
The principle
Remove accidental complexity without hiding the engineering.
Core stack
Production systems are built from durable fundamentals, not trend-chasing.
Writing
Practical notes on payments, distributed systems, and the lessons of building reliable software at scale.
The boundaries, invariants, and failure modes that make payment APIs trustworthy.
How cancellation moves through a Go service and why ignoring it creates invisible production work.
Queues coordinate work; they do not replace durable state, ownership, or reconciliation.
Timeouts are part of an API contract, not an afterthought added after the first outage.
Trajectory
Seven-plus years moving from individual contribution to technical leadership in payments.
2019
Gitty Inc.
Software Engineer
2021
Ayoconnect
Software Engineer II
2022
Ayoconnect
Software Engineer III / Team Lead
2024
Ayoconnect
Software Engineer IV / Tech Lead
2026
Ayoconnect
Principal Software Engineer
Principles
Scale is a design constraint, not a feature you add later. The decisions that matter are usually about data flow and failure, made early.
Most complexity is speculative. I add it when a real constraint forces it, and try to remove it when the constraint disappears.
Writing forces me to actually understand something. The blog is where I work through what I've built and what it taught me.
The interesting part of payments isn't the tech stack — it's moving money reliably for real people. The engineering serves that.
Working abroad and growing into leadership taught me that sustainable engineering is as much about people and pace as it is about code.
Open to thoughtful work
For engineering opportunities, consulting, collaboration, or a technical conversation — I'd be glad to hear from you.