Alan Shimel

Alan Shimel sits down with Leslie Pascual, Field Engineering Manager for AI and Security Solutions at ActiveState.

Claude Code, OpenAI Codex, GitHub Copilot, Cursor and a growing field of challengers are competing to define the future of software.

AI-assisted development has quietly changed which part of the software lifecycle is hardest. Writing code is no longer the bottleneck.

Most enterprises never fully finished the DevOps transformation they started a decade ago. Agentic coding is now surfacing.

Anaconda no longer wants to be known only as the company behind the Python distribution.Its acquisition of Kilo Code adds a model-agnostic agentic engineering layer used by more than 3 million developers. Combined with its earlier acquisition of Outerbounds, Anaconda is assembling the pieces of a broader enterprise AI development platform.Alan Shimel examines why the deal is complementary to Anaconda’s Python roots, how the GitLab relationship may have helped bring the companies together and why Kilo may not be Anaconda’s final acquisition.Read the article: [ARTICLE LINK]#EnterpriseAI #AgenticAI #Python #OpenSource #DeveloperTools #DevOps

Tucker Callaway sat down with Alan Shimel at PlatformCon 2026 to walk through how his team is trying to move that needle in public.

AI coding assistants have made it trivially easy to ship software faster — and that is precisely the problem.

Kubernetes automated infrastructure coordination.AI agents are starting to automate operational reasoning itself.That’s a much bigger leap than most people realize.The industry spent the first phase of AI obsessing over models and copilots. The next phase is going to be about orchestration, governance and operational trust.That’s the bigger signal behind the latest Automation Anywhere announcements.My latest piece explores why the automation layer increasingly wants to become the operational runtime for enterprise AI.#AI #EnterpriseAI #PlatformEngineering #CloudNative #Automation #DevOps

GitLab’s “Act 2” announcement is about a lot more than layoffs or AI agents.This feels like a defining moment for a company that helped shape DevOps culture itself.The real question:Can GitLab reinvent itself for the agentic era without losing the operational philosophy that made people trust it in the first place?I took a deep dive into:Sid Sijbrandij’s original visionGitLab’s “open book” cultureBrendan O’Leary’s critiqueReddit operator reactionsand what this says about the future of DevOps itselfI still find myself rooting for them.

CI/CD was built around a comforting idea: Software should do tomorrow what it did today, assuming the inputs are the same.