Posts

Featured

So, Who The Hell Is David Oduse?

If you've landed on this blog for the first time, you might reasonably wonder who is behind all these random articles about software, security, infrastructure, products, and whatever else I happened to become interested in. I'm David Oduse . I'm a software engineer, product owner, techpreneur, and an endlessly curious person who has somehow made a habit of turning curiosity into software. I build things. I break things. I fix things. I think things. And, when something teaches me something interesting, I write about it. That's probably the simplest way to explain this website. I Didn't Really Plan for It to Become This My path into tech has been driven more by curiosity than by some perfectly structured career plan. I've always enjoyed figuring things out. How does this system work? Why was it designed this way? What happens if something fails? Can this process be made simpler? What happens if someone tries to abuse it? Could I build one myself? ...

Before Monesize Was a Company, It Was My Spreadsheet

How a personal bookkeeping habit, a few Google Forms, and about 25 individual setups eventually led me to build a software company. I didn't set out to build a software company when I started keeping records of my finances. I wasn't researching the accounting software market, looking for a startup idea, or trying to identify a gap in the Nigerian technology ecosystem. I simply wanted to keep better track of my money movements. On January 1, 2024, I started recording my expenses using Google Forms and Google Sheets. I wanted a simple way to document what I spent, when I spent it, and what I spent it on. I didn't want to rely on memory, scroll through bank transaction histories whenever I needed to understand my spending, or guess where my money had gone at the end of the month. I wanted records. Actual records. What started as a personal financial tracking exercise eventually became the foundation of Monesize, a company that has since taken me through product development, cu...

Building Infrastructure Observability at Monesize

Infrastructure monitoring became a priority at Monesize after we experienced firsthand how difficult it can be to diagnose production problems without a centralized view of system health. We have individual servers running the company's services, application logs available through PM2, and AWS providing infrastructure status. However, these sources did not give us one place to understand what was happening across the infrastructure when something went wrong. The problem became clear during a production incident in which I could no longer access the backend over SSH, even though the EC2 instance still appeared as running in the AWS console. More critically, all the applications running across the infrastructure became inaccessible through their web interfaces, and the monitoring endpoints also stopped being accessible. This was not an isolated backend issue. The outage affected the applications themselves, while the backend logs also exposed database and Redis connectivity problems...

One Identity, Many Products: Engineering Monesize Gateway

Image
Today, Monesize has become a company offering a suite of independent business software products. Core handles finance and operations. Desk manages customer support. Engage runs sales and CRM. Books handles accounting, with more adjacent products in the long-term roadmap.  Each product has its own domain and can operate independently, allowing a business to adopt the products it needs without having to adopt the entire suite. Monesize Gateway That independence is deliberate, but it introduces a platform-level problem as the product portfolio grows. Each product naturally wants to maintain its own users, authentication state, and understanding of which people belong to which organization. That works while the products are isolated. It becomes increasingly difficult once the same business starts using multiple Monesize products. A business using three products should not have to manage three unrelated identities for the same employee. An employee leaving the organization should not re...

Startup Theatre and the Illusion of Progress

There is something increasingly strange about the way people start startups today. The barrier to producing software has fallen so dramatically that someone can have an idea in the morning, spend a few hours prompting an AI coding tool, have something that looks like a product by evening, buy a domain, generate a logo, put together a landing page, change their LinkedIn headline to “Founder & CEO,” and announce to the world that they have launched a startup. The announcement gets a few congratulations, someone asks whether they are raising, another person offers to make an introduction to an investor, and suddenly there is a feeling of momentum. But what actually moved? This is a phenomenon I eventually termed " startup theatre ." It is the production of all the visible artifacts associated with entrepreneurship without necessarily doing the difficult work that makes those artifacts meaningful. The pitch deck exists. The MVP exists. The company name exists. The LinkedIn an...

Building a Self-Hosted SIEM for Monesize Infrastructure

As Monesize's infrastructure keeps growing, security monitoring had to evolve beyond checking individual servers, reviewing application logs and responding to vulnerabilities when they surface. A production environment generates too much security information for that approach to remain practical. System logs, application events, package inventories, authentication activity and network traffic all contain useful signals, but those signals become much more valuable when they can be collected centrally and investigated in context. That led us to build a self-hosted Security Information and Event Management system, or SIEM, for Monesize. The objective was not simply to install a security dashboard. We wanted a central security monitoring layer that could collect telemetry from our workloads, identify vulnerabilities in installed software, inspect network activity, generate security alerts and give us a single place from which to investigate what was happening across the environment. We...