Completely different to the order I use, which basically amounts to "how hard is it to fix this later". So most important questions are: (1) API must be as cor

Completely different to the order I use, which basically amounts to "how hard is it to fix this later". So most important questions are: (1) API must be as correct as possible, especially if its exposed outside of the immediate team. Changing APIs is a royal pain. (2) Documentation of what's going on, especially for non-obvious stuff. If we come back to this in 3 years time and the author has moved on, do we have any hope of fixing it? (3) Testing. What degree of confidence do we have this is doing the right thing? Will it protect me when I change it in a few years time? Any minor bugs or code style issues can be fixed later as/when they are found and cause problems.