Vol. I · No. 1

    The Front Page · Backend Engineering

    Three years on, the engines still hum — fintech, logistics, med-tech, ed-tech, e-commerce, one API at a time.

    By Bakare Praise·Staff Notebook·

    When systems fall, customers notice. When they don't, nobody does — and that, quietly, is the work. For three years I've designed APIs, event-driven services, well-kept monoliths and cloud-native microservices for teams that needed the lights to stay on: payments to clear, packages to move, patients to be seen, students to learn. The pleasure of the job is making the complicated feel ordinary.

    Read the profile·Download the résumé ⤓·See selected works →

    LiveThe Wire · Clean Code Edition
    "Clean code always looks like it was written by someone who cares." — Robert C. Martin ◆ "The only way to go fast, is to go well." — Robert C. Martin ◆ "Truth can only be found in one place: the code." — Robert C. Martin ◆ "Functions should do one thing. They should do it well. They should do it only." — Robert C. Martin ◆ "A class should have one, and only one, reason to change." — Single Responsibility ◆ "Software entities should be open for extension, but closed for modification." — Open–Closed ◆ "Subtypes must be substitutable for their base types." — Liskov Substitution ◆ "Many client-specific interfaces are better than one general-purpose interface." — Interface Segregation ◆ "Depend on abstractions, not on concretions." — Dependency Inversion ◆

    The Profile · Issue 01

    Building the backbone of scalable products.

    A backend engineer's notes on three years of keeping the lights on — across fintech, logistics, med-tech, ed-tech, and e-commerce.


    Over three years, I have worked on production backend systems for teams that could not afford to be surprised. At MAP Systems the work was event-driven microservices — the kind that spend most of their time being unremarkable. At Uhunger it was APIs carrying more than 10,000 monthly transactions, where every failed call meant a customer left waiting. The brief changes; the discipline doesn't.

    I work in two ecosystems and switch between them without ceremony: Java with Spring Boot and Kafka where the domain calls for it, and Node.js with NestJS and Express where it doesn't — both paired with relational databases I trust to outlast me. I have built and maintained payment systems, wallets, and secure transaction flows integrated with Paystack, Flutterwave, VFD and Dotai. Reliability and data integrity are not the glamorous parts of the job; they are the job.

    "Reliability isn't a feature. It's the bill that comes due — and you pay it every day, in small careful decisions."
    — From the desk

    My core focus is backend engineering, system design, and service reliability. I am frontend-capable when a sprint asks for it, but the work I return to is architecture, infrastructure-aware design, and the long middle of maintainability — the years between ship and rewrite.

    Field Notes · The Toolkit

    The toolkit, by chapter.

    What I reach for, in roughly the order I reach for it. No logos, no leaderboards — just the things that show up in the work.


    Languages▮▮▮▮▮
    Java·TypeScript·JavaScript·SQL·Go
    Runtimes & Frameworks▮▮▮▮▮
    Spring Boot·Node.js·NestJS·Express
    Databases▮▮▮▮▮
    PostgreSQL·MySQL·MongoDB
    Architecture & System Design▮▮▮▮▯
    Modular Monoliths·Microservices·Event-Driven Architecture·REST APIs
    Caching & Messaging▮▮▮▮▯
    Redis·RabbitMQ·Kafka
    Platform & Operations▮▮▮▮▯
    AWS (EC2, S3)·Docker·GitHub Actions·Nginx
    Frontend (Secondary)▮▮▮▯▯
    React·Next.js·Tailwind CSS

    House RulesEverything above is applied to SOLID: one responsibility per module, open to extension but closed to modification, parts you can substitute without surprises, interfaces kept small, and dependencies that point at abstractions — never at implementations.

    "Always learning, always building." A short list today; a different one in twelve months.

    Career · In Chapters

    Where the work has happened.

    Six chapters of building backends — most recent first. Read in any order; the lessons compound.


    1. INow

      Moniepoint Inc.

      Jul 2026 — Aug 2026

      Internship · Lagos, Nigeria

      Backend Engineering Intern · DreamDevs Cohort 2

      Got in through DreamDevs, Moniepoint's engineering programme: HackerRank screening and live coding rounds, then the cohort itself from April to June. I made it through to an internship. Then came two months inside a payments platform at real scale, writing and maintaining Java backend services in production. Traced and fixed runtime failures that had been taking production services down, then worked through slow and misbehaving endpoints until the Apdex scores came back up. Paired with senior backend engineers and the engineering manager — the fastest way I know to learn how a system this size actually behaves.

      "Through DreamDevs, into production Java at payments scale."
    2. IIChapter

      Cognetik Technologies

      Sept 2024 — Jul 2026

      Full-Time · Remote

      Backend Engineer

      The brief shifted weekly. I designed and built backend services for a Learning Management System with automated grading and role-based access, then turned to an exam platform carrying twenty thousand concurrent candidates with zero downtime, then to logistics — shipment booking, tracking, workflows — then to real estate, where access control, billing, ticketing and payments all sit behind one API.

      "Twenty thousand concurrent candidates. Zero downtime."
    3. IIIChapter

      MAP Systems Inc.

      Dec 2024 — Aug 2025

      Contract · Manitoba, Canada (Remote)

      Backend Engineer

      Architected event-driven microservices with NestJS, RabbitMQ and MySQL — scalable, isolated, and quiet. Built the real-time spine for chat, voice and video, which lifted platform engagement by forty percent. Added multi-factor authentication and tighter access flows that materially reduced account-takeover risk. Deployed on AWS with Redis caching and held 99.9% uptime.

      "99.9% uptime. The rest is detail."
    4. IVChapter

      Uhunger

      Jan 2024 — Sep 2024

      Contract · Abuja, Nigeria (Remote)

      Backend Engineer

      Designed RESTful APIs that carried more than ten thousand monthly transactions for a food-delivery platform. Optimised database queries and indexing until response times fell by forty-five percent. Integrated Paystack and automated CI/CD pipelines, cutting release cycles by seventy percent.

      "Response times down 45%. Release cycles down 70%."
    5. VChapter

      ProcureRex

      Jul 2023 — Jun 2024

      Contract · Lagos, Nigeria (Remote)

      Backend Engineer

      Built scalable backend services for procurement and vendor management workflows. Designed secure wallet services integrated with Paystack for transaction processing, with steady attention to data consistency and reliability across financial modules.

      "Wallets, vendors, money — and the data behind them."
    6. VIChapter

      Intelligra Solutions Limited

      Mar 2023 — Aug 2023

      Internship · Remote

      Backend Engineer Intern

      First proper post on a backend team. Studied architecture and REST API design in production under senior mentorship. Built and tested endpoints, learned SQL in earnest, and took part in sprints, code reviews and the small daily acts of collaborative engineering.

      "Where the discipline started."

    — End of recorded chapters · Next one in progress —

    Selected Works · The Clippings File

    Pieces I've kept on file.

    Seven projects worth re-reading — open-source experiments and client builds, filed in the order I'd hand them to you.


    The Feature · Side Project · Networking

    Gotunnel thumbnail

    Gotunnel

    A tunnel I didn't need, built to find out how one works.


    Written in Go over a custom binary protocol with stream multiplexing, TLS and automatic reconnection. Exposes local HTTP and TCP services, with TCP tunnels locked to approved visitors by default. A personal learning project with a free, rate-limited hosted server.

    Go·TCP/IP·Binary Protocols·TLS·Multiplexing
    Kleari thumbnail

    Open Source · macOS

    Kleari

    A Mac cleaner that asks before it touches anything.


    A native macOS app in Rust and Tauri that finds space you can reclaim, explains each finding and its risk, and moves only what you approve into a quarantine you can undo. Live system readings, developer-cache cleanup and mouse tuning ride along. Everything stays on the Mac: no account, no telemetry, and the only request it makes is the update check, which CI keeps that way. Free and open source, provided as is.

    Rust·Tauri·React·TypeScript·SQLite·macOS
    Treeoh thumbnail

    Client Work · Logistics

    Treeoh

    Rates, routes and real-time tracking for domestic and international shipments.


    Backend platform for a logistics product. APIs handle rate calculation, shipment lifecycle, and live tracking across multiple carrier integrations, designed to scale with the catalogue rather than buckle under it.

    Node.js·NestJS·PostgreSQL·AWS
    Uhunger thumbnail

    Client Work · Food Delivery

    Uhunger

    Ten thousand monthly orders, one steady backend.


    Backend system for a campus food-delivery platform: order processing, live tracking, Paystack payment flows. Engineered to keep response times low at the dinner rush and the payment ledger honest the rest of the time.

    Node.js·Express·PostgreSQL·Paystack
    Learning Management System thumbnail

    Client Work · Ed-Tech

    Learning Management System

    Courses, assessments, and twenty thousand candidates writing at once.


    Backend for a learning platform: course management, grading workflows, role-based access. Built to absorb the spike that arrives on exam day without surprising anyone — including the operators.

    Node.js·NestJS·PostgreSQL·Next.js
    BuyTrek thumbnail

    Open Source · E-Commerce

    BuyTrek

    Carts, catalogues, payments — with the cache where it pays.


    E-commerce backend covering product catalogues, carts, orders and payments. Structured APIs with Redis caching for the hot paths and careful data consistency for the rest.

    Node.js·NestJS·MySQL·Redis

    — More in the archive —

    Letters to the Editor

    Write in.

    Roles, contracts, demos, questions, kindred projects. The address is below; the letterbox is open.


    Dear Praise,

    Sent straight to my inbox — I'll reply to your return address, usually within a day. Your approximate location, looked up from your IP address, is noted on my copy.


    Colophon

    "I invented the term object-oriented, and I can tell you I did not have C++ in mind."
    — Alan Kay

    Print Run

    Three years in circulation across fintech, logistics, med-tech, ed-tech and e-commerce. Readership measured in uptime, not clicks — a new edition ships whenever the backend does.

    Office

    England, United Kingdom.
    [email protected]


    © 2026 Bakare Praise Stephen. All rights reserved.
    Visits are logged with approximate location and time. IP addresses are not stored.

    Vol. I · No. 1 · Filed from England

    Return to the masthead ↑