So scientific processes have a little trick up their sleeves called the Null Hypothesis. The null hypothesis, or default answer, is generally assumed true until evidence indicates otherwise. How often do you use this process to mutate your software development process? How do you protect yourself from the confirmation bias during your process improvement experiments? Do you see this null hypothesis at work in the TDD process of proving a unit test fails before the implementation code creates evidence to indicate otherwise?
|France is Bacon|
Be careful with a southern US accent when you communicate Francis Bacon - you may create this mental model.
And now for some serious fun - Hank Green's song I F***ing Love Science.
"...it's a process, not an ideology..."