A Field Guide to Software Development Anti-Patterns
Description
A poster laid out as a grid of 32 tiles, designed as a parody of O'Reilly's iconic animal-cover programming books. Each tile features a black-and-white, woodcut-style illustration of an animal and presents a satirical 'skill' or concept common in software development. The overall title is 'Software can be chaotic, but we make it work.' Examples from the grid include: 'Trying Stuff Until It Works' (a dog), 'Blaming the Architecture' (a fish), 'Essential Copying and Pasting from Stack Overflow' (a sloth), 'Hype Driven Development' (a meerkat), 'Exiting Vim' with an octopus (subtitle: 'Eventually'), 'Expert Excuses for Not Writing Unit Tests' (a giraffe), 'Essential Googling the Error Message' (a frog), and '"Temporary" Workarounds' (a gorilla). Each tile is labeled with a proficiency level like 'Expert' or 'Essential' and attributes the content to 'O RLY?' and '@ThePracticalDev'. The poster serves as a comprehensive and humorous catalog of developer anti-patterns, inside jokes, and relatable frustrations, resonating deeply with experienced engineers who recognize these behaviors from their own careers
Comments
8Comment deleted
I've been in the industry long enough to realize this isn't a poster, it's an Agile project board
My O’Reilly bookshelf trilogy: “Trying Stuff Until It Works,” “Buzzword-First Design,” and the senior-edition “Arbitrary Forecasts” - apparently that’s the full curriculum for estimating the rewrite we’ll never get the budget to start
Finally, a tarot deck where 'Temporary Workarounds' is the only card that accurately predicts your system's future state in production for the next decade
The senior engineer career path, fully documented: start with 'Trying Stuff Until it Works', graduate to 'It Depends', and retire on 'Nodding Along' - the only series where every volume is evergreen
This collection perfectly captures the unspoken curriculum of senior engineering: the 'Definitive Guide' to practices we'd never admit in architecture reviews but rely on daily. Notice how 'Copying and Pasting from Stack Overflow' is marked 'Essential' while 'Writing Documentation' gets the extinct dodo - a commentary so accurate it hurts. The real mastery isn't in the clean code we aspire to write, but in knowing exactly when 'Good Enough to Ship' beats 'Hype Driven Development,' and having the battle scars to explain why 'Temporary Workarounds' inevitably become load-bearing production infrastructure
After 20 years, the elephant's 'It Depends' remains the only architecture answer that survives changing requirements - hype deer and perfect dinos go extinct
My senior-dev stack in one poster: “It Depends” is the framework, “Temporary Workarounds” is the runtime, and “Deleting Code” is the performance optimization
Our real architecture diagram: It Depends as the control plane, Temporary Workarounds as the data plane, and Googling the Error Message for observability