The story, told as evolution

1 Software engineer

I've spent twenty-five-plus years building software, including engineering work at Dell, Bank of America, AMCS, and SentryOne. The formative lesson: most complexity in software is accidental, and most of it comes from systems that were never designed to work together.

2 Product & platform thinker

Building products taught me a repeating pattern: inside every good feature there is a smaller product trying to get out, and under every good product there is a platform capability nobody has extracted yet. Booking is an engine, not a feature. Queries are a language, not a dialog box. Decomposition became my habit.

3 Founding Sneat

Sneat started from an observation I couldn't unsee: family life runs on nine-plus apps that share nothing. The fix isn't a better app — it's a shared graph of people, events, assets, and money that many focused apps read and write. Each new app makes every existing app more valuable.

How that chaos looks from a family's side is told in the Sneat origin story — seven panels, one kitchen, and a wall of sticky notes.

4 Ecosystem engineer

Following that logic honestly led me beyond one company's products. Shared data must be user-owned — so OpenVaultDB. Storage must be swappable — so DALgo. Dozens of modules must stay coherent — so SpecScore and GraphSpec. Knowledge itself needs graph-native navigation — so this site. That practice — products, standards, infrastructure, and teams designed to reinforce one another — is what I call ecosystem engineering.

🧱 What stays constant

• Make complexity understandable — clarity is a feature.
• Connect vision, architecture, branding, and execution as one act of design.
• Build environments where talented people do the best work of their careers.
• Prefer systems that compound over features that impress.

💬 In colleagues' words

From LinkedIn recommendations across two decades — executives, direct managers, teammates, reports, and clients.