Imaginary problems are the root of bad software

The chief catalyst for bad software is imaginary problems, according to this author. Complex or broken software isn’t purposely designed to be overly complex or dysfunctional, but instead is designed to do something other than its intended purpose. When communicating requirements to development teams through a chain of sales, management and technical departments, some aspects will inevitably get lost in translation, leading to the creation of imaginary problems which can affect the quality of software. Ultimately, the perpetual solving of these imaginary problems helps teams or companies to grow, and employees to find escapism in their work.

To top