Sign the DevOps Manifesto ✍️

[francescobianco]

Thank you for your interest in the DevOps Manifesto.

This manifesto redefines DevOps as a software engineering discipline, not as cloud system administration.
It focuses on engineering practices that improve developer experience, automation, project structure, and software evolution, rather than just managing production environments.

By leaving a comment on this issue, you are:

✔️ Signing the Manifesto

Your comment counts as your official endorsement of the DevOps Manifesto.

✔️ Sharing your ideas

You’re invited (but not required) to include:

• What DevOps means to you
• Why you support this vision
• Ideas or principles you think should be part of the discipline
• Stories from real projects that reflect this approach

✔️ Joining the conversation

This issue acts as the public ledger of signatories.
Every comment is a voice contributing to a healthier, engineering-first understanding of DevOps.

---

How to sign

1. Scroll down to the comments section
2. Add a new comment stating that you support the manifesto
3. (Optional) Share your thoughts, suggestions, or personal experience

That's it. Your comment = your signature.

---

Why this matters

Too often, “DevOps” gets misused to describe:

• cloud system administrators
• tooling operators
• ops-only practitioners

This manifesto brings DevOps back to its core:
engineering, automation, reproducibility, software structure, and developer experience.

Thank you for being part of this movement.
Your contribution strengthens a community that believes DevOps is fundamentally about building better software.

[masenocturnal]

I support this manifesto.

[suxstellino]

I support this manifesto.
Thanks!

What DevOps means to me

For me, DevOps is a practical mindset: a way to turn people, processes, and tools into a coherent flow of value. It’s not about chasing tooling trends, it’s about building shared responsibility, transparency, and a culture where improvement is continuous and natural.

Why I support this vision

I’ve seen what happens when DevOps is missing: silos, chaos, and slow delivery.
And I’ve lived the opposite. As our company grew, we avoided the typical “reorg” and instead invested in culture, trust, lightweight structures, and lean processes. DevOps made our teams more resilient, more aligned, and more autonomous.

Principles I believe should define the discipline

• Culture first, tools second (mindset)
• Adaptive documentation as a living asset
• Shared ownership, no gatekeepers, no blame
• Flat, transparent collaboration, no micromanagement.
• Continuous learning and onboarding, mentoring, and context for every new team member.
• Feedback (as soon as possible) everywhere, inspect, adapt, improve
• Sustainable pace, quality and people first.

Real stories that reflect this approach

Read more on my blog

I’ve helped build processes and a company culture where onboarding, documentation, and technical practices evolve continuously. When our team expanded quickly, we stabilized not by adding hierarchy but by simplifying workflows, reducing handoffs, and improving visibility.

We applied DevOps principles to everything: from workstations to project and company workflows. The result was an organization that scaled without losing cohesion. This is the proof that DevOps is about people and shared responsibility.

[fabiocozzolino]

I support this manifesto!

Thanks you for this initiative!

[osevan]

I don't support this manifesto .

Devops have no idea about infrastructure and long-time kernel workers have to clean up the work afterwards and fix it.

Because they simply lack the experience in which situations a future software can stumble into userspace.

Security , read paths, write paths, ram usage and oom killing.

Does the software collide with Linux kernel and its page cache or are there more efficient kernel functions that could have been used?

A true server engineer, benchmarks his software and sees if the code changes have actually improved or worsened.

From my subjective point of view, - with 22 years of Linux kernel experience - I can write that devops is an industry-created discipline to save costs on skilled personnel, but to drive up infrastructure costs

The winners are of course the big cloud providers :aws, google cloude und Azure cloud .

And it's no longer a secret that a capable engineer can handle the infrastructure and database and latency and throughput, better than the big 3.