Re:The terrorist inside my husband's brain
by dredmorbius on Saturday October 01, 2016 @09:40PM
(#12620711)
Lack of systemic thinking across a great many areas is unfortunately overly common. Including in software and technology, but hardly limited to that.
Answering the criticism raised in several responses, it's not that a deep and systemic understanding is specific to software, and inapplicable elsewhere. Yes, the fact of a human-constructed system may make the intention of a system clearer, and its detection easier, but the entirety of existance, at least as our brains are fundamentally equipped to make sense of it, is a system. Primary phenomena are rooted in underlying systems, prerequisites, causes, and interactions. "Five whys", or any other set of inductive explorations, is not a privilege of software systems and workers alone.
The asystematic approach is one that is, paradoxically, a result of increasing complexity of knowledge itself. Rather than individuals spanning multiple disciplines or even subdisciplines or specialties, they're are trailed off into individual leaf-nodes of research, skill, and application, and efforts to break out of this pigeon hole are obstructed at virtually all levels of the system.
Pay and reward are largely commensurate with specialisation. Reputation is contingent on specialisation. Procedure compensation is contingent on specialisation. Access to diagnostic equipment is contingent on specialisation.
And so forth.
Each individual member associated with treatment has their own very small aspect as their particular area of concern.
In software, it's like the person who resolves a bug in medical pricing codes by simply applying the value that was expected in that specific instance for a price, rather than, say, fixing an algorithm or lookup table such that the right answer appears regardless of specific circumstances (I'm paraphrasing from an actual bug/fix story seen recently). From the point of view of a naive management system, that worker has a very high bug resolution rate -- but they're treating the symptom only of an underlying software deficiency.
In a similar vein: you can "fix" a water spot on a wall by repainting the wall.
Or you could replace the plaster that's been waterlogged.
Or you could seal the exterior wall leak that's allowing water in.
Or you could shore up the foundation that's settled, allowing the wall to leak.
Or you could address the underlying geology -- a sinkhole, ground subsidence, a fault line -- that's causing the foundation to move.
Paint is cheaper than plaster is cheaper than siding is cheaper than concrete is cheaper than earth-moving equipment. And there may be an appropriate level of fix. But walking through the problem to its fundamental source(s) provides a full understanding of the problem.
Answering the criticism raised in several responses, it's not that a deep and systemic understanding is specific to software, and inapplicable elsewhere. Yes, the fact of a human-constructed system may make the intention of a system clearer, and its detection easier, but the entirety of existance, at least as our brains are fundamentally equipped to make sense of it, is a system. Primary phenomena are rooted in underlying systems, prerequisites, causes, and interactions. "Five whys", or any other set of inductive explorations, is not a privilege of software systems and workers alone.
The asystematic approach is one that is, paradoxically, a result of increasing complexity of knowledge itself. Rather than individuals spanning multiple disciplines or even subdisciplines or specialties, they're are trailed off into individual leaf-nodes of research, skill, and application, and efforts to break out of this pigeon hole are obstructed at virtually all levels of the system.
Pay and reward are largely commensurate with specialisation. Reputation is contingent on specialisation. Procedure compensation is contingent on specialisation. Access to diagnostic equipment is contingent on specialisation.
And so forth.
Each individual member associated with treatment has their own very small aspect as their particular area of concern.
In software, it's like the person who resolves a bug in medical pricing codes by simply applying the value that was expected in that specific instance for a price, rather than, say, fixing an algorithm or lookup table such that the right answer appears regardless of specific circumstances (I'm paraphrasing from an actual bug/fix story seen recently). From the point of view of a naive management system, that worker has a very high bug resolution rate -- but they're treating the symptom only of an underlying software deficiency.
In a similar vein: you can "fix" a water spot on a wall by repainting the wall.
Or you could replace the plaster that's been waterlogged.
Or you could seal the exterior wall leak that's allowing water in.
Or you could shore up the foundation that's settled, allowing the wall to leak.
Or you could address the underlying geology -- a sinkhole, ground subsidence, a fault line -- that's causing the foundation to move.
Paint is cheaper than plaster is cheaper than siding is cheaper than concrete is cheaper than earth-moving equipment. And there may be an appropriate level of fix. But walking through the problem to its fundamental source(s) provides a full understanding of the problem.