Uncle Bob presents the universal rules of software architecture that will help you dramatically improve developer productivity throughout the life of any software system.

"A good architecture comes from understanding it more as a journey than as a destination, more as an ongoing process of enquiry than as a frozen artifact." -- Kevlin Henney

We get together every two weeks for 30 min (to an hour) to talk about the chapter(s). Each meeting consists of an informal 5-10 min review then discussion, e.g. lean coffee style or whatever structure the group prefers. For example, we could discuss what we found helpful, unhelpful, and needed clarifying. As you read chapters, if you think of something you want to ask or discuss ahead of meeting time, you can also jot it down in the Google doc to discuss on the day. Finally, while it's to your benefit to read the chapter ahead of time, it's not mandatory and you should aim to come to book club regardless. Questions from all levels of experience helps solidify everyone's learning.

Meeting Room: Toronto Office, 6F's Boardroom 2.0

• Comments and questions for meetings
• Chapter summaries

• Martin, Ben
• Andrew Lam
• Ev Cheung
• Camila Herculano
• Arti Singh
• Ken Easson