About Brian Childress
I've been building software since the early 2000s. Over 20+ years I've worked as a senior engineer and application architect inside venture-backed startups and large financial institutions, shipping production systems at every scale, from pre-launch products to platforms handling millions of accounts. I hold multiple U.S. patents for software design, including work in application security.
My work centers on a simple observation: most systems don't fail because they're too small. They fail because they got too complicated to understand, and nobody could safely change them anymore. I'm the person who arrives when releases have become rare and risky, finds where complexity crept in, removes what isn't earning its keep, and leaves behind a system the team can actually move on. In one case that meant cutting cloud spend 25% by deleting an entire data layer rather than optimizing it. In another, taking a platform from roughly weekly releases to multiple safe deploys a day.
Recently my focus has been helping teams adopt AI-assisted development without drowning in code they can no longer comprehend. It's a new version of the same old problem: powerful tools producing systems nobody fully understands. I work on it hands-on, in the code, not from a slide deck.
How I work
I get into the actual codebase, look at the pull request history, understand the team structure, and trace the path that got the system here. The technical problems and the organizational problems are almost always connected.
I work directly alongside the people who own the code. The goal isn't a report; it's a team that ships confidently after I'm gone.
I write about what actually worked, what it cost, and what I'd do again. No growth-hacking, no hot takes. You can read through the blog to get a sense of how I think.
Want to talk through a system?
Start with a 30-minute call. No pitch, no prep required. Just tell me what's going on.