01Question02Build03Use
Making things.
Making sense.
Becoming.
I’m Robert. I build software, follow questions, and write about what I discover along the way.
An idea becomes
something useful.
I turn questions into products, then take responsibility for what happens when people use them.
Give it a purpose.
Then give it a life.
Product, engineering, and the responsibility
of staying with what you build.
MY CURRENT FOCUS · CLOSED BETA
rootmail.
Business email.
Every customer’s identity.
A record of what happened.
I designed, built, and now operate the platform, from the API and dashboard to the infrastructure and developer SDKs.
01 / IDENTITYONE PLATFORM. MANY CUSTOMERS.
The platform is shared.
The identity is theirs.
Your application
rootmail.One workspace
ACustomer ATheir domain & signing key
BCustomer BTheir domain & signing key
Workspaces and sub-tenants keep sending domains and signing keys distinct, whether you serve one business or many.
Architecture, simplified.02 / EVIDENCEFOLLOW THE MESSAGE.
“Sent” is just
the beginning.
- 01Request acceptedThe platform receives the request.
- 02Queued for sendingThe work moves into the sending pipeline.
- 03Provider event recordedKeep the signal and its source.
- 04A reply, when it arrivesAnother part of the conversation.
I built the record around what the system observes. A provider event is evidence; it isn’t a promise that someone read the message.
An explanatory lifecycle, not live message data.03 / OWNERSHIPBUILD IT. STAY WITH IT.
The whole product.
Including what’s underneath.
01The interfaceDashboard & customer experience
02The contractAPI, authentication & SDKs
03The engineQueues & sending infrastructure
04The responsibilityOperations, tracing & improvement
The product is the promise. Engineering is how I keep it, through the first build and everything that follows.
BEFORE ROOTMAIL / A FOUNDER’S PERSPECTIVE
The work matters.
So does working together.
Samuel MarseilleFounder, Oneshot TranslationFrom his recommendation · June 27, 2026
He treated our platform as if he owned it, because for all practical purposes, he did.
His infrastructure choices — Docker, CI/CD pipelines, proactive monitoring — reflected an engineer who thinks in systems, not just features.
For a non-technical founder, having an engineer who combines full autonomy with clear communication is invaluable — and rare.
We worked together from December 2024 to December 2025.
The platform behind these wordsBuilt. Tried.
Carried forward.
Oneshot
Translation.
A document translation business, built into a complete platform. Customer experience, automated processing, deployment and reliability.
~60%less turnaround time
99%+annual uptime
Inside the work
I built the frontend and backend, integrated third-party services, and automated document ingestion with AWS Lambda. Docker, CI/CD and monitoring supported the platform in production.
See this chapter in my journey ↗Intelligent
Writing Assistant
An experiment in making writing tools more useful, built with Python, FastAPI and React.
Explore the projectCloser to
the machine.
A custom printf in C. Learning systems by building the foundations myself.
Explore the codeSome questions
become essays.
Software, possibility, and the very human
business of figuring things out.
A few places to begin
THE POSSIBLEThe Developer codes
The Moment Starship Becomes Real.
Read the essayTHE PRACTICAL
The Developer codesIf-Match:
Read the essay
If-Match:
two curls, one 412.
Read the essay
THE PERSONALOur Curious MindsHe lives in you…
Read the essay
He lives in you…
in the simplest things.
Read the essayFind your kind
of conversation.
Pick a place that feels like you.
I’ll meet you there.
SubstackBuild. Write. Explore. Become.
Stay for the longer story.
Essays, questions and the work of becoming. Three publications, each with its own point of view.
Choose your notebookSubscribe here, just below.
LinkedInOdinaka Robert Nnamani
Build a professional connection.
The engineer, the founder, and the thinking behind the work. A place to connect around what we could build together.
X@paschals_robert
Join the thought while it’s forming.
A shorter route into the conversation: ideas, questions and the people thinking about what comes next.
X may ask you to sign in.
Medium@robertpaschal
Follow an idea a little further.
Another home for my writing. Find a story, take your time with it, and follow along on Medium.
DEV@robertpaschal
Get into the details.
Software, implementation and learning through the work. Find me in the developer community and join the discussion.
01 / 05
Different notebooks.
The same curiosity.
Choose the part that speaks to you.
Let the next piece come to you.
01 / THE WHOLE JOURNEYPascal.
Build. Write.
Explore. Become.
The home for what I’m building, what I’m learning, and who I’m becoming.
Explore the notebook ↗
02 / UNDER THE SURFACEThe Developer
codes.
Understand the tools.
Imagine what comes next.
Software, emerging technology, and the ideas changing what we can build.
Read the publication ↗
03 / THE HUMAN PARTOur Curious
Minds.
Stay open.
Follow the feeling.
Stories, reflection, and the small things that help us understand ourselves.
Read the publication ↗Signups are handled by Substack. Unsubscribe whenever you like.
Somewhere
in the middle.
I don’t think we become
ourselves all at once.
I studied biological sciences, trained in software engineering, built products for other people, and started building one of my own. The route hasn’t been a straight line. The curiosity has stayed.
01 / THE CURIOSITY
A way of looking.
Biological sciences taught me to look closely at systems. Software gave me a way to build them.
Follow the path02 / THE CRAFT
A way of making.
I care about the whole product: the experience on screen and the infrastructure nobody should have to think about.
See it in the work03 / THE REFLECTION
A way of understanding.
Writing is where I take the questions left over: ambition, creativity, failure, and building a life that feels like my own.
Find it in the writingA home for a life
in progress.
Pascal began with a question:
what if I shared the becoming, too?
A path. A point along it. Not an arrival.I build things to make an idea useful. I write to understand what the work asks of me. Pascal gives both a place to live — including the uncertainty.
01The line keeps going.
The flowing mark reminds me of a path. My own has moved from biological sciences into software, from building for others to building Rootmail. A turn in the path doesn’t erase what came before it.
02One home for all of it.
The P carries the Pascal name. I didn’t want the technical work and the person doing it to live in separate boxes. Software, creativity, ambition, and the questions left after the laptop closes belong in the same story.
03Here. Still on the way.
The little blue dot is a point along the path. It gives the mark a place to pause without making that place the finish. I don’t need to have everything figured out before I can share something worth reading.
“You don’t have to wait until you’ve arrived
to have something worth sharing.”
A path.
Always unfolding.
ALX Africa
Software engineering · Training & projects
Learn it.
Build it from scratch.
From C and a UNIX shell to APIs, databases and distributed systems. A foundation built through the work itself.
One of those foundations ↗JUL 2023 — AUG 2024Oneshot Translation
Full-Stack Software Engineer
A whole platform.
A business depending on it.
Working directly with the founder, I turned business goals into a complete product, then took care of it in production.
The founder’s perspective ↗DEC 2024 — DEC 2025Outly Technologies
Chief Technology Officer
Build the product.
Listen to the market.
I led engineering for a consumer marketplace. We built, but traction didn’t follow. That chapter belongs here too.
Making software is one part of finding something people need.FEB — JUN 2026Rootmail
Founder & Principal Engineer
An idea of my own.
A responsibility I chose.
Building and operating an email platform through a closed beta. Product, engineering and the next decision, all in the same hands.
Back to what I’m building ↗JUN 2026 — PRESENTStill becoming.
The detours belong in the story, too.
Still a way forward.
01Change direction.Biological sciences to software
02Learn from the attempt.Outly, and the questions it left
03Begin again.Rootmail. Writing. The next question.
FROM THE CHANGE OF DIRECTIONBegin before
Begin before
you feel ready.
Biological sciences wasn’t the end of my story. Learning software meant being a beginner again — and finding another way to follow the same curiosity.
FROM THE THINGS THAT DIDN’T LANDLet the attempt
Let the attempt
teach you.
At Outly, we built a product; traction didn’t follow. That experience stays with me. Building something and finding something people need are different kinds of work.
FROM BEGINNING AGAINKeep making.
Keep making.
Keep making sense.
Rootmail gives the next attempt a shape. Writing gives me a place to examine the decisions, doubts, and discoveries along the way.
Stay for the next chapterWhat could we
make happen?
A team. An idea. A question you can’t shake.
I’d like to hear it.
Independent work.
Shared possibility.
If something I build or write has meant something to you,
you can be part of what comes next.
Buy Me a Coffee
A little fuel for
the next idea.
For the build that saved you time, or the essay that stayed with you. A small thank-you can be encouragement to keep making.
Coming soonFollow the journey
Patreon
Give the work
room to grow.
Back the time behind the work: the experiments, the rewrites, and the ideas worth staying with. A way to support the long game.
Coming soonFollow the journey
Bring someone along
Good work travels
person to person.
If something here stayed with you, pass it to someone who might need it. Or join a notebook and be part of what comes next.