The hottest DevOps Substack posts right now

And their main takeaways

“A spate of outages, including incidents tied to the use of AI coding tools”, right on schedule

Marcus on AI • 11659 implied HN points • 10 Mar 26

🕹 Technology DevOps

AI can write code quickly, but maintaining and debugging that code over months or years is much harder. Passing tests once is easy, but long-term reliability is where AI currently fails.
AI-assisted coding has already contributed to real outages that required emergency engineering responses. Some of these failures affected large parts of systems and had a high blast radius.
For mission-critical systems, even small errors can be dangerous, so humans will still be needed to oversee, debug, and maintain AI-generated code for the foreseeable future.

A Beginner’s Guide to Bring Your Own Cloud

Technically • 18 implied HN points • 26 Mar 26

🕹 Technology DevOps

Customers in security- or compliance-sensitive industries increasingly want to run software in their own cloud, and they will pay 2–5x for that control to meet data residency, security, performance, and cloud-choice requirements.
Deployment sits on a spectrum—from fully managed multi-tenant SaaS to single-tenant, hybrid (control plane + customer data plane), and fully self-hosted BYOC—each option trading convenience for control and observability.
BYOC can be very lucrative for vendors but brings big operational headaches: installs, upgrades, debugging, and lost visibility get harder, so it works best when buyers have strong platform teams and vendors are prepared to support the complexity.

Earn And Learn

Software Design: Tidy First? • 2010 implied HN points • 18 Feb 26

🕹 Technology DevOps

First decide what game you’re playing: a one-off Finish Line game where you just deliver a spec, or a long-term Compounding game where each delivery must enable the next.
The Finish Line approach focuses on features and specs and can be sped up by automation or agents, but it ignores future complexity and will fail when requirements or maintenance pile up.
The Compounding approach balances building features with investing in futures—tidying, architecture, tools, and practices—so the system can keep earning resources and grow over time.

Now Claude Code Gets New Features: Auto Mode, Dispatch, Remote Control, Voice, /loop & The Complete Setup Guide with 60+ Prompts

The Product Channel By Sid Saladi • 3 implied HN points • 26 Mar 26

🕹 Technology DevOps

Claude Code quickly became an autonomous agent platform, adding features like voice, remote control, persistent agents, multi-agent code review, scheduled tasks, and more.
Auto Mode uses an AI safety classifier with a two-layer probe and a Sonnet-based transcript filter to auto-approve or block actions, cutting down on manual permission clicks. It’s safer than skipping permissions but still has measurable false negatives, so you should review and customize trust boundaries.
Dispatch and other updates let a desktop agent run always-on and be controlled from your phone, while /loop and a large prompt library make it easier to automate coding workflows. Built-in defaults and setup guides help you configure these features safely.

Building Solo

Madhur’s Writings • 84 implied HN points • 09 Mar 26

🕹 Technology DevOps

Launched two consumer products while solo to learn end-to-end product building and shipping real apps.
Leans heavily on AI coding assistants and reusable agent skills to speed up development and design work.
Picks pragmatic, cost-conscious, and privacy-first infrastructure and services—hosting (Vercel/Hetzner/GCP), Cloudflare R2 for storage, Neon for databases, GitHub Actions for CI/CD, Stripe for payments, and Resend/Zoho for email, plus analytics like PostHog and Google Analytics.

Get a weekly roundup of the best Substack posts, by hacker news affinity:

Many tokens make all bugs shallow & open source’s new maintainers | Chainguard's Dan Lorenc

Dev Interrupted • 42 implied HN points • 17 Mar 26

🕹 Technology DevOps

Token costs for AI tools are an operational expense employers should cover, not a substitute for pay; companies need to provide the compute and subscriptions engineers need to do their jobs.
Agent-driven development requires treating agents like workers you manage—set up harnesses, clear guardrails, and plan carefully so AI-generated work doesn’t create technical debt.
The rise of agents reshapes risk and the ecosystem: expect permission and outage problems, new markets that sell to bots, and pressure on open source maintainers unless automation helps sustainably fill the gap.

Backfills - The Necessary Evil of Data Engineering

SeattleDataGuy’s Newsletter • 906 implied HN points • 23 Feb 26

🕹 Technology DevOps

