Why we’re starting JoonaPay Engineering
A place to explain the engineering decisions behind financial software, with room for the whole team to write.
Financial software raises questions that deserve more space than a short social post.
What does a payment timeout actually tell us? How should an integration communicate uncertainty? Where does a technical decision become an operational responsibility?
JoonaPay Engineering is a place to work through those questions in writing.
What belongs here
The focus is payments, software architecture and building financial infrastructure for Francophone Africa. Articles can explain a technical idea, examine a tradeoff or make a useful connection between an industry development and the work of building software.
A useful explanation should make its assumptions visible. A hypothetical example should be called a hypothetical example. A claim about a particular technology should point to its documentation.
A place for engineers to write
This blog is built around Markdown files. Each article has a title, a short description, a date, topics and named authors. Engineers can write in their editor and review an article through the same Git workflow they use for code.
The aim is to make the reasoning accessible: enough detail for another engineer to learn from it, and enough context for a technical leader or partner to understand why it matters.
Follow along
Browse the articles, meet the authors, or subscribe to the RSS feed.
You can also follow Ben on LinkedIn and X for shorter notes and discussion.