Gernot Starke hat mich dank seines Blog-Posts daran erinnert, dass ich noch die “Checkliste zur Überprüfung von Softwarearchitekturdiagrammen” teilen wollte.
Checkliste Softwarearchitekturdiagramme

Gernot Starke hat mich dank seines Blog-Posts daran erinnert, dass ich noch die “Checkliste zur Überprüfung von Softwarearchitekturdiagrammen” teilen wollte.
Last Saturday, I got some bone conduction headphones. Knowing that some housework is coming up, I wanted to use that time “productively” and listen to some good audiobooks. I also read Simon Wardley’s book awhile ago, but wanted to go over it again just for fun, but never found time lately. So what why not LISTEN to Simons’s book?
Another great talk from Eric Evans about the beginnings of the Domain Driven Design book and the development until today! Here is, what I took away: The second title “Tackling complexity in the heart of software” subsume the content of
Uncle Bob explains a great basic architecture pattern for designing understandable software systems. He shows in detail how the Boundary Control (he used “interactor” instead “control” to avoid confusing with the MVP pattern) Entity pattern works. I think its in