|
|
|
|
|
|
by ConceptJunkie
2767 days ago
|
|
|
> My recommendation is not to try to understand the code per se, but understand the business that the code was being used in/by. You're absolutely right, but the problem comes when the code itself is the only authoritative documentation of what the code does, and in a lot of cases, the only authoritative documentation (or even the only documentation, period) of what the code is supposed to do! |
|
|