Programmers tend to notice False dichotomy because they repeatedly experience that a model designed with Boolean based on a false dichotomy is changed to Boolean when they learn the details of Specific Needs and use case and it becomes clear that they made a mistake. The theory is that we have repeatedly been forced to change the design when we learned the details of Specific Needs and use case.

It is easy to understand the harm of the “false dichotomy” because of the specific experience of having to pay additional costs due to the false dichotomy.


This page is auto-translated from /nishio/プログラマは誤った二分法に気付きやすい using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. I’m very happy to spread my thought to non-Japanese readers.