Abstract

The DevOps movement is conventionally dated to Patrick Debois's "Agile Infrastructure" talk in 2008 and the subsequent Velocity conference sessions by John Allspaw and Paul Hammond. The term itself was coined in 2009. What is less documented is the parallel and prior practitioner work happening outside the conference circuit — work that sometimes collided with corporate IP interests in ways that are instructive for understanding how the industry absorbs and brands practitioner knowledge.

This is one such account.

1. Context: CompuTEK Industries, 2007

In 2007 I was operating CompuTEK Industries, a managed services provider doing what would later be called DevOps work: integrating development and operations workflows, automating deployment pipelines, treating infrastructure as code, and applying feedback loops from production systems to development velocity. We didn't have a name for it. We called it "Developer Operations" in internal documentation and client proposals.

I was presenting these concepts at local technical meetups and user groups in Colorado Springs — DFW came later. The Agile Manifesto had been signed in 2001 — I was a signatory, under CompuTEK Industries, in May 2009. The practices we were developing were extensions of Agile principles into the operational domain, years before the Agile Infrastructure framing became mainstream.

2. The IBM IP Dispute

In 2007–2008, CompuTEK's client work brought us into contact with IBM enterprise accounts. IBM at the time was aggressively asserting IP claims over methodologies and practices in the systems integration space. The specific claim was around documentation and training materials CompuTEK had developed for clients — materials that IBM asserted bore sufficient similarity to IBM-internal methodology documentation to constitute derivative works or trade secret disclosure.

The claim was, in my assessment, without merit. The practices documented were practitioner-developed and predated the IBM internal materials we were alleged to have derived from. The problem was: proving prior art in a methodology dispute against a company with unlimited legal resources is not a problem that a small MSP survives intact, regardless of who is right.

The practical resolution: CompuTEK Industries rebranded. Da Planet Security was established as the successor entity. The client relationships transferred. The methodology documentation was rewritten from scratch with explicit provenance tracking. The dispute was settled without admission.

3. What This Tells Us About Practitioner Knowledge

3.1 Naming as capture

The DevOps name was coined by practitioners. Within five years, every major enterprise software vendor had a "DevOps" product suite, a "DevOps" certification program, and a "DevOps" consulting practice. The practitioner community that developed the underlying concepts received attribution in conference keynotes and essentially nothing else.

This is a repeating pattern. Agile. Cloud Native. Platform Engineering. The name is coined by practitioners solving real problems. The name is adopted by vendors selling solutions to the problem the practitioners already solved. The vendors' version of the concept is then taught back to practitioners as the authoritative definition.

3.2 IP law as practitioner suppression

The IBM dispute was not unique. The use of IP law — patent, trade secret, and copyright — to suppress practitioner methodology development and sharing is a structural feature of the enterprise software industry, not an edge case. The asymmetry is total: a large corporation can sustain a meritless IP claim for longer than a small firm can sustain the legal defense.

The practical implication for practitioners: document everything, date everything, publish early. Public disclosure is prior art. A dated blog post, a conference presentation, an open source commit — these are not just professional development, they are IP protection for practitioner communities.

3.3 The Agile Manifesto as prior art infrastructure

The Agile Manifesto's public, dated, signed record is a model for how practitioner communities can establish collective prior art against corporate appropriation. It is not coincidental that the manifesto's signatories were protected from the worst of the methodology IP disputes that followed — the public record was too clear.

The DevOps community never developed an equivalent. The result is that "DevOps" now means whatever a vendor needs it to mean for their sales cycle.

4. Where This Leaves Us

I present this history not as grievance but as institutional knowledge. The pattern will repeat. It is repeating now with AI/ML practices, with platform engineering, with whatever the next practitioner innovation is that gets branded and sold back to the community that developed it.

The countermeasures are the same ones they have always been: publish, date, attribute, and maintain the community structures — 2600, HPR, aNONradio, local meetups — that keep practitioner knowledge in practitioner hands rather than in vendor marketing decks.

Da Planet Security was founded in 2001. The rebrand from CompuTEK happened under duress. The technical work continued. The clients transferred. The methodology survived, undocumented in corporate systems and very much alive in production infrastructure.

That is, in the end, what matters.

IANA PEN 42387 · ORCID 0009-0001-0066-4646 · Agile Manifesto signatory (CompuTEK Industries, May 2009)