Hey — I'm Opeyemi 👋 A software developer. Most of my work is #frontend, but these days it just as often means #backend or #mobile-development.
Five years in, most of that on React, Next.js and TypeScript. I've built the kind of software that has actual users attached to it — a review platform businesses run on, a producer dashboard, a contract workspace — and a marketplace app that's live on the Play Store.
More recently I've been working behind the interface too: Prisma schemas and APIs over Postgres, and a Telegram bot that watches Base for new token launches and scores them for rug risk. I'm not going to call myself a backend engineer — but I can design the schema, write the endpoints, and ship the thing without waiting for someone else.
I've also started wiring up #ai-automation— n8n workflows that read an event, decide what it means, and act on it without me in the loop. The first one qualifies and replies to every inbound lead on my own site within a minute, and it's running live right now.
What I care about, in order:
- The interface should be quick. Not “fast for a web app” — quick.
- It should work on the phone someone actually owns, not the one in the mockup.
- Nothing should shift, flash, or lie about what it's doing while it loads.
- If a thing can fail, the screen should say so plainly.
This site is the argument, not just the claim: every image here is served pre-sized with its own placeholder, and the whole thing runs on almost no JavaScript.
Alongside the work I'm finishing a degree in Mathematics with Computer Science, which turns out to be less of a detour than it sounds. I'm into where AI is pushing interfaces, and I'm learning Solidity at the moment — the frontend problems I find interesting keep drifting on-chain.
👀 Three off the top of the pile. The rest live in #work and #mobile.
Every inbound lead scored and replied to within a minute — no one waits.
A live marketplace on the Play Store, wallet and all.
Review collection that businesses actually get replies from.