This blog is a place to be honest about building and running software for a living: the architecture, the politics, and the drama that comes with being a founder for a decade.
Who writes here
The author is a long-time software engineer and founder who has spent over 20 years building enterprise platforms, most recently as a co-founder and Chief Software Engineering Officer of a life and annuity policy administration SaaS company. The posts blend deep technical experience in Java, cloud infrastructure, and regulated insurance workflows with the realities of running a company where ownership, control of infrastructure, and strategic direction are all live issues.
What the blog covers
On the technical side, expect posts about Java, Spring Boot, plugin architectures, and design patterns that actually survive in production SaaS systems, not just in interview questions. There will also be practical writing on cloud deployment, CI/CD, SOC 2–friendly architectures, and the kinds of engineering tradeoffs that show up when uptime, auditors, and clients are all watching.
Founder life and internal politics
Another thread here is founder and partner dynamics: who controls the AWS, GitHub, and Google Workspace accounts, how equity and board power translate into day‑to‑day leverage, and what happens when those relationships break down. Some posts will dig into internal politics around “cause,” repurchase rights, vesting, and how governance and personal trust can diverge sharply once real money and control are on the line.
Clients, contracts, and projects
There will be posts about managing enterprise clients: setting expectations, negotiating contracts, navigating security questionnaires, and keeping projects alive when scope, budget, or internal champions move. The goal is to be candid about how to structure deals, communicate risk, and still ship working software in industries that care more about compliance and stability than shiny features.
Ten years of SaaS drama
Finally, this blog will talk openly about the drama of spending a decade building a SaaS company: the slow grind of implementation projects, the emotional cost of founder disputes, and the tension between building product and putting out fires. If you are a developer, architect, or founder who has ever wondered whether everyone else’s journey is as messy as yours, these stories, patterns, and scars are for you.