I'm Ogechukwu Macpherson Dieze — most people just call me Macpherson.

I'm a full-stack software engineer based in Nigeria. I realized I hadn't actually introduced myself properly on this Journal yet, so here's that: who I am, what I actually do, and what this space is generally about.

What I do

I take web products from idea to production — not just the interface, but everything underneath it: user workflows, APIs, data modeling, authentication, deployment, and the work that comes after launch to keep a system healthy.

My core stack is React, Next.js, TypeScript, Node.js, firebase, supabase and MongoDB. I work across the whole stack because I think a product should feel coherent for the people using it and maintainable for the people running it — those are two different jobs, and most engineers lean toward one at the expense of the other.

Some things I've built

A few projects that show the range of what I work on:

- Dayli Energy Solutions — a full-stack platform for selling solar products (panels, batteries, inverters), with inventory tracking, customer ordering, and secure authentication baked in.

- Smart Study Platform — an AI-powered tool that takes raw academic content and restructures it into digestible, interactive learning material in real time.

- AI Crop Disease Detector — built during the West African Buildathon (Build with AI), an event focused on solving local problems with AI.

- GLITEC Ecosystem — the site for GLITEC Advanced School of Technology.

- OTPGenerator — a small, focused tool: a one-time password generator with a countdown timer, built with Vite and React.

You can see the full breakdown of these (and more) on the homepage or projects page.

How I work

I front-load ambiguity rather than let it show up mid-project — that means milestone maps, clear interface contracts, and checkpoints the client can actually see progress at, not just take my word for. On the technical side: typed surfaces, regression gates, accessible UI by default, and telemetry that's actually useful when something breaks in incident week, not just documentation nobody reads.

What this Journal is for

I use this space to write about the things I run into while shipping production software — latency budgets, data modeling decisions, release hygiene, the stuff that doesn't make it into a project description but matters a lot in practice. If you've read some of the earlier posts here, this one's just filling the gap of a proper introduction.

If you're building something and want to talk through scope, I'm currently open for new project briefs — you can [get an hourly estimate] quote or [reach out directly] contact.