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
Ideas on AI, engineering, leadership, technology businesses and complex systems, published elsewhere and collected here.
Three filters, blast radius, rollback and visibility, decide which IoT DevOps tasks AI may touch. Production access stays human.
What broke when his company grew from 10 to 90 people, and the four management shifts that fixed it.
AI erodes the entry-level work that builds engineering judgment. Four practices to keep juniors thinking instead of parroting output.
Why burnout is a management problem, with the story of keeping a 90-person team working after the invasion of Ukraine.
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.
Three signals to invest in developer training, how to tie it to business goals, and how to measure ROI, with a $10,000-a-month cloud saving as the example.
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.
How to spot a skills gap early (quality drops, lead overload) and close it with 360 reviews, development plans and mentoring.
Five leadership skills AI cannot replace, illustrated with situations from running a 90-person engineering team.
Five practices for Ukraine, US and Europe teams: a written communication policy, agreed progress reporting, audience-adapted presentations, a knowledge base.
A concrete cadence for developer growth: tests, sprint experiment days, monthly clubs, and how to diagnose a stalled engineer.
How to pitch refactoring to executives as ROI: cost the legacy burden, cite Southwest and Netscape, pilot one module first.
Why technical leaders over-control, a five-step delegation system, and the team that shrank a 16 TB database to 1 TB on its own.
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.
How a predictive-maintenance team keeps AI diagnostics accurate: field-experienced analysts, three time zones, two-tier triage, custom tooling.
Five big-data mistakes from running a 16 TB, ten-billion-records-a-day platform: retention, quality, uncapped autoscaling, surplus fields, wrong database.
Per-sensor fault signatures for an electric motor: vibration, temperature, current and motion amplification, with thresholds and six implementation steps.
Four traits that mark product-minded engineers, and the retention practices behind five-to-eight-year average tenure.
A role-by-role plan for starting production data analytics and predictive maintenance, with the barriers and the expected downtime reduction.
From Waddington's RAF bombers to a four-stage IIoT pipeline: how modern predictive maintenance works and why it is bought as a service.
The business case for IIoT predictive maintenance: downtime costs, ROI, implementation challenges, and build versus buy.
Why queries slow down at IIoT scale, and how a PdM platform cut latency from 10 s to 2 s by moving to TimescaleDB.
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].