Operations | Monitoring | ITSM | DevOps | Cloud

In 2008, Nuance hired me to join their Healthcare Speech Recognition team as a “Release Engineer.” DevOps wasn’t a thing yet — Patrick Debois and Andrew Shafer wouldn’t hold their first “DevOpsDays” until 2009. But I was lucky that “Release Engineer” at Nuance meant “jack of all trades” who wrote Makefiles, bash scripts, Perl, and Java to build and release code to a fleet of hundreds of on-premise Linux machines.

To read more on the findings from this research, visit the Digital Sovereignty Revolution whitepaper by clicking here. For years, global hyperscalers have been the backbone of cloud infrastructure for UK businesses. Their scale, reach, and performance made them the default choice. But as geopolitical uncertainty grows and concerns around data governance deepen, the cracks in this model are beginning to show.

A recent study looked at real-world Python programs and found something important: Python isn’t the main reason apps slow down. The real problems come from inside the code like poor logic, memory issues, and slow database queries. The problem is, these issues often go unnoticed. Your app may seem fine until users start complaining about slowness or things start breaking under pressure.

Yesterday, like many others in the tech community, I found myself pausing to fully grasp the implications of the Microsoft SharePoint hack. As one of the most widely adopted document management and collaboration platforms globally, SharePoint’s compromise inevitably sends ripples of concern through businesses everywhere. This news reminded me of a conversation I had just last week with an enterprise customer. We were discussing how one might approach cybersecurity from a hacker’s perspective.

Attestations, or as we like to call them, evidence, are a critical piece to proving software supply chain integrity and security. However, without the right tools and processes, reviewing and verifying attestations can be time-consuming. At JFrog, we’re deeply committed to empowering developers, DevOps, and Security teams to make these complex workstreams as simple as possible.

Banks and financial institutions operate in one of the most complex, highly regulated and risk-averse industries.

In this case study, we’ll tell you how Alloy’s solutions have become a key asset in our client’s journey towards digitization.

There’s a hard truth in IT: everyone wants automation, but nobody wants to wait six months (or more) to get it off the ground. Traditional automation initiatives are often bogged down in backlog, scripting complexity, and integration chaos. That’s exactly what makes agentic workflows different. Agentic workflows don’t just automate tasks; they act. They understand intent, operate autonomously, and improve over time.

The Quest For The Five Minute Deploy Speed is everything at incident.io. The faster we can test and ship code, the faster we can get new products and features out to customers. Over the last three years, as our codebase grew and our test suite expanded, we drifted away from our own goals: "We aim for less than 5 minutes between merging a PR and getting it into production." This is the story of how we got back on track.

Background task processing is something that many developers may encounter when building Elixir applications. This might include sending emails asynchronously, posting and fetching data from an API, and more. Oban, a powerful and persistent job processing library, offers a reliable way to handle background tasks, scheduled operations, and more. However, like any complex system, Oban requires careful monitoring to ensure its smooth operation, identify bottlenecks, and prevent unexpected failures.