AI Is Changing DevOps, but Production Access Is Still the Line
Three filters, blast radius, rollback and visibility, decide which IoT DevOps tasks AI may touch. Production access stays human.
Writing
AI is an analyst, not an executor. Blast radius, rollback and visibility decide what it may touch, and judgment still has to be trained.
Three filters, blast radius, rollback and visibility, decide which IoT DevOps tasks AI may touch. Production access stays human.
AI erodes the entry-level work that builds engineering judgment. Four practices to keep juniors thinking instead of parroting output.
Four ways AI assistants create IoT technical debt, backed by studies, and three disciplines to contain it: review, no-go zones, refactoring.
Where a 90-developer IIoT team gets real value from AI agents (prototyping, tests, routine code) and why ISO 27001 blocks autonomy.
Why AI tooling tires engineering teams through micro-decisions and tool sprawl, and how to adopt it without burnout.
Why Shadow AI, Copilot-style vulnerabilities and automation bias threaten businesses, and four controls from corporate LLM access to data residency.
Where LLMs fit in Industrial IoT: interpreting ML predictive-maintenance output, RAG over manuals, protocol interoperability. Humans decide.
Five steps from a real Copilot Agent rollout: baseline KPIs, CI/CD embedding, prompt training, an AI policy, and scaling.
Five readiness checks for scaling cloud AI: data quality thresholds, elastic GPU capacity, MLOps orchestration, security KPIs, monitoring.
Why predictive maintenance still needs vibration analysts: scarce matched training data, missing operational context, noisy sensors.
How a PdM pipeline turns bearing vibration into FFT spectra and alerts, plus six infrastructure steps an IT team must prepare.
I'm always interested in thoughtful conversations about technology, engineering organizations, AI and ambitious products.
Get in touch opens LinkedIn in a new tab. Email reaches [email protected].