I'm Jay. I live in Nigeria, where I build the future.
My origin story in tech begins in 2021, not with some cinematic "I've been coding since I was six" narrative, but with curiosity colliding with possibility. That year I opened the door to programming and quickly noticed something peculiar about software: a single idea, written as code, can quietly shape how millions of people interact with the world. That realization stuck.
I'm a software engineer who works across backend and frontend systems, building applications that are practical, scalable, and genuinely useful. My toolkit spans TypeScript, Golang, and modern web frameworks. I enjoy the craft of translating abstract problems into elegant systems sometimes that means designing APIs and backend services; sometimes it means building interfaces where complexity disappears and things just work.
The motivation behind my work is simple but ambitious: build software people cannot do without. Email did it. Search did it. Messaging did it. I'm drawn to products that become so woven into daily routines they feel almost invisible yet the world would be awkward without them. That's the bar I build toward.
Beyond writing code, I spend time studying system design, emerging technologies, and the architecture behind products that scale to millions of users. Lately, I've been going deep on AI engineering specifically, what it takes to keep autonomous agents reliable once they leave the demo and hit production. Agents fail in ways traditional software doesn't: a tool call hangs mid-task, a step silently drops, and the whole run degrades without anyone noticing until it's too late. I'm building a Go-based orchestration layer that treats those failures as first-class events to detect and recover from, not edge cases to hope around. It's the kind of problem that sits at the intersection of distributed systems and AI, and I find that endlessly interesting.
And when I step away from the terminal, you'll likely find me deep in an anime series, dissecting a good film, or lost in a game three things that, like great software, reward patience and attention to craft.
I'm still early in the journey, but the trajectory is clear: keep learning, keep building, keep chasing the idea that the next thing I ship might become something people rely on every single day.
The mission isn't just to write code. It's to build things that matter.

Three shifts that shaped how I build.
Frontend first, out of necessity
Started shipping full Next.js codebases from scratch — component architecture, type contracts, pixel-precise Figma builds.
Pulled toward the backend
Found the real satisfaction in schema design and API contracts — modular architecture, structured logging, systems that hold under load.
Now building AI agent systems in Go
Deep in a self-directed curriculum on agent orchestration from first principles — harness engineering, context management, sandboxed execution, and durable multi-agent workflows, built in Go instead of imported as framework abstractions.
What I reach for.
"I love working across the stack, but my happy place is designing clean APIs, scalable systems, and backend logic that just works."
Usage
Tools, technologies and gadgets I use on a daily basis but not limited to.
Technologies
Golang — Systems & Backend Language
React — UI Library
Next.js — React Framework
NestJS — Node.js Backend Framework
React Native — Cross-platform Mobile Framework
Tailwind CSS — Utility-first Styling Library
Python — Programming Language
PostgreSQL — Relational Database
Prisma — Next-generation ORM
Tools
Visual Studio Code — Primary Text Editor
Neovim — Terminal-based Text Editor
GitHub Copilot — AI Coding Assistant
Heroes
Inspired by Rafael Condo's heroes list, here's my own curated lineup of code conjurers and digital dynamos that I'm absolutely stoked to meet someday. "In no particular order"