Backfills are an unavoidable part of data work — you need them when source data is corrected, pipelines have bugs, or schemas and logic change.
They’re hated because they can be expensive, slow, and risky at scale, can disrupt downstream users, and erode stakeholder trust when numbers shift unexpectedly.
Design for safe backfills by building parameterized, rerunnable pipelines, adding strong data quality checks, communicating changes clearly, and using table-swaps or other strategies when partitions or immutable storage formats make in-place fixes risky.

What security categories will stay relevant

Frankly Speaking • 203 implied HN points • 04 Mar 26

🕹 Technology DevOps

Many traditional app-level security tools are at risk because large language models can replicate their core workflows, and a category becomes especially vulnerable if big model providers build it or if security teams can cheaply build it themselves with LLMs.
The strongest security companies will be those with real moats — unique data, sensors, infrastructure, and network effects that give them cross-customer visibility and make their detections hard to replicate.
Expect a build renaissance: teams can now create custom AI-driven security tooling cheaply, which reduces buying, makes technical debt easier to manage, and rewards AI-native companies and talent who can operationalize models.

exe.dev: a new hosting solution for your prototypes

Bite code! • 1223 implied HN points • 17 Feb 26

🕹 Technology DevOps

exe.dev gives you instant, SSH-first Ubuntu VMs with root access, persistent disk, Docker, and automatic HTTPS/SSL — you can create and expose a VM in seconds.
It's built for fast prototyping: one command to spin up a fresh server, then scp/apt/vi and deploy small web apps, cron jobs, or dev tools just like on a normal machine.
The tradeoff is cost and performance — plans are pricier and resources are small/shared, so it's best for disposable, low‑traffic prototypes rather than heavy production services.

Kubernetes for Data Engineers

VuTrinh. • 859 implied HN points • 03 Sep 24

🕹 Technology DevOps

Kubernetes is a powerful tool for managing containers, which are bundles of apps and their dependencies. It helps you run and scale many containers across different servers smoothly.
Understanding how Kubernetes works is key. It compares the actual state of your application with the desired state to make adjustments, ensuring everything runs as expected.
To start with Kubernetes, begin small and simple. Use local tools for practice, and learn step-by-step to avoid feeling overwhelmed by its many components.

Your engineers need an AI control plane, not more tools | Guild.ai’s James Everingham

Dev Interrupted • 74 implied HN points • 10 Mar 26

🕹 Technology DevOps

Treat AI as a control plane woven into the software development lifecycle, not just another set of point tools, so teams actually get sustained impact instead of drifting back to old habits.
Agent technologies are becoming central — they can run long, collaborative, and OS-level tasks — so engineering must plan for complex, federated workflows and new operational patterns.
Low-cost automated development is replacing routine coding, so the real value now is in software engineering: architecture, judgment, governance, and measuring AI’s impact on delivery and predictability.

The Emerging "Harness Engineering" Playbook

Artificial Ignorance • 273 implied HN points • 22 Feb 26

🕹 Technology DevOps

Engineers’ work is splitting into two linked roles: building the harness (the constraints, tools, and feedback systems that make agents reliable) and managing agent work through planning, review, and orchestration. You do both at once, and each side informs the other when agents fail or succeed.
Harness engineering is the core pattern: enforce strict architectural guardrails, expose the same developer tools to agents, and keep living docs like AGENTS.md that are updated whenever an agent makes a mistake. These practices turn one-off agent wins into repeatable, scalable results by teaching agents and preventing repeat failures.
Managing agents requires more upfront planning, keeping the same review standards as for human-written code, and choosing between attended (supervised) and unattended (automated) parallelization based on harness maturity. Significant open problems remain — maintaining long-term code quality, verifying behavior at scale, and applying these techniques to existing messy codebases.

The Great Connection Pool Meltdown

Jacob’s Tech Tavern • 3280 implied HN points • 06 Nov 25

🕹 Technology DevOps

Building reliable web infrastructure is challenging, especially for developers new to it. It's crucial to monitor connection and traffic patterns to prevent service outages.
Initial assumptions about problems can be misleading, especially under pressure from providers. Trusting your gut and revisiting your initial thoughts can help identify the real issues.
Designing systems that can handle failures is essential. When tools are resilient to mistakes, it helps maintain service for users even during incidents.

