Agile Complexification Inverter

Truth is a wonderful concept - but can we really know it? I'm very excited about the 2017 release of a Wonder Woman movie.  Can't wait - it looks great, I always love the first in a series.  I like the character development, the WHY of the foundational aspects of the character.  From the preview it looks like we will see  Princess Diana of Themyscira  grow up and the reasons she finds her self in America.  Fascinating... I learned a bit about the truth of the back story of the back story of ... well the history of the creator of the Wonder Woman myth in of all places... a training course on DiSC by Dr. Abelson .  [ Queue the spooky dream sequence music. ] The inventor of the Wonder Woman myth is William Moulton Marston . Wonder Woman made her debut in All Star Comics #8 (December 1941), scripted by Marston.  If you have one in the garage I'll buy it from you.  Apparently, Marston designed Wonder Woman as an allegory for the true lead...

Watch this video ( Can You Solve This? by Veritasium ) to see the scientific process in action (well it takes a while for the people to become scientific... but they do).  My guess is that you - like me - will fall into the fallacy of confirmation bias at the first opportunity.  A phenomena referred to as the black swan fallacy. 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 Since this scientific process is not very natural for us humans; it leaves ...