The Ledger
Every statement that passed quotation and attribution checks. Mix any filter with any other: certainty 1/5, debate potential 5/5, or both at once.
why aren't all 9 resolved? a statement only gets an assessment when the public record can support or contradict it. opinions and what-ifs never can, and 0 checkable ones are still open, waiting for their date. predictions held up or didn't; assertions are supported or contradicted. on every card: ▮▮▮▮▮ certainty · ▮▮▮▮▮ debate potential. speakers are clickable
Daigle: GitHub uses Microsoft Teams for video, but keeps Slack for ChatOps
“So we use teams for video communication, like, but we don't use it for chat.
We get home for a long, long history, right?
We always talk about chat ops and like, everything is built into slack, like every command, every flow, even though you have been acquired…”
Daigle stealthily generated GitHub's executive revenue deck using custom AI
“I built like a little app just to make it so I could look at some of the information in a SQLite database more easily. And I ultimately built this entire presentation without touching any of it. And I was like, okay, I'm just going to present this to our CRO, …”
Daigle: GitHub will never hide source code in low-code abstractions
“When we put a veneer on top of something, we still always show you the code that's kind of like a tenant. We're never gonna, like, hide the code from you ever because what, like, yeah, it's the whole point, you know.”
Daigle: GitHub Actions expansion drives massive CPU demand across data centers
“Some of the growth issues which is why we're, I was talking about you know, pushing hard on more CPUs is in actions in particular more tools, more agents, more PRs mean more builds in more CPUs. And so we are expanding through not just our data center, but obv…”
Daigle: GitHub's permissioning bottlenecks stem from a legacy 'MySQL 1' database
“The place that we continue to have pain is in permissioning. And so, right now, many of our permissioning layers sit into a database that we, like, internally call MySQL one, and old Hubbers will know what I'm talking about.”
Daigle: GitHub distributes internal AI CLI skills across non-technical staff
“What we've actually ended up doing is
We've built like a set of you know, skills internally.
We have like, we each have our set of skills and we've just been distributing even to the non-technical folks, the CLI.
And then effectively we're just giving it acces…”
GitHub uses Azure dev compute for fast, isolated AI agent VMs
“We have a new underlying agent containerization service. It's like through, we're using it under the hood. It's through Azure. They recently announced it. The Azure like dev compute, but it's like very fast very fast compute to be able to like spin up you know…”
Daigle: GitHub Copilot tools and agents share a single unified SDK
“Also have now had, now have like a single underlying SDK and harness for our coding agent, you know, co-pilot ultimately the new CLI, the new desktop app, cloud agents that use the same SDK.”
GitHub deploys Microsoft's WorkIQ context engines to its internal developers
“These little, like oversimplifying it context engines are wild good, and, like, we've given them to our developers at GitHub. We've given them to employees at GitHub as we've used these tools to be able to just ask questions around
Everything that you have in …”