From now on, I intend to publish a series on best practices that help create robust code.
It is very important to take into account that these best practices might not be best practices in a different context: techniques that help you write robust code might very well be detrimental to write code at top speed.
So, what’s the context for these “robust code” best practices:
- Projects that must run reliably, with almost no downtime.
- Projects that need to be able to evolve in a very reliable way.
- Public APIs that should remain as stable as possible.
- Projects used by very many users.
You will have to keep this in mind to make sense of some of the best practices I’ll write about!
