Anyshift.io

Someone changed a Terraform config on Jan 5. It broke prod on Jan 26. The drift was visible the whole time. Nobody saw it. Annie would have flagged it on Jan 6. Your team would have fixed it Tuesday morning. Not 3am Saturday.

Someone changed a Terraform config on Jan 5. It broke prod on Jan 26. The drift was visible the whole time. Nobody saw it. Annie would have flagged it on Jan 6. Your team would have fixed it Tuesday morning. Not 3am Saturday.

Someone changed a Terraform config on Jan 5. It broke prod on Jan 26. The drift was visible the whole time. Nobody saw it. Annie would have flagged it on Jan 6. Your team would have fixed it Tuesday morning. Not 3am Saturday.

Someone changed a Terraform config on Jan 5. It broke prod on Jan 26. The drift was visible the whole time. Nobody saw it. Annie would have flagged it on Jan 6. Your team would have fixed it Tuesday morning. Not 3am Saturday.

AI Builder #10 💫: Jeffrey Snover | PowerShell inventor, Google Distinguished Engineer For Jeffrey, the most underrated shift in AI is the dramatic reduction in cost. “Engineering’s all about trade-offs.” And the cost assumptions behind those trade-offs keep changing. His point: don’t just make the same system cheaper. Ask what you would build if you had 1,000 times more capacity. But cheaper doesn’t mean more reliable. At Harvard, he’s building a neurosymbolic system that combines LLMs with explicit rules and checks. Why? “There are things where the errors matter.” Being able to explain a decision matters too. And where would he put $10M? “I would short frontier models.” He thinks the efficiency gains ahead could undermine the economics of today’s most expensive models. Thanks Jeffrey for joining us!

"At a business level nothing is precious. Everything is disposable.” AI Builder #9 💫: Eli Schleifer | CEO & Co-founder, Trunk What changes when you can test a product idea in a day instead of spending months building it? For Eli, AI changes more than how fast engineers write code. It changes how quickly they can learn, change direction, and throw away something that doesn't work. His most effective teams today? “Teams of like two or three.” Smaller groups, larger areas of ownership, with each engineer guiding their own agents. And maybe the hardest skill to learn: getting comfortable deleting what you just built. As Eli puts it, “We should be very happy to throw away our most precious things if they're getting in the way.” Thanks Eli for joining us!