What DevOps Really Is (and Isn’t): History, Principles, Tools, and Culture

DevOps: What It Is and What It Is Not

Is DevOps a job title, a department, or a set of best‑practice principles like Agile and Lean? Recent job postings show a variety of titles—technical manager, architect, evangelist, development director, data scientist, and operations‑development engineer—yet the core classification still falls into two groups: development engineers and operations engineers, with many so‑called DevOps engineers leaning more toward operations.

Historically, as computing became more specialized, development and operations split into distinct roles and departments. Development focuses on rapid feature delivery, while operations prioritize system stability, reliability, and security, creating an inherent tension.

With the rise of cloud platforms, infrastructure became programmable and easier to provision, allowing developers to create servers, databases, and deploy applications directly (e.g., AWS tools and APIs).

Agile’s emphasis on fast iteration—design, develop, test, and release in short cycles—led to the need for tighter collaboration between developers and operators. In 2008, Patrick Debois presented “Agile Infrastructure & Operations” at the Agile 2008 conference in Toronto, planting the seed for DevOps. The following year, John Allspaw and Paul Hammond’s “10+ Deploys per Day” talk at O’Reilly Velocity 2009 demonstrated the practical benefits of DevOps thinking.

These events sparked the creation of DevOpsDays, first held in Ghent, Belgium, in October 2009, and helped popularize the term.

What DevOps Is Not

DevOps is not a specific job title, a dedicated department, or a guarantee that development and operations report to the same manager. It is a cultural mindset that encourages collaboration, shared goals, and mutual respect.

According to Wikipedia, DevOps emphasizes cooperation between developers and IT operations to automate software delivery and infrastructure changes, enabling fast, frequent, and reliable releases.

In practice, DevOps can be seen as a combination of tools and culture.

Toolchain

Typical DevOps tooling includes:

Code management: editors, code review tools, version control systems.

Packaging and build: npm, Maven, Docker, Jenkins.

CI/CD: Drone.io, Wercker, Travis CI, CircleCI, Codeship.

Configuration management / Infrastructure as Code: Ansible, Chef, Puppet.

Monitoring: ELK stack, InfluxDB, Grafana, Graphite.

Release systems: Codeship, Jenkins.

ChatOps: Slack, HipChat, BearyChat.

Additional capabilities such as canary releases, A/B testing, and rolling updates are also common.

Cloud providers (e.g., AWS) and container platforms (e.g., Docker Cloud, Lingque Cloud) offer integrated services that embody DevOps principles.

Organizational Culture

DevOps promotes values like respect, trust, a healthy attitude toward failure, and avoiding blame. These cultural pillars, first highlighted by Flickr engineers in 2009, are essential for successful adoption.

Beyond tools and culture, DevOps involves people’s mindset, processes, lean thinking, automation, measurement (e.g., Metrics‑Driven Development), sharing, communication, and iterative improvement cycles such as PDCA/OODA.

Empathy—understanding and considering the perspectives of others—is highlighted as a critical soft skill for bridging the gap between developers and operators.

Beyond Dev and Ops

While the name combines Development and Operations, DevOps also encompasses IT (infrastructure, networking), project and product management, and even functions like sales, marketing, HR, and finance, requiring cross‑functional collaboration.

Recruitment Note

The author mentions Lingque Cloud, a DevOps‑oriented container cloud platform supporting Mesos, Kubernetes, and Swarm, and invites interested developers to apply, emphasizing a flexible hiring approach that values personal fit over formal credentials.