Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on Goodbye, Clean Code. Parent comment
Unless you are sure you will need to separately evolve the initially duplicated cases, assume YAGNI: You're Not Gonna Need It (the repetitions).
Avoid repetition like the plague; when the new requirements arise that conflict with the reduced repetition, confront it at that time.
It's possible they they are bad requirements, in which case the clean, DRY code can support arguments against the requirements.
Treat the computer as more of an Analytical Engine, and less of a Jacquard Loom.
The special case behaviors for various shapes hinted at in the article:
> For example, we later needed many special cases and behaviors for different handles on different shapes.
This sounds like it might be a bad experience for the end user who has to learn annoying shape-specific handle quirks.
There are no comments on this comment yet.
Unless you are sure you will need to separately evolve the initially duplicated cases, assume YAGNI: You're Not Gonna Need It (the repetitions).
Avoid repetition like the plague; when the new requirements arise that conflict with the reduced repetition, confront it at that time.
It's possible they they are bad requirements, in which case the clean, DRY code can support arguments against the requirements.
Treat the computer as more of an Analytical Engine, and less of a Jacquard Loom.
The special case behaviors for various shapes hinted at in the article:
> For example, we later needed many special cases and behaviors for different handles on different shapes.
This sounds like it might be a bad experience for the end user who has to learn annoying shape-specific handle quirks.