|
|
|
|
|
by PhineasRex
1465 days ago
|
|
This is a great example of why documentation is important though. If that comment had documented why 75 had been removed and what the impact of that was you would know how to address this situation. In fact, even the fact that the comment is now wrong tells you that the change was ill-considered and needs to be revisited. |
|
Any fix should produce at least a test to guard against regressions of the bug it's trying to fix and encode the correct business logic.
The test name would then explain the why. The test variables present the story of the what. And finally, the API calls tell the story of how how.