How Feedback Loops and Interpretive Labor Help Us Develop Better Software
Information naturally flows from those who have more power to those who have less.
4 posts
Information naturally flows from those who have more power to those who have less.
In my last post, I talked about how all systems have flaws, and how these flaws require interpretive labor to be patched or worked around so that the system can keep running. These systems become dysfunctional when it is hard or impossible to learn from that interpretive labor what those flaws are. Without good feedback mechanisms, none of the flaws will be fixed, and the system will not adapt to changes.
As I've said a few times now, all models are wrong. That includes laws and norms, employee handbooks and product roadmaps, system diagrams and city plans. If something is abstracting away from reality, it's creating a gap. What happens when that gap causes problems?
Bureaucracy is stupid, David Graeber writes in The Utopia of Rules: On Technology, Stupidity, and the Secret Joys of Bureaucracy. As the premise for a book, it’s more fertile than it sounds.