When critical open source goes end of life...
Bill Doerrfeld | August 8, 2025
My latest for The New Stack explores how to respond to OSS EOLs
What do you do when critical open source projects you depend upon go end of life?
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.
In my latest for The New Stack, I share strategies to protect your stack and reduce risk when critical OSS projects go EOL.
Check it out for some good future-proofing strategies as well as tips on how to react if you're caught off guard.
My latest on InfoWorld reviews MCP servers from 5 major cloud providers
How are organizations actually using agentic knowledge bases in practice? My article for The New Stack looks at six emerging patterns.
My report for the eBPF Foundation explores enterprise eBPF case studies, production deployments, and real business outcomes across cloud-native environments.
Longtime Bottomless user sharing why I love automated coffee delivery triggered by a smart scale, plus a referral link for a free first bag.
MCP servers can quickly drain context windows without guardrails. Thankfully, there are ways around this, say the experts.
It may seem like AI agents are suddenly doing everything across industries. But in reality, the pace of agentic AI is moving carefully, and very deliberately, in highly regulated environments like finance and banking.
My latest feature for InfoWorld explores when it makes sense to scrape public web sources, and when official API integrations are the better choice for external data.
What does it mean to go nano with your software updates — to "carve with a scalpel" instead of swinging a hammer? For my latest DirectorPlus piece, I caught up with Chainguard VP Dustin Kirkland to dig into that idea.
I recently moderated a webinar that brought together three luminaries in the API community to discuss the importance of API standards in agentic AI development.
The more folks use MCP servers in development, the more they’re realizing it can lead to runaway token usage, unpredictable response sizes, and flooded context windows.
