How to Write Unmaintainable Code (1999) (doc.ic.ac.uk)

The article is a satirical, intentionally harmful list of “techniques” for writing code that is hard to maintain, aiming to ensure future developers struggle to make even simple changes. It recommends behaviors like misleading or outdated comments, confusing naming and formatting, excessive nesting, and avoiding helpful documentation and modular structure. While presented as advice, it is clearly framed as a cautionary critique of practices that sabotage readability, correctness, and maintainability.