Software Anti-Patterns that Impact DevOps

Part Three in a Series on DevOps Anti-Patterns

I rarely test my code, but when I do, I test in production.
An oldie but goodie

You have layers of application code that developers are afraid to touch

You practice resume driven development

You don’t have adequate automated testing

Changes break downstream services

Disaster Girl: They told me to version my APIs, so I deployed a breaking change.
Disaster Girl: They told me to version my APIs, so I deployed a breaking change.

Your code short-cuts good implementation with Feature Envy

Your databases contain business logic

Cheezburger Cat: I’m in ur database, changing ur schema.
Cheezburger Cat: I’m in ur database, changing ur schema.

You have “pinned” library or language versions

You go through “integration hell” at the end of a sprint or release cycle

Epic parrot running from explosion
Epic parrot running from explosion
Honestly, I think this is one of the best pieces of the internet

You store passwords or run-time configuration in code

Next Up

Software and Technology Nerd, DevOps Ninja, Maker of Things, Aerospace Enthusiast. https://orc.works/