Summary:
1. Write programs for people, not computers.
2. Automate repetitive tasks.
3. Use the computer to record history.
4. Make incremental changes.
5. Use version control.
6. Don’t repeat yourself (or others).
7. Plan for mistakes.
8. Optimize software only after it works correctly.
9. Document design and purpose, not mechanics.
10. Conduct code reviews.This is exactly what happens for many users when you suggest them to install GNU/Linux and enjoy freedom. They say: «I don't want to learn another OS. I just use the computer to get things done». Then they'll keep using Excel.
It's not a risk, it's a certainty! That's why the the last point is about conducting reviews.
I shall never understand why a work like this (useful and to the point) needs a 'Conclusion' section. There are no conclusions, just a list of practices.
I know this is an absurd rant but can we stop this nonsense?
Conclusion: please stop concluding something which is not an argumentation.
1. Read abstract. Interesting? Go to 2, else stop reading.
2. Read introduction. Still interesting? Go to 3, else stop reading.
3. Read conclusion. Still interesting? Read the rest of the paper, else stop reading.