[image source: Vilkasss on pixabay.com]
There is a subspecies of humans (let's call them Tech-Troglodytes of the "Rabid Agile™" clan) - that insist:
a. You don't need diagrams
b. You don't need documentation
c. The source code is all that matters.
Requiring each person (many of whom may not be technical) to solely develop their understanding of an area by reading [M * N] lines of source code (where [N] may be 10^P, and P may often be > 4)] - encompassing a single application, suites of applications, or the context and behavior distributed across multiple enterprise application domains (some of which may be owned by external partners, or commercial products/services) - would be wasteful, inefficient, and egregiously demonstrates a mind altogether too content with its first and poorest notion.
A good architecture diagram is a work of art - that provides some of the finest levels of abstraction for reasoning about the design, capabilities, and limitations of a system.
No comments:
Post a Comment