The latest update to the OpenTofu infrastructure-as-code (IaC) tool is making it simpler to update and refactor configurations without having to rework the entire codebase. Version 1.12.0 of OpenTofu has added a destroy = false lifecycle option that enables DevOps engineers to drop an object from state without issuing a destroy application programming interface (API) call. Previously, any time a resource was updated or added an API call would try to destroy the actual infrastructure behind it. While DevOps teams could work around that issue by carefully maintaining state, the chances that something could go awry were fairly high. Now OpenTofu 1.12.0 allows DevOps teams to tie prevent_destroy to an input variable within the same module. Once set to default, the API call to destroy the IT infrastructure environment is overwritten. That per-stack variable configuration means DevOps teams can define the safety behavior once per environment and have it stay consistent across every run. ...
Engineering roadmaps inside enterprises that never planned to build AI products are now being eaten by AI work. Teams at hospitals, banks and government agencies are spending huge chunks of their sprint capacity wiring up models, UI components and accessibility plumbing for AI features that aren’t core to what their business actually does. The mismatch between where the work is going and where the value is created is starting to force a different conversation about what belongs in-house and what doesn’t. Mike Hideo, VP of Software Engineering at TinyMCE, joins Mike Vizard to argue that the next layer developers will commodify is the AI trust layer — the governance, control, provenance and UI components that wrap every LLM-driven feature. The case is straightforward: writing a prompt is cheap, but building reliable audit trails, permission models and accessible interfaces around AI output is the part teams keep rebuilding from scratch with every new model release. The conversation g...