Excited to share my talk from Nordic APIs' Platform Summit 2025. As the opening talk of the event, I wanted to address the elephant in the room head-on: MCP.
Block's open source initiative is helping to build brand reputation, attract talent, boost partnerships, guide internal open source best practices, and aid long-term system reliability.
Achieving ROI with AI requires a mix of strong leadership stewardship upfront, shifting the talent framework, and embedding proper monitoring and governance throughout the lifecycle.
I recently explored what goes into creating a solid AI agent knowledge base — from the types of data it should contain to the retrieval mechanisms and architecture patterns that support reliable agentic behavior.
I recently spoke with LinkedIn VP of Engineering Prashanthi Padmanabhan about the making of their Hiring Assistant, an agent recruiters are using to optimize the applicant selection process.
How do you fail at platform engineering? Make it 100% UI-first. Don't market it. Survey no one. Measure success by who's onboarded. And just copy what others are doing.
MCP shines for indeterministic workflows, novel integrations, and giving AI coding agents context on the fly. But for more predictable automation it may be overengineeering.
For my latest DirectorPlus column with LeadDev, I synced with JB Brown, VP of engineering at Smartsheet, to learn about their multi-agent AI development strategy.
Alternative clouds are having a moment. Nearly 75% of orgs are using two or more alt clouds beyond the hyperscalers, according to a HostingAdvice.com report.
In a multi-agent coding workflow, an engineer leads a "team" of specialist AI agents to perform various SDLC tasks: scaffolding, coding, testing, log analysis, deployment, and more.
Open-source software churn is accelerating. With more frequent version end-of-lives and even total project abandonments, it's harder than ever to keep up.
I covered a report from HostingAdvice.com, which found that the majority of programming language migrations are driven by hype, instead of proven outcomes.
Facing an existential crisis, Stack Overflow has had to pivot quickly. I synced with a director to discover what team strategies are helping them adapt.