My Story
Grit, commitment, dedication, consistency
Necessity is the difference between wanting something and needing it, and I grew up on the needing side of that line. Where I'm from, infrastructure isn't assumed — "basic things" isn't a phrase, it's a daily accounting. You stop asking whether a problem is interesting and start asking whether it's load-bearing. Software was the craft I found that could actually move that line: a road doesn't get built because I write code, but a bus operator's entire business running reliably off a phone does, and multiplied across a country, that's infrastructure too. I don't think I'm ordinary, and I don't say that lightly — the ground I grew up on wasn't ordinary, and it left its mark. So I build. Zoomaa, CrisisEcho, MigoMap — different shapes, same root: find where the infrastructure is missing, and build the thing that has to hold weight. I'm a man on a strange journey. Until it's finished, there's no rest.
Grit
Grit is what's left when the interesting part is over, and infrastructure work is mostly the uninteresting part. Everyone can do the first eighty percent — it's fun, it's momentum, it's a thing coming together. The last twenty is the part that decides whether anyone can actually depend on what you built, and it's slow, unglamorous, and invisible even when you get it right. CrisisEcho lived in that twenty percent for weeks. That's most of what grit actually is: staying in the boring part long enough to find the thing that makes the system trustworthy, not just impressive.
Commitment
Commitment is deciding before you know how it ends. You don't build something where nothing existed before by re-litigating the decision every morning based on how the previous day went — if I'd worked that way, CrisisEcho would have died in week two. What got it through was structure: refusing to move to the next phase until the current one was actually clean. Commitment isn't stubbornness. It's building the work so that finishing stays possible even when the ending isn't visible yet.
Dedication
Dedication is caring about the parts nobody will ever thank you for — and where I'm from, nobody thanking you for something never meant it didn't matter. Passengers on Zoomaa will never notice the boarding flow reconciling itself the instant a signal comes back. But someone standing in a yard with no network and a queue of forty people will have a day that works instead of one that doesn't, and that's the whole difference between a feature and infrastructure. None of it demos well. All of it is the gap between a thing that works and a thing that works when it actually has to.
Consistency
Consistency is the pillar that makes the other three mean anything. Grit gets you through a hard week, commitment gets you through a hard project — consistency is what turns those into a body of work, showing up at the same standard whether the day is exciting or it's just maintenance nobody's watching. It's also the hardest of the four to fake. You can perform grit for an audience. You can't perform years of showing up.
What I read, and what it did to me
Dostoevsky's Notes from the Underground was the first book that made me uncomfortable in a way I couldn't argue my way out of. Its narrator is brilliant, self-aware, and completely paralysed — proof that intelligence without action is just an elaborate way of standing still. I think about that whenever I catch myself researching instead of building.
Crime and Punishment is about what happens when you decide the rules apply to other people. Raskolnikov reasons his way, step by careful step, into something monstrous — and every step is logical. It's the most persuasive argument I know that clean reasoning from a bad premise gets you somewhere terrible faster than muddled thinking ever could.
Solzhenitsyn's The Gulag Archipelago is the heaviest book I've read and I don't think I'll ever be done with it. Its line about the line between good and evil running through every human heart, rather than between people, permanently ruined my ability to think of myself as the reliably good party in a disagreement.
Lanza's Biocentrism and Penrose's The Emperor's New Mind pull in opposite directions and I keep both. Biocentrism makes the case that consciousness isn't a footnote to physics; Penrose argues that mind isn't computation, that there's something in human understanding no algorithm reaches. I work in AI. Holding a serious argument for the limits of computation next to the thing I build with every day keeps me honest about what these systems are and aren't.
And the Bible, which I return to differently than the others — not as an argument to evaluate but as the ground I stand on when the arguments run out.
Who I study
Jesus, first and above the rest — not as a historical figure to admire but as the person I'm trying to follow. Everything below is a distant second.
Tesla, for the discipline of building the whole thing in his head before touching material, and for the willingness to be right in public while everyone else was wrong. Da Vinci, for refusing the premise that you have to choose — anatomy and engineering and painting were one investigation to him, and I've never believed the specialisation argument since.
Michael Jackson, for a reason people find odd until they look at the footage: the rehearsal. The genius everyone talks about was preceded by an obsessiveness about repetition that's genuinely uncomfortable to watch. He'd run the same eight bars until it was involuntary. That's not talent, that's consistency wearing talent's clothes.
And Dostoevsky, for looking directly at the worst of what people are and refusing to either flinch or despair.
How I actually work
Own the whole stack. I want to know what the database is doing and what the pixel is doing, because the bugs that matter live between layers and nobody who owns only one layer can see them.
Ship it. A system that isn't in front of users is a hypothesis, not a product. Zoomaa, Zoomaa Partner, MigoMap and AuraGo are all in app stores because that's the only version of the work that counts.
Design for the failure, not the demo. No network, simultaneous writes, a model that's confident and wrong — these aren't edge cases, they're Tuesday.
Be honest about numbers. Every figure on this site names where it came from. Where a measurement has a weakness — a metric I labelled myself, a rubric that's inherently subjective — I'd rather say so than let it look sturdier than it is.
Education
Training & graduations
Expected 2027
M.Eng. Computer Science — Data Analytics & AI
Virginia Tech
Apr 2023
B.Tech. Computer Science & Engineering — GPA 3.5
Lovely Professional University
Journey
Milestones
2021
Software Engineer Intern — Zenith Bank (Ghana)
Built a React customer portal with real-time transaction monitoring for 50,000+ monthly active users, designed REST and gRPC microservices in Spring Boot that cut partner integration time by 25%, and implemented OAuth 2.0 with RBAC.
2022
Software Engineer Intern — XEARTH
Architected payment microservices in Java and Go scaling to 100,000+ daily active users at 99.99% uptime, integrated 5+ payment gateways to PCI-DSS Level 1 with circuit breakers, and built a fault-tolerant reconciliation engine that auto-resolved 95% of discrepancies.
2023 — 2025
Software Engineer — Instaacoders Technologies
Kubernetes-based distributed systems in C++ and Python at 15,000+ RPM for 50,000+ daily active users. Migrated search to OpenSearch over a Kafka CDC pipeline, cutting P95 latency 60% and lifting conversion 18%; reached 99.9% data consistency with exactly-once semantics.
2025
AuraGo Food · MigoMap
Shipped two products independently: a multimodal RAG food-discovery platform, and a co-activity planner that grew past 1,000 users and needed an AI moderation pipeline to protect what it was for.
2026
CrisisEcho — M.Eng. capstone, Virginia Tech
A real-time crisis intelligence platform: eight data sources through Kafka, a six-gate AI verification pipeline, and a Flutter app — four pods on GKE Autopilot with CI/CD on every push to main.
2026
Zoomaa — intercity travel platform
A passenger app, a multi-tenant operator back-office and a Go backend, live on the App Store — atomic seat booking, split mobile-money payments, live tracking and offline-first boarding.
Recognition
Awards & honours
Ghana National Secretariat Scholarship
Government of Ghana — National Scholarships Secretariat
Moments
In the field
In their words
What colleagues say
Sample testimonial. Samuel owned the whole stack on this one — pipeline, backend and app — and the parts nobody sees were as considered as the parts you do.
Sample testimonial. He shipped the thing, then kept going until the failure paths were as solid as the happy path. Rare.
Sample testimonial. Clear about what he knew, clearer about what he didn't, and quick to prove either way with a measurement.