alphalist.CTO Podcast

The episode contains genuine technical depth in specific stretches - ServiceNow's metadata-amplification architecture, the RaptorDB acquisition rationale, and the Windsurf productivity measurement - but roughly half the runtime is personal origin story, vague AI cheerleading, and market commentary that any tech observer would already know.

“we may issue four hundred queries to try to figure out how to do that for you on your behalf. So there's a big amplification between like the number of screens. We render and the number. database operations”

“I bought about seven thousand licenses. We trained seven thousand engineers on how to use it and we could demonstrate, we got about fifteen percent of a productivity bump out of that just measured as stories per engineer for sprint”

The anthropomorphic agent framing - creating a literal user account for an AI agent so it inherits all existing human governance rules - is a genuinely non-obvious product insight. The chess-boards analogy for vibe coding is fresh. Most other AI takes (lean in, incumbents have advantages, consumption pricing) are widely circulated.

“its an anthropomorphic paradigm, you literally go to be user table create a user called a ipad. if u want apat to work case us sign up at and like. it follows everything you've already done”

“AI coding If u get to that next level is like playing five Boards of Chess because you have multiple prompts spending time They're interrupting you when they finish, and then you've got to react”

Pat Casey is a rare genuine practitioner: employee number two at ServiceNow, hands-on coder for years, board member of MariaDB, architect of a proprietary database acquisition, and leader of 10,000 engineers through a 20-year growth arc - this is not a recycled thought-leader but someone who has actually built and scaled the thing being discussed.

“i was the first person other than fred uh to work on the codebase..and that was I think early two thousand five”

“it runs about, It's about ten thousand human beings, about seven thousand of whom wrote code or plausibly wrote code”

Technical specifics are strong and verifiable: 90K databases, 25 billion queries per hour, 97% Raptor Standard conversion, 7,000 Windsurf licenses, 15% sprint-velocity lift. Business and customer-outcome evidence is thinner - no named enterprise case studies, no revenue-per-agent figures, and productivity claims lack error bars or methodology detail.

“twenty five billion queries an hour”

“I think on like ninety seven percent of the way through converting my ninety thousand databases over to Raptor standard”

The host shows genuine preparation - citing a specific 2024 interview, tracking the Windsurf investment, asking about the single-tenant architecture trade-off - but questions frequently trail off into vagueness and there is almost no genuine pushback or follow-up when Pat makes bold claims about incumbent advantage or AI productivity multiples.

“So I think in an interview that i saw in the year twenty-twenty four you basically made big investment into windsurf licensees for all your engineers. um.. You said this brought ten percent productivity Back in the days”

“And did she ever... I mean your in a way running. then Postgres? Like how big is the difference between like your own proprietary form set or your own proprietory technology and core Postgres”