The article advocates for a proactive approach towards dealing with messy code. Rather than succumbing to frustration, one should recognize that this 'Big Pile of Mud' sustains the company. It emphasizes stopping further deterioration of the code and instead encourages gradual improvement, inspired by the Boy Scout rule, which suggests leaving the code in a better state than found. Simple acts like formatting and renaming variables enhance readability and maintainability, ultimately contributing to a more efficient and organized development process.
"Instead of giving in to the anger and blame, it's important to realize that this Big Pile of Mud works and puts food on the table for you and everyone in your company. Sure, it's a mess, but it pays the bills."
"Job one is not to make things any worse than they already are. Don't add another layer of depth to that huge, nested if statement. Don't add 120 more lines of code to that God class."
Collection
[
|
...
]