[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"lesson-software-architecture-architecture-in-practice-en":3,"cheat-sheet---en":3,"topic-info----en":3,"prev-software-architecture-architecture-in-practice-en":3,"next-software-architecture-architecture-in-practice-en":3,"domain-info-software-architecture-architecture-in-practice-en":4},null,{"meta":5,"body":8},{"title":6,"description":7},"Architecture in Practice","The daily craft that separates working architects from diagram owners. You document with C4 views and ADRs, evaluate designs with scenarios and fitness functions, manage technical debt, and modernize legacy systems without a risky rewrite.",{"type":9,"value":10,"toc":15},"minimark",[11],[12,13,14],"p",{},"This domain covers the part of the job that happens between the diagrams: writing documentation people actually read, recording decisions before the reasons are forgotten, reviewing designs before they fail in production, and steering old systems toward new shapes. It ends with the human side: how an architect earns influence inside a team.",{"title":16,"searchDepth":17,"depth":17,"links":18},"",3,[]]