devwhateverops.com — Manifesto

Breaking things carefully is how you go faster!

A set of principles for engineers who build end to end — written as the AI hype begins to settle.

Own the full loop. No gates, no handoffs, no role hiding.

CULTURE

DevOps was never a role. It was a direction. Every “-Ops” suffix we invented since — SecOps, AIOps, DocOps, FinOps — was an attempt to name a culture shift. Most of the time it became a job title instead. A new silo built to solve the problem of silos.The baseline for any engineer is understanding the full system they work in. Not just the code they write — how it is tested, how it is deployed, how it behaves in production, and what happens when it breaks. Specialization on top of that foundation is a multiplier. Specialization instead of it is a liability.End-to-end ownership is not a senior bar. It is the entry bar. Hiring should reflect that. Can you write it, test it, pipeline it, deploy it, instrument it, and close the loop? That is the question.

Automate everything. Smooth is fast, fast is smooth.

PIPELINE

Automation is not about replacing people. It is about removing every ceiling on how fast and safely people can move. Every manual step in a pipeline is a speed limit. Every approval gate that exists because nobody automated the check is a tax on momentum.Requirements, specifications, and architectural decisions — RFCs, PRDs, ADRs — are not side artifacts. They are first-class inputs. Code, tests, and pipeline stages should be able to reference them, trace back to them, and validate against them. The loop from specification to deployment to observation should be closed, not scattered across tools and folders nobody reads.Ops must be invisible. Not because it doesn’t matter — because it matters so much it cannot depend on human intervention. Smooth is fast. Fast is smooth.

Every change is a hypothesis. Ship small, observe, decide.

EXPERIMENTS

It is okay to break things. That is why we have controlled rollouts.The fastest engineering teams break things more often than slow ones — not because they are reckless, but because they built systems where breaking things is safe, observable, and cheap. Fear of breaking things is the real bottleneck. A/B testing and gradual rollouts are not just risk management tools. They are permission structures. They change what “safe to ship” means.An experiment is an experiment regardless of what you are changing. A new UI button observed against click behaviour. A copy change measured against conversion. An AI model swap validated against a baseline dataset. A feature rolled to five percent of traffic. The discipline is identical — hypothesis, controlled change, observation, decision. The tooling varies. The culture does not.Evaluation, dataset versioning, experiment tracking, and baseline comparisons are not exotic ML infrastructure. They are what CI/CD looks like when your system has a probabilistic component. AIOps is a variation on the theme, not a separate practice. Old quality is still there. AI eval is the new layer on top.

WHY MOST COMPANIES ARE NOT HERE YET

COST OF FRAGMENTATION

The cost of fragmentation is invisible. Nobody budgets for the deployment that required three teams and a ticket. Nobody measures the speed lost to a gate that exists because the test was never automated. The real cost of the current way of working is consistently underestimated — which means the investment required to change it is consistently underfunded.Beyond cost: most organisations have people with rational reasons to resist this direction. Specialists who built careers inside a narrow lane. Managers who built teams around a function. Change that threatens identity moves slowly. And automation costs now but pays later — which is the wrong shape for most quarterly plans.

The principles don’t change. The articles will.

FROM HERE

This is not a new movement. It is the original one, still completing itself.The principles here will not age. The specific articles, tools, and examples that follow on this site will — and that is the point. This page is the anchor. Everything else is the elaboration.If you build end to end, you are already here. If you are trying to get there, you are in the right place.

More specific, hands-on writing coming. Follow along.

On the leadership side of this: humancopilot.eu

Hands-on articles on Medium