Code Is Crap

2026-09-16 | original

read original get Clean Code by Robert C. Martin → more articles

Why This Matters

This piece uses a provocative title to make a broader point about the state of software quality, resonating with developers and companies grappling with technical debt and maintainability issues. The lighthearted framing (with a mnemonic like 'CRAP') suggests the article is offering a practical or humorous lens on assessing code quality, which matters to engineering teams making decisions about legacy systems and development practices.

Key Takeaways

The article appears to use 'CRAP' as an acronym or mnemonic device related to evaluating code quality.
It includes a historical perspective on the concept, suggesting it has been used or discussed before in tech circles.
The piece is framed with a playful, informal tone, using mild language to make a point about code quality memorable.

Worth a Look

Clean Code by Robert C. Martin — If you're pondering how much code out there is truly 'crap,' this book is the classic guide to writing maintainable, readable software. It's a great practical companion for developers wanting to apply real craftsmanship principles to their own projects.

See Clean Code by Robert C. Martin on Amazon → Affiliate link — we may earn a commission on purchases, at no extra cost to you. Product picked by AI based on this article; it is not a tested recommendation.

Note: This post is rated PG-13 for use of a mild expletive. If you are likely to be offended by the repeated use a word commonly heard in elementary school playgrounds, please don’t read any further.

A Brief History of CRAP

Use CRAP On Your Project

vintage

Explore topics: code quality software development crap principle elementary programming concepts project management