Skip to content

Instantly share code, notes, and snippets.

@andir

andir/sm.md

Last active February 18, 2026 20:13
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save andir/4176035d579913326eab56e013dbe97f to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save andir/4176035d579913326eab56e013dbe97f to your computer and use it in GitHub Desktop.
Download ZIP
Raw
sm.md

🧾 The Simple Sabotage Guide for Cloud-Native Organizations

(A Satirical Field Manual for Maximum Bureaucratic Drag)

General Principles

  1. Prefer Meetings Over Progress When a decision can be made in Slack, schedule a 60-minute Zoom. When a 60-minute Zoom will suffice, create a recurring weekly sync. Always conclude with: “Let’s take this offline.”

  2. Elevate Process Above Outcome If something works, insist it violates the “approved architecture vision.” If it doesn’t work, propose forming a governance committee.

  3. Revere Documentation, Avoid Clarity Write extensive documentation in Confluence. Ensure it is:

    • Slightly outdated
    • Full of acronyms
    • Missing the one step that actually matters

Cloud Architecture Sabotage

  1. Microservices for Everything Even a “Hello World” app deserves 14 services, 3 queues, and a service mesh. Bonus points if no one understands the network topology.

  2. Environment Multiplication Strategy Maintain:

    • Dev
    • Dev2
    • Dev3
    • QA
    • QA2
    • Pre-Prod
    • Pre-Pre-Prod
    • Final-Pre-Prod-v2

    Ensure none match production.

  3. Credential Chaos Rotate secrets frequently. Never tell anyone where they’re stored. If using a vault, ensure only one engineer understands it—and they are on vacation.

DevOps Optimization (for Minimal Velocity)

  1. CI/CD Pipeline Expansion If a build takes 5 minutes, improve it to 45. Add:

    • 3 security scanners
    • 2 linters that disagree
    • 1 mysterious failing integration test

  2. Rename the Main Branch Quarterly master → main → trunk → primary → main-final

  3. Deploy on Fridays at 4:59 PM Announce confidently: “It’s a small change.”

Kubernetes Enhancement Protocol

  1. Use Kubernetes for projects that could run on a Raspberry Pi.
  2. Tune resource limits randomly.
  3. When pods crash, say: “It’s probably DNS.”

Communication Best Practices

  1. Use Slack for urgent matters. Mute all notifications.

  2. When tagged directly, respond with:

    “Can you create a ticket?”

  3. Create duplicate tickets in:

    • Jira
    • Azure DevOps
    • A personal Notion board

Leadership Guidance

  1. Announce a “cloud cost optimization initiative.” Simultaneously approve three new AI pilot projects.

  2. Adopt every new buzzword:

    • Serverless-first
    • Platform engineering
    • DevSecFinAIOps

  3. Reorganize teams during critical product launches.

Advanced Techniques

  • Introduce a breaking API change labeled as a “minor refactor.”
  • Begin migration to a new cloud provider before finishing the previous one.
  • Declare: “We’ll fix it in the next sprint.”

Closing Directive

If all else fails, start a discussion about:

  • Tabs vs spaces
  • Which IaC tool is “the future”
  • Whether Kubernetes is overkill

With discipline and consistency, productivity may be reduced by up to 73%, while morale decreases in direct proportion to the number of dashboards created.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment