43. It’s Always the Goddamned Interfaces
Project team members focus relentlessly on interfaces, both automated and human.
In order to design a system, we must know the interfaces between the system and the environment. We need to know the system’s raw inputs and its final products. Until we have that census of inputs and outputs, we are in preliminary analysis: We have not bounded the problem. Once we have that census, we can start to define the functionality of the system.
What happens in design, after we get agreement on functionality? We break a large, complex system into subsystems, and subsystems into components. And yes, a useful way to ...
Get Adrenaline Junkies and Template Zombies: Understanding Patterns of Project Behavior now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