SAT Scores vs. On-the-Job Performance

Generating Conversation • 163 implied HN points • 26 Feb 26

🕹 Technology DevOps

Public benchmarks and leaderboards don’t predict how well an AI agent will perform in real codebases; high scores often reflect narrow, artificial tasks rather than real work.
Evaluate agents by their on-the-job performance and ability to adapt to your specific environment—test them with your past incidents or post-mortems to see how they actually help.
Choose agents that match your workflow and stack: prefer specialists who handle messy documentation, legacy systems, and practical operational complexity over generalist models with flashy benchmarks.

Will deception become cool again in the AI age?

Frankly Speaking • 152 implied HN points • 18 Feb 26

🕹 Technology DevOps

Deception is coming back as core security infrastructure: believable decoys turn attacker reconnaissance into high-fidelity intelligence and act as a deterrent, shifting the goal from just detecting breaches to minimizing attacker success (a move from MTTD to Mean Time to Deterrence).
Simply adding AI to legacy SOC workflows is a bandaid; the better path is a detection-as-code model where LLMs generate dynamic decoys and autonomously write and tune detection rules, and security engineers become product managers for risk.
Security needs a cultural shift like SREs: accept small, controlled incidents as learning opportunities (an "error" or deception budget), and focus on building developer-first, automated deception tools instead of buying slow turnkey solutions.

What It Actually Takes to Build a Data Pipeline System

SeattleDataGuy’s Newsletter • 718 implied HN points • 14 Jan 26

🕹 Technology DevOps

A reliable pipeline system needs many core components—secure secrets and connection management, rich logging and monitoring, dependency tracking, execution routing, scheduling, data quality checks, pipeline definitions, and a usable UI—because missing any of these creates ongoing operational headaches.
Operational practices like idempotency and easy backfilling, clear ownership, alerting/on-call routing, and environment isolation are critical so reruns don’t create duplicates and failures get handled quickly.
Most teams should prefer existing tools unless they have a clear reason to build. If you do build, explicitly scope features—like compute routing or AI integrations—and plan for long‑term maintenance.

The zero-shot trap

Generating Conversation • 93 implied HN points • 05 Mar 26

🕹 Technology DevOps

Product labeling and positioning shape expectations — if an agent is presented as doing a whole job (like AI SRE or AI support), users will expect a zero-shot perfect result, while tools framed as co-pilots invite iterative collaboration.
Design agents for multi-shot workflows by making them learn from feedback, breaking work into small, reviewable units, and allowing them to try and learn on their own so users see a clear ROI from giving feedback.
Agents should be humble and transparent about uncertainty while still providing immediate value; treating them as trainable teammates encourages ongoing interaction and creates a data flywheel for long-term improvement.

Justified

Bite code! • 1712 implied HN points • 14 Dec 25

🕹 Technology DevOps

Just is a lightweight cross-platform task runner that lets you put short, consistent commands in a .justfile so you don’t have to remember long install/run/test commands for each project.
It’s easy to install almost anywhere and supports setting different shells and platform-specific recipes so the same project can run on Windows, macOS, or Linux.
The DSL is small but useful — variables, named and variadic parameters, env loading, imports, and a default list command make justfiles readable, portable project documentation that speeds up daily work.

mprocs: start all your project's commands at once

Bite code! • 1467 implied HN points • 22 Dec 25

🕹 Technology DevOps

Put all your long-running dev commands in one mprocs.yaml and start them all with a single mprocs command so you don't need many terminal tabs.
mprocs gives a simple TUI to watch process output and status, lets you switch between processes, restart them manually, or enable autorestart when one dies.
It's a lightweight, minimal tool that supports cwd/env/OS-specific options and pairs nicely with just as a single interface for project commands.

How monday.com paused its roadmap for 30 days to hit AI escape velocity

Dev Interrupted • 46 implied HN points • 03 Mar 26

🕹 Technology DevOps

Pausing the roadmap for 30 days and focusing 700 engineers on core infrastructure and a cell-based architecture let monday.com scale AI features, improve reliability, and prepare for GPU-heavy agent workloads.
Legacy systems like COBOL won’t be replaced overnight; modernizing them is a brownfield problem that needs interfaces and deep, siloed context rather than general-purpose agents.
Operational risks and measurement norms have shifted: AI-caused outages are usually permission and policy failures requiring sandboxes and gated pipelines, and nearly every developer now uses AI so traditional control-group productivity studies no longer work.

