About Me

Hi, I'm David Oduse.

I'm a software engineer, product builder, entrepreneur and an endlessly curious person with a strong interest in enterprise software, distributed systems, security engineering, and the practical realities of building products that businesses depend on every day.

This blog is where I document that journey.

Some posts are about software architecture. Others explore cybersecurity, product development, engineering decisions, or lessons learned while building real systems. Occasionally, I write about ideas that don't fit neatly into any category. The common thread is simple: I enjoy understanding how complex systems work and sharing what I learn along the way.

My Journey

My path into technology has been driven by curiosity more than anything else.

I enjoy solving difficult problems, whether that means designing reliable backend systems, understanding how vulnerabilities are exploited, improving operational workflows, or building products that simplify complicated business processes.

Over the years, my interests have expanded beyond writing software. Today, I spend a significant amount of time studying system architecture, accounting systems, enterprise operations, cybersecurity, and the relationship between technology and business strategy.

I believe good engineering is about much more than writing code. It is about designing systems that remain correct when things fail, that are understandable by the people maintaining them, and that solve meaningful problems for the people using them.

Building Monesize Core

Much of my recent work revolves around Monesize Core, an enterprise operations and financial platform designed for growing organizations.

Rather than treating accounting, inventory, payroll, purchasing, projects, compliance, and reporting as disconnected systems, Monesize Core brings them together on a single operational foundation.

One of the ideas that has shaped the platform is that business operations should naturally produce financial records. Instead of entering the same information multiple times across different systems, operational events generate the accounting records that reflect what actually happened.

Building Monesize Core has exposed me to challenges far beyond application development. It has involved designing event-driven architectures, implementing reliable accounting workflows, integrating with government APIs such as HMRC Making Tax Digital, thinking deeply about permissions and organizational structure, and constantly refining both technical and product decisions.

Many of the engineering articles on this blog are inspired by problems encountered while building the platform.

Security Engineering

Alongside software engineering, I have developed a growing interest in cybersecurity and offensive security.

I actively study penetration testing, vulnerability research, secure software design, and infrastructure security. Much of this learning comes through hands-on practice, where I explore realistic attack scenarios, document exploitation techniques, and then explain how those vulnerabilities can be prevented.

For me, security is not separate from software engineering. Building reliable systems also means understanding how they fail, how they can be abused, and how they should be defended.

Many of the security write-ups published here are intended to explain not only what happened during an assessment, but why it mattered and what lessons can be applied in real production environments.

Why I Write

I write because writing is how I think. Sometimes that thinking revolves around software architecture or security. Other times it wanders into philosophy, society, history, business, or whatever question happens to occupy my mind. This website exists because I enjoy following those questions wherever they lead.

Whenever I solve an interesting problem, whether it involves distributed systems, Linux infrastructure, accounting engines, or security testing, I find that writing about it forces me to think more clearly about the decisions I made and the trade-offs involved.

Most articles here are based on real work rather than hypothetical examples. Sometimes they document successful implementations. Sometimes they describe mistakes, unexpected failures, or lessons learned after something did not work as planned.

My goal is not simply to explain what I built, but why I built it that way.

What You'll Find Here

Topics on this blog include:

  • Enterprise software engineering
  • Backend architecture and distributed systems
  • Cybersecurity and penetration testing
  • Secure infrastructure and DevOps
  • Product engineering
  • Business software design
  • Linux administration
  • Software reliability
  • Engineering lessons from real projects
  • Technology thoughts
  • Essays on random ideas that don't fit neatly into a category

The content reflects my own experiences, opinions, and observations. It should not be interpreted as representing the views of any employer, client, organization, or project unless explicitly stated.

Looking Ahead

Technology changes quickly, but the principles behind good engineering tend to endure.

I expect my interests will continue to evolve over time. Today that includes enterprise software, accounting systems, and security engineering. Tomorrow it may include operating systems, compilers, distributed databases, or entirely different areas of computer science.

Whatever I happen to be exploring, this blog will continue to serve as a record of that journey.

Thank you for stopping by.

I hope you find something here that teaches you something new, challenges the way you think, or simply reminds you that every interesting engineering problem has a story behind it.