PirOps: What 18th-Century Piracy can Teach Us about SecOps
summary
Links 18th‑century Caribbean pirate practice to concrete SecOps/SRE tactics: pirates create Articles (ship constitution) that predefine pay, injury compensation and shared fate; they maintain an overabundance of crew and redundancy with short shifts to reduce toil; leadership is temporary and functional via an incident commander role rather than status; manual ops are treated as defects — manual ops as bugs — so teams prioritize automation and project work. Empirical note: pirates thrive ~35 years until naval patrols jump from 2 to 24 ships (1690→1725).
AI-written summary · about
chapters (4)
- 0:00The pirate organization
- 8:43Culture and performance
- 11:35Toil, leadership, and scale
- 24:05Concluding thoughts
related talks
34mDevSecOps: How to Use DevOps to Make You More Secure
29mThe SecDevOpronomicon
49mLessons from DevSecOps Trenches
57mBuilding a Modern Security Engineering Organization
27mDevSecOps: How to Use DevOps to Make You More Secure
49mStories from the SOC Front Lines
35mResponding to Supply Chain Vulnerabilities – A Maritime Perspective
33mDevSecOps: How to Use DevOps to Make You More Secure