Operations | Monitoring | ITSM | DevOps | Cloud

More and more often, infotainment systems are being developed and delivered like software, yet often they are still tested and validated using hardware-centric processes. This is far from ideal: access to devices is limited, environments are difficult to reproduce, and iteration slows down as soon as multiple teams need to work in parallel. These challenges become even more visible as cockpit systems move toward wide displays and high resolutions.

AI is creating an overwhelming surge of digital artifacts and software components. The key to success is learning how to ride, secure, govern, and manage that wave – rather than being overwhelmed by it. This weekend, I asked my team to watch Chasing Mavericks. Jay Moriarity (not J-Frog, but stay with me) was one of the most driven and determined surfers imaginable. His courage and spirit were extraordinary. But those virtues were shaped and refined by his mentor, Frosty Hesson.

The bell rings. Last call for 398-day certificates is March 15. After that, every CA is required to cut you off at 200 days. Some have already stopped serving them early. The rest follow in two weeks. The irony of good certificate management is that when it works, nobody notices. No alerts, no outages, no 2am pages. The only time it gets attention is when something expires. Which means the teams doing it well rarely have the budget or the political capital to fix the process before it breaks.

Cloud migration strategies range from quick rehosting to complete application refactoring. Lift and shift migration (also called rehosting) moves applications from on-premises to the cloud with minimal changes, promising speed and lower initial costs compared to other strategies. But does lift and shift actually deliver long-term savings? This guide examines when lift and shift makes sense, when it creates hidden costs, and what alternatives exist.

As digital transformation accelerates, the underlying infrastructure supporting your enterprise or service provider network faces unprecedented pressure. The exponential growth of data, driven by cloud computing, 5G, and particularly Artificial Intelligence (AI), demands a fundamental rethink of how you approach connectivity.

This is part two of a series of the implications of AI generated code becoming mainstream. We recently wrote about how AI-generated code is overwhelming SRE teams with production complexity they can’t manage. Turns out that’s only half the problem. The other half shows up on the cloud bill. A prospect reached out to us last month. They’d been using Cursor and Claude Code for six months, shipping features at unprecedented velocity. Product was thrilled.

The MySQL ODBC driver is what keeps BI tools, reporting systems, and ETL pipelines connected to MySQL without errors. Teams have depended on it for years, and it’s still vital today, especially with MySQL ranked worldwide in February 2026. However, not all ODBC drivers are built alike. There are two categories: open-source options and commercial ones. While both connect applications to MySQL, they differ in areas like stability, performance, security, and support.