Start with the assumption that whatever the code is doing, it’s intentional. Then figure out what it does. Then comes the fun part, figuring out why.
This is in contrast to the usual approach of deciding what you think the code should do, then inspecting it and determining that it must be wrong.
[Comment removed by author]
Start with the assumption that whatever the code is doing, it’s intentional. Then figure out what it does. Then comes the fun part, figuring out why.
This is in contrast to the usual approach of deciding what you think the code should do, then inspecting it and determining that it must be wrong.
Great post. Brings back a lot of the memories I have from the banking industry :)