Fundamentals of Software Architecture - Neal Ford and Mark Richards

[@anitsh]

I'm just listening, rewinding and taking note. 10+years and they take me back to school. True Masters.

[@kaustavchakraborty3244]

Software Architect has to be hands on, Period.

[@mahdiakhi6874]

The book and this video are same. Both are amazing!

[@m0xiemarlinspike]

Decided against the Webinar for security reasons as it required Zoom so really appreciate you sharing the talk here

[@farruhhabibullaev5316]

Tradeoff is not only in software architecture but in whole universe.

[@kamesh7818]

Very useful, I loved this talk. Thank you for sharing.

[@benjaminpope2909]

Just bought the book. Keen!

[@alexandercastillo7876]

I've enjoyed this video as much as the book! such an amazing job!

[@alessandrob.g.4524]

These folks make my head spin

[@armorsmith43]

What you say “illities”, do you mean “abilities” like “observability” or “reliability”?

[@chinhdo6006]

fault-tolerance, backward compatibility, extensibility, reliability, maintainability, availability, security, usability, and other such -ilities. Stakeholder concerns often translate into requirements on these quality attributes, which are variously called non-functional requirements, extra-functional requirements, behavioral requirements, or quality attribute requirements.

[@washedtoohot]

-ilities remind me of -omics in biology, like genomics, proteomics

[@zxyi9090]

Timespan axioms is an axiom which is validated/invalidated over time strictly to software discipline.

[@米德术子]

Software architecture is WHY，while Software design is HOW