,
24 tweets,
2 min read
Read on Twitter
Average age in the software industry is low
The industry is fast growing and newcomers outnumber highly experienced individuals
Formal education tends to be computer science, rare to see software engineering or architecture
Software systems outlive the developers who work on them (hopefully not literally!)
We are a "community of enthusiastic amateurs"
Functional requirements != fashion
Tech community follows fashions as much as any other
Check out the Garter Hype Cycle 
Productivity doesn't come until long after peak hype
Some concepts never escape the Trough of Dissilusionment (UML!)
There are a lot of cognitive and social biases attached to what we think is good / important
Software architecture should be a response to the needs and qualities of the system. The structure should not be chosen based on fashion
There are lots of trade-offs which need to be understood and balanced against the needs
There are lots of external forces acting on a system. The net force will be zero, hopefully not because the system has collapsed
Projects often fail due to non-functional requirements / qualities. These are often not explicitly analysed, designed or documented
Emergent == hard to model, predict and control
Often, emergent == accidental
Software architecture is really about considering qualities and constraints while facilitating the features
"Functionality is independent of structure"
Choose your architectural style based on the qualities you require
Difficult to monitor qualities, but they can be planned for
Most stakeholders are feature-oriented
"look after the quality attributes - the features will look after themselves"