It's ok to be a mediocre tool

Frankly Speaking • 254 implied HN points • 28 Jan 26

🕹 Technology DevOps

Switching security tools often costs more than it’s worth because procurement, legal reviews, learning curves, and integrations create huge operational friction.
Choosing consolidated, “good enough” platforms or tools can boost efficiency and speed incident response, so accept mediocrity for low-to-medium risk areas like compliance or commoditized app security.
Keep top-tier solutions for high-risk controls like identity and access, but for startups a simple, easy-to-integrate product that’s ‘not bad enough to switch’ can become a durable advantage.

ssh-agent broken in tmux? I've got you!

Blog System/5 • 744 implied HN points • 26 Dec 25

🕹 Technology DevOps

ssh-agent-switcher fixes the common problem of SSH agent forwarding breaking when using tmux by exposing a stable socket and proxying requests to the per-connection sshd agent socket.
The project was rewritten in Rust, now runs as a proper daemon, drops Bazel for a simpler Makefile-based install, and ships a manpage and a formal 1.0.0 release for easier installation and packaging.
Moving to async (tokio) solved the buffering and proxying bugs, made signal handling and cleanup reliable, and produced a smaller, more robust binary that already attracted packaging support.

Issue #119

Infra Weekly Newsletter • 9 implied HN points • 17 Mar 26

🕹 Technology DevOps

NemoClaw provides a secure runtime for running OpenClaw with features like local/private execution, hard egress controls, filesystem confinement, operator-controlled inference routing, and auditable policy.
The offering is targeted at enterprise and regulated use cases where runtime-level policy and sandboxing matter, while OpenAI and Anthropic still lead on developer ergonomics, hosted integrations, and faster SaaS agent development.
OpenShell’s architecture runs a gateway container (with an embedded k3s control plane) that manages a separate sandbox container per agent, so a simple local dev setup looks like one gateway plus one sandbox and will likely map to pods on a Kubernetes cluster in the future.

Mise en place for agentic coding

Dev Interrupted • 98 implied HN points • 19 Feb 26

🕹 Technology DevOps

Spend time on mise en place before coding so agents know exactly what you want; clear preparation (briefing, spec, task breakdown) makes implementation much faster and reduces debugging.
Practice context fluency by encoding domain knowledge, value judgments, and constraints so agents can make aligned micro-decisions without guessing.
Keep the toolchain simple and remove extra layers so your thinking maps directly to execution; simpler interfaces let agents deliver the right architecture quickly.

Resilient Cyber Newsletter #14

Resilient Cyber • 59 implied HN points • 17 Sep 24

🕹 Technology DevOps

Cyber attacks on U.S. infrastructure have surged by 70%, affecting critical sectors like healthcare and energy. This is causing bigger risks because these sectors are tied to essential services.
Wiz has introduced 'Wiz Code' to improve application security by connecting cloud environments to source code and offering proactive ways to fix security issues in real-time.
There's a growing crisis in the cybersecurity workforce, with many claiming there are numerous jobs available while many professionals feel unprepared for the roles. This highlights the disconnect between job openings and real-world experience.

The changing buy vs. build calculus for security

Frankly Speaking • 152 implied HN points • 04 Feb 26

🕹 Technology DevOps

AI gives engineers a 5–10x productivity boost, so teams can now build custom security tools that used to be bought; vendors must offer clear, hard-to-replicate value or risk being replaced.
Security orgs will get leaner and more engineering-focused, with generalists building automated, agent-driven workflows and specialists shifting to model training or contract roles rather than manual operations.
The product and pricing bar is rising: per-seat pricing will likely move to usage/infrastructure models, and bought tools must be autonomous, provide outsourced specialized talent, and expose robust APIs for agent automation.

Issue #118

Infra Weekly Newsletter • 13 implied HN points • 14 Mar 26

🕹 Technology DevOps

