AI for your role

AI for DevOps / Platform

Ship infrastructure faster with AI handling the boilerplate, not the decisions.

Get the DevOps / Platform brief
The shift

How AI is changing the DevOps / Platform role

In 2026, AI is taking over the repetitive parts of infrastructure work: drafting Terraform and Helm charts, explaining failing CI/CD pipelines, and summarizing logs during incidents. Assistants now read your stack traces and Kubernetes events and suggest concrete fixes instead of generic advice. The shift is moving engineers from typing YAML to reviewing and approving AI-generated changes.

What AI can take off your plate

  • Drafting first versions of Terraform, Helm charts, and Dockerfiles
  • Reading and summarizing long pipeline logs and stack traces
  • Grouping and deduplicating alerts during an active incident
  • Generating runbook drafts and post-incident timeline summaries
  • Writing routine shell scripts and kubectl one-liners

What stays distinctly human

  • Deciding architecture tradeoffs and what the platform should optimize for
  • Judging acceptable risk before a production change or rollback
  • Setting on-call expectations and protecting the team from burnout
  • Owning security and compliance decisions with real accountability
  • Negotiating priorities and SLAs with product and other teams
Tools

Five AI tools for DevOps / Platforms

GitHub Copilot
Autocompletes Terraform, Dockerfiles, and shell scripts inline and explains unfamiliar config blocks in your editor.
Try it →
Claude
Pastes in a 500-line Helm chart or stack trace and gets a plain explanation plus a corrected version you can review.
Try it →
Cursor
Edits across an entire infrastructure repo, refactoring modules and updating variable references in one pass.
Try it →
k8sgpt
Scans a Kubernetes cluster for misconfigured pods, failing probes, and resource issues and writes the diagnosis in plain English.
Try it →
PagerDuty AIOps
Groups related alerts during an incident and surfaces the likely root cause so on-call engineers see one summary instead of fifty pages.
Try it →
Prompts

Five prompts to try today

Paste these into Claude or ChatGPT and replace the bracketed parts with your own details.

1. Explain a failed pipeline
Here is the full log output from a failed [CI tool] job: [paste log]. Identify the exact step that failed, the root cause, and the minimal change to fix it. Do not suggest unrelated improvements.
2. Write a Terraform module
Write a Terraform module for [resource, e.g. an AWS RDS Postgres instance] with [requirements: multi-AZ, encryption, 7-day backups]. Use variables for all environment-specific values and include sensible defaults and outputs.
3. Debug a Kubernetes pod
My pod is stuck in [state, e.g. CrashLoopBackOff]. Here is the output of kubectl describe and the container logs: [paste]. List the most likely causes ranked by probability and the command to confirm each.
4. Review a change for risk
Review this [Terraform/Helm/YAML] diff for production safety: [paste diff]. Flag anything that could cause downtime, data loss, or a security regression, and note what I should test before applying.
5. Draft a runbook
Write a runbook for handling [incident type, e.g. database connection pool exhaustion] on [service]. Include detection signals, immediate mitigation steps, rollback procedure, and who to escalate to.
The playbook

Every AI play for DevOps / Platform

Your full AI playbook for your role — updated every week. Tap any card for a step-by-step walkthrough and examples.

✦  New AI plays are added every week — and go straight to subscribers in their morning brief. Skip the scrolling and get yours delivered free. Get my free brief →
Loading the library…

A day in your inbox

This is the kind of brief a DevOps / Platform gets, every weekday morning.
Monday morning
✦ Personalized for: DevOps / Platform
Engineering PlaybookDebugging
Read the stack trace with a second pair of eyes

You hit an error you have not seen before. Instead of blind guessing, make the model narrow the search first.

Claude (free)  FREE  reads code and error output, explains likely causes

Paste the failure

Give it the error and the code that threw it.

Here is a stack trace and the function it points to. Language: [language]. List the 3 most likely root causes, ranked, with the exact line each one points to. Stack trace: [paste full trace] Code: [paste function]
Ask for the cheapest check

Get a way to confirm before you change anything.

For your top cause, give me one log line or one-line check I can add to confirm it before I edit anything.
Fix and verify

Apply the fix yourself, then run the failing case again. Do not paste secrets or customer data into the prompt.

You stop guessing and test one theory at a time. You still write the fix and run it.

Your role, all in one place
  
Tools, prompts & tricks
Your full library, one tap away.
›
  
Your playbook
Every entry, building each week.
›
  
How AI is changing your role
Where your work is heading.
›

You’re subscribed as DevOps / Platform.  ·  Update your roles  ·  Manage preferences  ·  Unsubscribe
The Morning Current · Powered by Atomic Media Group, LLC

Get the DevOps / Platform brief

One AI play, built for your role, every weekday morning. Free.

You’re in! We just emailed your first brief — it should land in a minute. Add brief@themorningcurrent.com to your contacts so it never hits spam.
Free forever. Unsubscribe anytime. We use your role only to personalize your brief.