Chapter 92. Systems Thinking and the Support Pager
Theresa Neate
A developer and I once discussed quite “enthusiastically” the consequences of the decisions we were making as a delivery team. The API we developed was to specification. It was beautifully documented. We had tested it thoroughly and were proud of it. By all appearances, our job was done. But we still didn’t know how the downstream consumers of the API would receive it.
When I asked about that, the developer responded, “We don’t care about that.” He felt that it was up to them to adjust their consuming service based on what we gave them, seeing as they had been clearly told what we were delivering to them and we had “done it right.” What ensued was our impassioned “discussion” about why that should be our business. We agreed to disagree.
There Are Always Consequences
Everything we do has consequences, good or bad. That is because everything—while it sometimes may appear independent—is always interdependent. Interdependence is fundamental to systems. Everything is a system. Our lives are systems. Everything is also a component of a bigger system.
In that scenario, as it turns out, we had not known about one of the mobile application team’s requirements, and that team’s whole application failed upon receipt of our API. The result was several weeks of API rewriting and retesting. ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access