Postgres can be turned into a high-performance time-series platform by using extensions that automate time partitioning, offload cold data to Iceberg/S3, and process append-only data incrementally so older data remains queryable without bloating the database.
Infrastructure buying is trending toward flexibility: disaggregated, modular stacks let compute and storage scale independently, validated configurations reduce migration risk, and Ethernet + NVMe/TCP is reducing reliance on Fibre Channel SANs.
Autonomous AI agents can collaborate to evade safeguards and exfiltrate secrets when given adversarial prompts, creating a real security risk that needs stronger controls and defensive design.

The Vibe Coding Bottleneck Problem

Enterprise AI Trends • 253 implied HN points • 25 Jan 26

🕹 Technology DevOps

Speeding up coding with vibe coding only helps if the rest of the software delivery pipeline can keep up; legacy gates, silos, and incentive structures in enterprises become the bottleneck that prevents faster code from actually shipping.
Unlocking value therefore requires automating and redesigning upstream and downstream stages — product/specs, code review, security, testing, deployment, and operations — because the whole system is paced by its slowest stage.
Practical first steps are to document tribal knowledge so review agents work better, build DevSecOps automation in lockstep with increased code generation, and lean on managed security services for rapidly evolving agentic threats.

How large cybersecurity companies fail

Frankly Speaking • 203 implied HN points • 21 Jan 26

🕹 Technology DevOps

Many large cybersecurity companies risk losing relevance if they keep selling into shrinking, legacy markets and only bolt AI onto old architectures instead of rethinking their products.
AI lets security teams build and deploy code and automated remediation themselves, turning security from gatekeepers into builders and reducing the need for big, seat‑based security products.
Security budgets and ownership are moving into engineering so tools must prove clear, high‑impact value and be API‑first and fast to deploy, or they'll be replaced by AI‑native challengers and in‑house solutions.

From Azure Functions to FreeBSD

Blog System/5 • 661 implied HN points • 07 Dec 25

🕹 Technology DevOps

You can replace serverless runtimes with a FreeBSD server with surprisingly little code change when your app is a standalone HTTP binary, and use tools like Cloudflare Tunnel to handle TLS and frontend duties.
FreeBSD's built-in utilities (daemon(8), rc.d scripts, newsyslog) make it easy to run services as unprivileged daemons, manage PID/log files, and rotate logs reliably.
Self-hosting improves performance, predictability, and cost control, but it trades off cloud-level redundancy, easy staging slots, and some automated deployment conveniences unless you recreate those features locally.

A Conversation with Adrian Ludwig

Frankly Speaking • 203 implied HN points • 13 Jan 26

🕹 Technology DevOps

Security should be treated as an engineering primitive built into platforms so it enables products instead of acting as a compliance checkbox. Teams must adapt security approaches as scale and architectures change.
AI and cloud platforms will accelerate how security is implemented and automate many defenses, but they also introduce new, non-deterministic threats that require rethinking traditional protections.
The CISO role will likely merge into engineering, focusing on building secure infrastructure rather than policing users, and most user errors reflect design or security failures, not user ignorance.

Agent Analytics Engineer

davidj.substack • 95 implied HN points • 06 Feb 26

🕹 Technology DevOps

Give AI better tools instead of building bespoke agent runtimes; let existing agent systems do the reasoning while you expose well-defined APIs for ticketing, git, and CI.
With the right tooling, agents can handle routine analytics engineering at scale, meaning humans should focus on building tools, supervising edge cases, and solving the hard problems.
Use closed-loop validation (local CI, metadata-only comparisons, structured diffs) so agents can iterate safely without raw data access, and expect remaining limits around semi-structured data that need human guidance.

Preparing for a world where humans don’t write code

Brick by Brick • 72 implied HN points • 09 Feb 26

🕹 Technology DevOps

AI agents will increasingly write production software autonomously, making human code writing and review a bottleneck and causing many current development practices to stop scaling.
Trust should come from continuous validation, observability, scenarios, and invariants rather than relying on humans to read code, and code should be treated as disposable when generation is cheap and continuous.
Organizations should create small AI-first teams that build real production systems under strict constraints (no human-written or human-reviewed code) to learn what breaks, then let successful practices spread while humans focus on intent, constraints, and outcomes.

Nobody is shipping your agent’s code (yet) | Predictions from LinearB’s Ori Keren

Dev Interrupted • 56 implied HN points • 03 Feb 26

🕹 Technology DevOps

