Özgür Özkök
Conway’s law is an adage in software engineering that states that an organization’s communication structure will inevitably resemble the design of its software. It is named after Melvin Conway, who introduced the idea in a 1967 paper.
The law is based on the reasoning that for a product to function, the authors and designers of its parts must communicate with each other to ensure compatibility between the components. If an organization’s details do not closely reflect the essential functions of the product, or if the relationships between organizations do not reflect the connections between product parts, then the project will be in trouble.
You can’t fight Conway’s law (but you can undoubtedly waste energy trying) — Practical implications of Conway’s law Most software that performs non-trivial tasks is complex. We understand that and welcome that. However, we often feel that much of the software we design, create and deploy is more complicated than […]
Speed of development and speed of repair isn’t only about problem solving and code. Monolithic codebases have fuzzy boundaries of ownership, massive teams with distributed accountabilities and intertwined dependencies. As you consider a microservices architecture don’t forget the cultural changes that need to be made. Nimble teams with autonomy, accountability […]
Speed of development and rate of repair isn’t only about problem-solving and code. Monolithic codebases have fuzzy ownership boundaries, massive teams with distributed accountabilities, and intertwined dependencies. As you consider a microservices architecture, don’t forget the cultural changes that must be made. Agile teams with autonomy, responsibility, and stellar communications […]