Ile-Ife, Nigeria

Hey, I'm Daniel.I build software..

I'm a software engineer at TestFlow, where I work on the backend behind computer-based testing: how questions are delivered, scored and turned into something students can actually learn from.

Most of what I build is on the server side, APIs, background jobs and the data behind a product. I also ship the interfaces, because a backend nobody can use is only half a product.

Calder, Intake and ORREI are what I'm building now. This is where they live.

Open to freelance projects and interesting collaborations.67 public repos812 commits
selected work03

TestFlow

Live

selected work01

Calder

In development

Drag me

currently shipping

const emerald = {
  role: "backend",
  mode: "ship it"
}

on the bench

Calder: email API

ship it.

2,600+

commits & counting

SWE @ TESTFLOW

Scroll to explore

What I do

Things I can help you build.

I work across different parts of software development, depending on what a project needs. Here are some areas I spend most of my time working in.

01of 04

Backend Development & APIs

I enjoy working on the parts of an application that users don't necessarily see but depend on every day. From authentication and database design to APIs, background jobs and third-party integrations, I focus on building systems that are reliable, maintainable and make sense as a project grows.

Node.jsTypeScriptPostgreSQLPrismaNeonQueues
keep scrolling
02of 04

Full-stack Development

I build web applications from the ground up, working across the frontend and backend to make sure everything fits together. That means thinking about the data, application logic, user experience and all the little details that make a product enjoyable to use.

Next.jsReactTypeScriptTailwind CSS
keep scrolling
03of 04

Developer Tools & Automation

I like finding ways to make repetitive work less repetitive. I've worked on bots, integrations and automation tools that connect services and simplify everyday development workflows. I'm also exploring how AI can fit into the tools developers already use.

PythonTelegram Bot APIMCPGitHub APICI/CD
keep scrolling
04of 04

Frontend & Interface Development

I care about how software feels to use, not just whether it works. I enjoy building clean interfaces, thoughtful interactions and responsive layouts. Things like loading states, transitions, accessibility and small usability details matter just as much as the main functionality.

ReactNext.jsFramer MotionTailwind CSSDesign Systems
that's the set
Selected work

A few things I've been working on.

Each of these started with a problem I kept running into. What follows is what the thing is, the decision that shaped it, and where it stands today. Real projects, with the engineering decisions written down.

Selected work01/ 04
selected work01

Calder

communication infrastructure

01 / 04
In developmentSolo developer: architecture, API, worker and dashboard.

Calder

Developer-first communication infrastructure.

Every application needs to communicate with its users. I kept running into the same problem whenever I worked on a new product: setting up transactional email meant rebuilding much of the same infrastructure. That's what led me to start Calder. It's a transactional email API with its own queue, background workers, AWS SES integration and dashboard. The idea is to give developers a straightforward way to handle application email without having to manage all the underlying infrastructure themselves. I'm building it with the intention of expanding beyond email into other communication channels.

TypeScriptNext.jsPostgreSQLAWS SES
Visit live site
selected work02

Intake

describe, review, create

02 / 04
LiveSolo developer: full-stack development, AI pipeline and provider integrations.

Intake

Describe, review, create.

Creating a form shouldn't mean spending the next twenty minutes clicking through settings and arranging questions. Intake lets you describe the form you want in plain language. It interprets your request, puts together a proposed structure and lets you review everything before creating the form in your Google Forms or Typeform account. I built it around a simple idea: people should spend more time thinking about what information they need and less time figuring out how to collect it.

TypeScriptNext.jsNeonBetter Auth
Visit live site
selected work03

TestFlow

in students' hands

03 / 04
LiveSoftware engineer, backend.

TestFlow

Exam confidence for Nigerian university students.

TestFlow is a computer-based testing and practice platform for Nigerian university students. Students practise questions across their courses, sit timed tests, read explanations and track progress against a study plan. I'm a software engineer on it, working on the exam engine: question delivery, scoring, study-plan progress and the services that hold the practice experience together. It's the work I'm proudest of, because a mistake in the code is a student's wasted study session.

Next.jsNode.jsPostgreSQLQuestion Bank
Visit live site
selected work04

ORREI

ORVN Labs

04 / 04
In development · Private betaPlatform engineering, data modelling and publishing workflow.

ORREI

A property deserves better than a forwarded PDF.

ORREI is being developed under ORVN Labs for real estate wholesalers and disposition teams in the United States. The idea is to take property information that's often scattered across documents, messages and spreadsheets and turn it into a structured, shareable presentation for potential buyers. One of the things I care about most with this project is data accuracy. Property information needs to retain its source, and AI-generated suggestions shouldn't automatically become published facts. People should be able to review and approve information before it goes live.

TypeScriptNext.jsNeonPostgreSQL RLS
Visit live site

scroll, 4 cards to go through

And the rest of the wall

Client work, experiments and ideas I've enjoyed bringing to life.

CypherHTML
Shipped

Cypher

A project that lets you control a Windows PC from your phone over your local network. It includes screen streaming, clipboard synchronisation, file transfers and session pairing without relying on cloud servers.

