> Plumbing knowledge, for example, is constantly tested by whether the place floods after you’ve advanced your theory about what pipe connects to what. You need to get it right because it costs you something when you get it wrong.
Sure, for obvious failures where water is leaking in a spectacular fashion. But there's tons of shoddy non-obvious projects that work and look fine now. The problems come down the road, years later. Usually these problems come from either cutting corners or working under constraints.
You know those horror stories programmers or sys admins trade? How they saw something and couldn't believe their own eyes? Plumbers have those too, in buckets.
Maybe this whole paragraph about the plumbing is just a meta commentary on the "nobody knows what's going on". In that case, disregard the above.
Sure, for obvious failures where water is leaking in a spectacular fashion. But there's tons of shoddy non-obvious projects that work and look fine now. The problems come down the road, years later. Usually these problems come from either cutting corners or working under constraints.
You know those horror stories programmers or sys admins trade? How they saw something and couldn't believe their own eyes? Plumbers have those too, in buckets.
Maybe this whole paragraph about the plumbing is just a meta commentary on the "nobody knows what's going on". In that case, disregard the above.