First time I heard about systems thinking was when discussing common traits of object-oriented analysis and design methods, in the 90’s, with colleagues at our first software development startup consulting firm. The discussion soon turned to general systems theory and several authors were mentioned; for example, Ludwig von Bertalanffy, Peter Checkland, Kenneth E. Boulding, Mario Bunge, Norbert Wiener, and of course, Gerald M. Weinberg, among many others.
Since then I have been studying this subject matter, along with the historical development of systematic approaches to software design, not just because these topics are directly related to my daily professional work (software solutions from inception, delivery, and evolution), but also because developing knowledge about all this is pure cheer joy.
It turned out that I found the need to go even deeper in order to avoid the misconception of the buzzwords; that is, a misuse of language by which people assumes that the positive effects of concepts comes from using and repeating the words without the required effort of continuously developing a proper understanding of those concepts.
It was obvious for me then that there is always need to be self-aware of the degree of my own scientific and philosophical illiteracy in order to face a proper systems thinking approach to professional work not just in software but in other professional activities, where the software would be just one component of the solutions.
The systems thinking approach changed my life forever, not just my professional life but also my approach to the world in general. There are colossal differences between my worldview before knowing about systems thinking, my progressively adjusted worldview during my journey since, and my current worldview (I am still adjusting it).
Just as an example of my daily work, now I am able to spot more easily the place, and the suitable limits, for dogmatic opinion and behavior while designing software in professional teams.
