Mark   Richards

Mark Richards’s Followers (54)

member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo

Mark Richards


Genre



There are multiple authors with this name in this data base. This one is Mark^^^Richards.

Average rating: 4.1 · 2,444 ratings · 281 reviews · 7 distinct worksSimilar authors
Fundamentals of Software Ar...

by
4.26 avg rating — 1,720 ratings — published 2020 — 2 editions
Rate this book
Clear rating
Software Architecture Patterns

3.65 avg rating — 465 ratings — published 2015 — 2 editions
Rate this book
Clear rating
Microservices AntiPatterns ...

4.04 avg rating — 113 ratings
Rate this book
Clear rating
Microservices vs Service-Or...

3.41 avg rating — 94 ratings2 editions
Rate this book
Clear rating
Java Message Service: Creat...

by
3.64 avg rating — 81 ratings — published 2000 — 16 editions
Rate this book
Clear rating
Java Transaction Design Str...

4.15 avg rating — 13 ratings — published 2006 — 5 editions
Rate this book
Clear rating
Software Architecture Funda...

by
3.83 avg rating — 12 ratings — published 2014
Rate this book
Clear rating
More books by Mark Richards…
Quotes by Mark Richards  (?)
Quotes are added by the Goodreads community and are not verified by Goodreads. (Learn more)

“Conway’s law: Organizations which design systems … are constrained to produce designs which are copies of the communication structures of these organizations.”
Mark Richards, Fundamentals of Software Architecture: An Engineering Approach

“The computer scientist Gerald Weinberg is famous for saying, “No matter what the problem is, it’s a people problem.”
Mark Richards, Fundamentals of Software Architecture: An Engineering Approach

“This picture shows someone standing next to a broken-down car on the side of a small country road. In this scenario, how many people might stop and ask the motorist if everything is OK? Because it’s a small road in a small community, probably everyone who passes by. However, how many times have motorists been stuck on the side of a busy highway in the middle of a large city and had thousands of cars simply drive by without anyone stopping and asking if everything is OK? All the time. This is a good example of the diffusion of responsibility. As cities get busier and more crowded, people assume the motorist has already called or help is on the way due to the large number of people witnessing the event. However, in most of these cases help is not on the way, and the motorist is stuck with a dead or forgotten cell phone, unable to call for help. An effective architect not only helps guide the development team through the implementation of the architecture, but also ensures that the team is healthy, happy, and working together to achieve a common goal. Looking for these three warning signs and consequently helping to correct them helps to ensure an effective development team.”
Mark Richards, Fundamentals of Software Architecture: An Engineering Approach



Is this you? Let us know. If not, help out and invite Mark to Goodreads.