Philosophy
A Principle is just in Principle
A principle is just that - a principle. It can nudge you towards the correct direction. But it may or may not apply to your situation. Only you have the actual and close understanding of your situation and what's going on
Bad code can lead to good code
Bad code can sometime be used in certain scenarios. You can avoid principles just because #A Principle is just in Principle.
It stays in your code as a marker for you to remind you to change it later. Will it be changed ever? Only time can tell. So bad code also might live a good life - as long as it works.
Its a code smell and that's good because it keeps you looking for abstraction that you have missed. But meanwhile, you can still provide value to your stakeholder.
I imagine rules like this one defining a landscape, where maintainable code lives in the valleys. As you add new behavior, it's like rain landing on your code. Initially you put it wherever it lands.. then you refactor to allow the forces of good design to push the behaviour around until it all ends up in the valleys. Philosophy#^c4d62c
Bad guideline is still better than no guideline
From #^f452b2.
Bad guidelines still ensure uniformity across application which otherwise would be missing. If it is followed religiously, then it makes the code more understandable as well.
