Usage
Why architecture matters?
What stands for building architecture remains true for software. You should never engage in a project without passing through a proper phase of design that all stakeholders can understand, contribute to, and agree upon. Building a smart software mental model to effectively support design discussion is a key skill within a team.
Agile methodology has promoted the team as a top-notch unit of value. We craft software as a team. We deliver product as a team. We make decisions as a team. And architecture is no exception. We should design as a team. To achieve this goal, we have no choice except shaping & sharing an ubiquitous software model.
Success in that matter is not an easy task. You need methods and you need tools. Take advantage of this post series to demystify underlying key concepts & learn how to craft highly-valuable materials.
Why architecture matters?
Gentle 101 covering core concepts.
Define and agree upon conventions to enforce model consistency.
End-to-end simple case study.
Deep dive sketch first approach, assets and drawbacks.
Deep dive code first approach, assets and drawbacks.
Map C4 model approach into daily life.
Start your code-first approach journey.
Architecture decisions are important and you should probably track them.