It is common to consider software architecture as structure, as infrastructure, as code, as technologies, as models, and so on, but what if we consider architecture as knowledge? The view that software architecture is the set of significant design decisions about a system is not a new one, but revisiting it we can see those decisions represent knowledge.
When we embrace the idea of knowledge as a first class concept, it has implications for our documentation, for our code, for our development process and for how we handle change.
In this session we will look at how represent such knowledge, from code to tests, from commit messages to models, from patterns to architecture decision records. In particular, with the increasing popularity of ADRs, we will look at examples that highlight some common pitfalls in their use along with the guidelines that address them.
🎫Get your tickets for Build Stuff 2024: [ Ссылка ]
