¶ Rusty Levels API design score

• http://www.pointy-stick.com/blog/2008/01/09/api-design-rusty-levels/
• ols-keynote-2003

The numbers are points. Pick the points that apply to your API, add them up, lower is better.

1. It's impossible to get wrong.

2. Compiler/linker won't let you get it wrong.

3. Compiler will warn if you get it wrong.

4. The simplest use is the correct one.

5. The name tells you how to use it.

6. Do it right or it will always break at runtime.

7. Follow common convention and you'll get it right.

8. Read the documentation and you'll get it right.

9. Read the implementation and you'll get it right.

10. Read the correct mailing list thread and you'll get it right.

11. Read the documentation and you'll get it wrong.

12. Follow common convention and you'll get it wrong.

13. Do it right and it will break at runtime.

14. The name tells you how not to use it.

15. The obvious use is wrong.

16. Compiler will warn if you get it right.

17. Compiler won't let you get it right.

18. It's impossible to get right.