Contribution 38
From WikiContent
(Difference between revisions)
(Removing all content from page) |
|||
| (2 intermediate revisions not shown.) | |||
| Line 1: | Line 1: | ||
| + | == Community == | ||
| + | |||
| + | As the architect, you make decisions that will affect the community revolving around your project for many years. In a way, the software design itself is part of the architecture. The way people come into the community and the way people leave are also part of it. A complicated architecture is difficult because the connections between the parts are blurred by the volume of noise, and many good people turn away. An architecture simple by decree is hard to work with because only things declared simple are allowed, and people feel helpless. | ||
| + | |||
| + | |||
| + | By [[Evan Cofsky]] | ||
| + | |||
| + | This work is licensed under a | ||
| + | [http://creativecommons.org/licenses/by/3.0/us/ Creative Commons Attribution 3] | ||
| + | |||
| + | Back to [[97 Things Every Software Architect Should Know]] home page | ||
Current revision
Community
As the architect, you make decisions that will affect the community revolving around your project for many years. In a way, the software design itself is part of the architecture. The way people come into the community and the way people leave are also part of it. A complicated architecture is difficult because the connections between the parts are blurred by the volume of noise, and many good people turn away. An architecture simple by decree is hard to work with because only things declared simple are allowed, and people feel helpless.
By Evan Cofsky
This work is licensed under a Creative Commons Attribution 3
Back to 97 Things Every Software Architect Should Know home page