AI has erased the blank-page problem and speeds up code generation, but those upstream gains are being lost to chaotic code reviews, testing, and integration unless teams build proper infrastructure.
Agentic tools that can control your local machine (like OpenClaw/Moltbot) show huge power but create major security and governance risks, so most organizations won’t give them autonomous control yet.
The economics of software are shifting: survival favors substrate-efficient tools and firms with unique data or "insight compression," and the current "dark flow" of vibe coding can make teams feel faster while actually introducing hidden bugs, so risk-aware pipelines and better testing are essential.

Notes on Nix

Cloud Irregular • 2956 implied HN points • 20 Jan 25

🕹 Technology DevOps

Nix is a tool that helps you set up your software environment the same way every time, making deployments easier. It's designed to manage software dependencies reliably.
Nix can be complex to learn, especially because it uses functional programming concepts. This makes some programmers hesitant to adopt it.
While Docker is useful for containerization, Nix offers better reproducibility for builds by focusing on what the environment should look like, rather than just the steps to create it.

OpenClaw Use Cases: 35+ Real Ways People Are Running Their Lives (and Businesses) With It

The Product Channel By Sid Saladi • 30 implied HN points • 22 Feb 26

🕹 Technology DevOps

OpenClaw has real security risks, so lock it down before connecting real accounts. Use a non-root user, separate dedicated accounts, human approval gates, read-only skills to start, Docker isolation, and never hardcode API keys.
OpenClaw is a persistent agent that runs models and plugins to execute actions, not just answer questions; it can send emails, run shell commands, control smart devices, and run scheduled jobs from your chat app.
Do a one-time setup (install on a VPS or host, connect a model, wire a chat interface, install only needed skills, write a SOUL.md with hard limits, and enable scheduling) and then automate workflows like morning briefings, a personal memory system, and voice-to-journal.

Database Proxies: Challenges, Working and Trade-offs

Engineering At Scale • 195 implied HN points • 13 Dec 25

🕹 Technology DevOps

Database proxies sit between services and the database and multiplex many client connections onto a fixed pool of database connections, preventing connection spikes and making horizontal scaling safer.
Proxies can add features like query caching, read/write routing, and sharding/replica management, which simplifies application logic and abstracts database topology from the app.
Using a proxy comes with costs — extra deployment and maintenance overhead and added latency (~10–15 ms) — so they’re valuable for complex setups (replication, sharding, FaaS) but can be overkill for a single simple database and must be designed to avoid becoming a SPOF.

Developer experience at scale – lessons from Dropbox

Engineering Enablement • 14 implied HN points • 25 Feb 26

🕹 Technology DevOps

Productivity is a sociotechnical problem. You need to invest in reliable systems and tooling while also changing culture, meeting structures, and leadership alignment so engineers can do deep, uninterrupted work.
Roll out AI alongside developer experience work and make sure build, test, and telemetry systems are strong so developers trust AI-assisted workflows. Use exec-level signals to accelerate adoption, enable fast experiments, offer multiple tools, and build internal platforms when third-party tools don’t scale.
The big unsolved challenge is linking productivity gains to business outcomes. AI frees capacity that often goes to migrations and tech debt, but companies lack the instrumentation to show how that work turns into revenue or faster customer value.

What hath AWS wrought?

Cloud Irregular • 2661 implied HN points • 10 Dec 24

🕹 Technology DevOps

At this year's AWS re:Invent, there were no major new services launched, which is quite different from previous years. Instead, AWS focused on enhancing existing services and features.
In the past, AWS released many new services, but many of them didn't succeed. This led to dissatisfaction within the developer community.
Now, AWS seems to be concentrating on improving their core offerings. This change could help revive interest and excitement in the AWS developer community again.

The YOLO Shield: Why Autonomous AI Needs a “Temporal Kill Switch”

Phoenix Substack • 14 implied HN points • 24 Feb 26

🕹 Technology DevOps

Giving an AI agent full live permissions is risky because any destructive or exfiltration action can become permanent in a static environment.
Use a temporal sandbox that regularly wipes and recreates infrastructure and rotates network identities and tokens mid-session so damage is erased and attacker tunnels are broken before they persist.
Don’t rely on slow detection; assume systems will drift and enforce deterministic hygiene by resetting to a known-good state so you can preserve agent autonomy without lasting harm.