DevOps Manifesto — Engineering, not Operations

2 min read Original article ↗

A manifesto for those who build software

For those who design, structure, and evolve software ecosystems—not just production environments.

DevOps is not a job title.
DevOps is not a rebranded sysadmin.
DevOps is not "the person who runs the pipeline" or "knows Kubernetes commands".

DevOps is software engineering applied to the entire product lifecycle.

Core Values

Software Engineering

OVER

Cloud console management

Development Environments

OVER

Production environments only

Developer Experience

OVER

Cloud provisioning

Structures & Standards

OVER

YAML and configurations

The Five Principles

I

Engineer for Containerization

Not "slap Docker on it", but design software that can be containerized. Software with clear boundaries, external configurations, deterministic builds.

  • Clear boundaries
  • External configs
  • Deterministic builds
  • Managed dependencies
  • Reproducible artifacts
  • Minimal runtime
II

Engineer Pipelines & Automation

The pipeline is not a YAML file: it's the product. It must be fast, parallelizable, self-validating, capable of spinning up and tearing down environments.

  • Speed
  • Parallelism
  • Self-validation
  • Infra as Code
  • Part of architecture
III

Engineer Project Structure

DevOps is architecture. Shared standards, conventions, reusable scaffolding, tools that prevent human error, bootstraps that start "right-first-time".

  • Shared standards
  • Clear conventions
  • Reusable scaffolding
  • Error prevention
  • Project bootstraps
IV

Transform & Modernize Legacy

The ability to take software written twenty years ago and bring it to the present: modularization, containerization, tests where none existed, functional boundaries.

  • Modularization
  • Legacy containerization
  • Test introduction
  • Functional boundaries
  • Verifiable standards
V

DevOps as a DevEx Discipline

DevOps is the science of developer environments. Goal: make development faster, more reliable, and more enjoyable. Starting with developers' daily tools.

  • Fast feedback loops
  • Reliable environments
  • Pleasant workflows
  • Daily tooling
  • Quality by construction

Anti-patterns to Eradicate

✗ The "cloud sysadmin" rebranded as DevOps

✗ "The one who knows how to deploy"

✗ Operations role managing servers

✗ Role created to fill organizational gaps

✗ Kubernetes-first, cloud-first, YAML-first

✗ Technocracy instead of methodology

The DevOps We Need Today

Build evolvable software Improve development environments Standardize and automate Measure what matters Make developers efficient

DevOps is not a department.
DevOps is an engineering discipline.

Sign the Manifesto

If you believe in this vision of DevOps—focused on engineering, automation, developer experience, and building better software—you can officially sign the manifesto.

Just leave a comment on the GitHub issue below.
Your comment counts as your signature, and you're welcome to share your ideas or perspective.

Sign the Manifesto on GitHub

github.com/alterloop/manifesto/issues/1