Stonetusker Insights

Engineering Deadlines, Checklists and Technical Notes

Start with the Delivery Deadline Radar for every dated change in one list, or the Delivery Checkup for five numbers that show where delivery waits. The checklists give eight plain questions for each of five kinds of engineering organisation. The technical notes each take one change and show how to check it.

By Subeesh Sivanandan, Founder, Stonetusker Systems · Updated 6 November 2026

Start here

• Delivery Deadline Radar: 22 Engineering Dates From 2025 to 2029
  For: Engineering leaders who want every dated change that touches delivery in one list, each with a check one engineer can run.
• How Long Does a Merged Change Wait? Five Delivery Numbers, With One Measured on Prometheus
  For: Any team with Git and a build pipeline.

Checklists by archetype

• Could Your Firmware Team Name Every Exposed Device Within a Day? Eight Questions for Device Makers
  For: Leaders of teams that ship firmware or connected devices in embedded, defence, automotive, energy or telecommunications products.
• Would Your Last Release Survive an Auditor's First Request? A Checklist for Regulated Software Teams
  For: Leaders of engineering teams in healthcare, medical technology, financial services, public sector or education, where every release has to stand up to an audit.
• Before the Next Traffic Peak: Eight Questions on Ingress, Certificates and Rollback for High-Traffic Platforms
  For: Leaders of platform and release teams in ecommerce, travel, gaming, streaming or advertising, where an outage at peak costs revenue.
• Which Model Answered That Request? A Lineage and Runtime Checklist for Machine Learning and Data Teams
  For: Leaders of teams that build model or data platforms, or ship products with models inside them.
• .NET 8 and 9 End on 10 November: A Runtime and Pipeline Checklist for Cloud Software Teams
  For: Leaders of engineering and platform teams at cloud software companies, security vendors or enterprise internal systems groups.

Topic notes

• 100-Day Certificates From March 2027: The Renewal Arithmetic, the Validation Window and the Clients That Keep Up
  For: Anyone with a public website, interface or device endpoint.
• Your Git History Already Holds the Before Picture: A Year-on-Year Test for Coding Assistants
  For: Teams that use coding assistants, or plan to.
• Bitnami Charts Still Point at Images Frozen in August 2025. What Replaces PostgreSQL, Redis, Kafka, MongoDB and RabbitMQ
  For: Teams that deploy Bitnami container images or Helm charts.
• Zero Hashes Counted, 2,403 in the File: Testing the 2026 Software Bill of Materials Elements on a Real Record
  For: Teams that sell software or devices to United States government, regulated or large enterprise buyers.
• The Cyber Resilience Act Gives You 24 Hours to Warn. What That Means for Products on Yocto Kirkstone
  For: Teams that ship firmware, devices or software products into the European Union.
• European Union Device Rules, 2026 to 2027: Which Dates Are Law and Which Are Only Requested
  For: Teams that ship firmware or connected devices into the European Union
• A Model Card Names the Training Data but Not Its Version. Annex IV of the Artificial Intelligence Act Asks Where It Came From
  For: Teams that build or ship artificial intelligence features to European Union customers.
• Ingress NGINX Is Out of Support. Here Is What ingress2gateway Converts, and What It Leaves to You
  For: Teams that run Kubernetes with the community Ingress NGINX controller.
• Three Weeks to Black Friday: Rehearse the Rollback Before You Agree the Freeze
  For: Ecommerce, travel, gaming and streaming teams, and any business with a seasonal peak.