O'Reilly logo
  • Erdem Azaklı thinks this is interesting:

Regardless of your approach to architecture, you can benefit a lot from attempting to diagram and model your architecture. When working as a consultant my team and I joined many different software development teams, and it was expected by clients that I would understand the software system and become productive working with it as soon as possible. One of the first things I did on any new project was ask the current team to provide an overview of the architecture -- I use the analogy of software architecture as a map (with high-level components, structure, and interactions) of the underlying terrain (code and deployment config). Most of the time the team had to draw the architecture on a whiteboard because they didn’t mainta...


Cover of Continuous Delivery in Java


Ne olursa olsun