BlueprintTypeScript
Alpha

Blueprint

An exploration of what an AI-powered engineering workspace could look like. It combines codebase intelligence, architecture decision records and local-first indexing to help developers understand and work with their projects.

PhoneDockKotlin
In development

PhoneDock

An ongoing project exploring better ways to connect phones and computers. The goal is to support things like screen sharing, file transfers, clipboard synchronisation and using a phone as a second display.

Attack on TitanTypeScript
Live

Attack on Titan

An experimental, cinematic web experience inspired by the visual world of Attack on Titan. I used it to explore animation, transitions, image-led layouts and unconventional navigation.

LIFELINKTypeScript
Prototype

LIFELINK

An emergency health identity concept built around the idea of a digital twin. The goal is to make important health information accessible when someone cannot communicate for themselves.

FormakTypeScript
Experiment

Formak

A small design and development experiment exploring claymorphism, soft shadows, rounded surfaces and playful interactions.

Noma FormTypeScript
Experiment

Noma Form

An exploration of how typography can influence the experience of filling out a form, using type as the main visual element rather than relying on decorative components.

This PortfolioNext.js
Live

This Portfolio

The website you're currently exploring. I built it to bring together my projects, writing, GitHub activity and a little bit of personality.

drag the line to see the rest

GitHub

A look at what I've been building.

I enjoy sharing my work publicly, whether it's a finished project, a small experiment or something I'm still trying to figure out. My GitHub is where most of that work lives. You'll find applications, experiments, utilities and the occasional idea that got a little out of hand.

0 public repositories2,622 contributions / year184 active days

0 contributions in the last year

synced from my pins

LessMore
Follow me on GitHub: @Emerald-dev0

new pins appear here automatically

About

A little more about me.

I write software for a living and mostly on the server side. Databases, APIs, background workers, the parts that have to stay standing when a product gets busy.

I got here by building things. An idea, a weekend, a problem I did not yet know how to solve. That loop never really stopped, and it is still how I learn fastest: ship something small, find out what I got wrong, fix it properly.

I care about the reasoning behind a decision, not just whether the code runs. Why this schema, why this queue, why not the simpler option. That is the part of engineering I find worth writing down, so I do.

Alongside the client work I build my own products. That is where the harder lessons are, because nobody hands you the requirements and nobody tells you when to stop.

currently

building
Calder, communication infrastructure for developers.
learning
System design and distributed systems.
reading
Designing Data-Intensive Applications.
listening
Whatever happens to be playing on Spotify.

Software engineer

Backend, APIs and data

Ile-Ife, Nigeria

UTC+1

Building in public

Projects, decisions and things I got wrong.

Open to freelance

Backend and full-stack work.

Usually working on something

even when I should probably be sleeping.

a human, not a résumé

Currently listeningWhat I'm listening to while building.A little soundtrack to the projects, late-night debugging sessions and everything in between.Pulled live from Spotify.
Process

From an idea to something people can use.

I like keeping projects straightforward. Good communication, clear expectations and regular progress make a huge difference.

  1. 1

    Understand the problem

    Before jumping into code, I'd like to understand what you're trying to achieve, who you're building it for and what success actually looks like. Sometimes the best first step is figuring out what doesn't need to be built.

    you get: A clear scope and agreed direction.
  2. 2

    Work out the approach

    Once we understand the problem, I'll work through the structure, technical decisions and user experience. If there's something particularly important or uncertain, I'd rather test it early than discover problems halfway through development.

    you get: A practical plan and an early look at the solution.
  3. 3

    Build and share progress

    I prefer working in smaller, manageable steps rather than disappearing for weeks and returning with a surprise. You'll have something to review as development progresses, and we can address feedback along the way.

    you get: Regular updates and working features.
  4. 4

    Get it live

    We'll get the application deployed, check that everything works as expected and take care of the final details. I'm also happy to help with fixes and improvements after launch.

    you get: A deployed product and a proper handover.
Content

I share what I'm learning along the way.

I enjoy documenting my experiences as a developer. Not just the finished projects, but the decisions, mistakes, tools and lessons that come with building software. Everything I write ends up on the blog first.

Daniel at a laptop, sunglasses on

I write to think, then publish so the thinking survives.

Mostly the decisions behind the software: why a schema looks like this, why a queue was worth it, why the obvious approach was the wrong one.

the blog is where it lands first

Building in public

Updates from projects I'm working on, things I've shipped and the occasional bug that took far longer to fix than it should have.

Learning as I go

Notes on concepts I'm working through, things I got wrong the first time and what I'd do differently now.

Tools and technology

Honest thoughts on developer tools, frameworks and technologies I've tried. What worked, what didn't and what I'd recommend to other developers.

Contact

Have something you'd like to build?

Maybe you have an idea you've been thinking about, an existing product that needs some work or a technical problem you're trying to solve. I'm always open to interesting projects, freelance opportunities and conversations with people building useful things. Tell me a little about what you're working on. We can take it from there.

the form is faster, I read every one

Prefer email? [email protected]