Very woolly. I was expecting more concrete things like
* Use static types
* Use CI and version control
* Use schema-based data storage
* Prefer function calls to events
* Use formal verification if possible
etc.
* Use static types
* Use CI and version control
* Use schema-based data storage
* Prefer function calls to events
* Use formal verification if possible
etc.
Great idea until it isn't. The article is full of bullshit but one thing is very true. We can't predict the future, especially so when we deal with humans and society where stuff changes fast. Strict schemas are more pain than gain here.
> * Use formal verification if possible
Wonder when F* and the like get mainstream so that "if possible" becomes "almost always".
A healthy practice combines both depending on the nature of the task.
> And is it always applicable?
No heuristic is always applicable.
Exactly. That's why it is called a heuristic and not a rule. :)