Sokkel. Close

DevOps playing cards based on assumptions and stuff found online. Have fun

Hello! I’m Otto the DevOps Octopus. I mentioned DevOps in one meeting—now it’s my responsibility.

Source: Martin ↗

You configured Kubernetes for 20,004 minutes this year

Source: LinkedIn ↗

Writing a good commit message is like documenting your crimes.

Microservices: Turning a monolith into a thousand-piece jigsaw puzzle.

Source: A linkedIn post

DevOps is just developers who were tricked into doing Ops.

Source: A colleague (Dev)

Did you know that 90% of DevOps Engineers Prefer Dark Mode?

Source: ChatGPT

Team GCP, Team Azure or Team AWS, your choice!!

Source: Just curious

I find that the most important button is always the smallest and hardest to find in DevOps tools.

Source: Marius ↗

Ready or not, here I come, you can't hide → An accidental $50,252 AWS bill.

Source: Ready or Not by Fugees ↗

We have logs, metrics, and traces. No idea what’s wrong, but we have data.

Source: Simen ↗

Best practices are just things someone got away with once.

Source: Bob

Your infrastructure decisions are like legacy orchestration platforms - they made sense when you started, but now they're just slowing you down

Source: LinkedIn ↗

Your infra docs are like a quantum particle — everywhere in theory, but never when you need them.

Source: LinkedIn ↗

Everyday needs to be a Vegas blackout day

Source: Turso ↗

My infrastructure is in perfect shape. It’s just undocumented, fragile, and nobody understands it.

Source: Dev at a party

Your scaling strategy is like a private equity playbook - full of good intentions that create bottlenecks instead of breakthroughs

Source: LinkedIn ↗

Your infrastructure migrations are like Azure’s payment portal – meant to be simple, but ended up needing three people and a full platform change.

Source: LinkedIn ↗