Books
Release It Book Club Chapter 1 Qa Team
Does your company have a traditional QA team? If so, what percentage of defects do you think they catch?
We don’t have a QA team at Seeq. In chapter 1 of Release It! Michael Nygard talks about how some engineers develop code for the QA team to verify rather than for the customer to use or to work well in production. I think that I have been guilty of that - especially some of the work I did at Groupon comes to mind. At Seeq, the bigger temptation is to write software for the support team to manage and keep running.
Release It Book Club Chapter 1 War Story
What’s the hairiest or most expensive production bug you’ve had to fix?
#ReleaseItBookClub #ReleaseItBookClubChapter1
Release It Book Club Loneliness
I think no one is reading this book with me. I miss you all. 🥹 You can just assume from now on the replies to these posts are me answering my own discussion questions 🤣. Or you can respond without reading the book. Maybe someone will pick it up sometime and follow the breadcrumbs.
Release It Book Preface Discussion 2
The preface of Release It! states, “If anybody has to go home for the day because your software stops working then this book is for you.” Do you work on something with that level of criticality? What do you work on that might be helped by the advice in this book?
#ReleaseItBookClubPreface #ReleaseItBookClub
Discuss on:
Release It Book Preface Discussion 1
What are you hoping to learn from Release It!? What are you hoping to get out of the book club?
#ReleaseItBookClubPreface #ReleaseItBookClub
I wasn’t sure what to expect from this book. Based on the title, I thought it would be about Continuous Delivery, deployment strategies, etc. Maybe it will touch on those topics, but it seems to be much more focused on the design of robust software in production. So now I am hoping that this book will help me espouse these principles of robustness in my own work and throughout my company. Similarly, for the book club I’m looking forward to hearing everyone’s thoughts and experiences on the content of the book to see how it could be applied in different contexts, and hopefully receive some inspiration for applying it in my context.
Release It Book Club Starts Next Week
#ReleaseItBookClub starts next week! You can obtain your copy (use discount code stevenoxley at pragprog.com) and start reading. I’ll start posting discussion questions next week using tag #ReleaseItBookClub and tag pattern #ReleaseItBookClubChapterN so you can read and discuss at your own pace. See you there!
Release It! Book Club Discount
I have news! You can use the discount code stevenoxley to get a 40% discount on Release It! Second Edition by Michael T. Nygard - making it that much easier to join the async book club that I’m starting here in February.
Release It! Async Book Club
I’m starting an async book club for the book Release It! Second Edition by Michael T. Nygard and you’re invited to join! You can sign up here to register your interest and (hopefully) get a discount on the book: https://forms.gle/kti3xFYD7cMjEBYk9. Or go ahead and buy the book now (I already have mine). I plan to start reading and posting discussion questions at the beginning of February. I’m looking forward to it, and feel free to spread the word - all are welcome!
Team Topologies Book Club: Chapter 1 Discussions
I love books. I love reading books about work. I especially love discussing books related to work with my colleagues, so I frequently run and participate in book clubs at work. I’m currently running a book club with the book Team Topologies by Matthew Skelton and Manuel Pais, and I thought I’d share the discussion questions I’m using for the book club. Here are the questions for chapter 1:
- What are the takeaways you have from this chapter?
- What ways have you seen our company’s org chart mismatch our communication structures?
- What are examples you’ve seen of missing dynamic and sensing aspects of traditional organization design?
- How are we doing with regard to the five rules of thumb for designing organizations?
- Design when there is a compelling reason.
- Develop options for deciding on a design.
- Choose the right time to design.
- Look for clues that things are out of alignment.
- Stay alert to the future.
- What are some examples you’ve seen of Conway’s law in action at our company?
- What are some examples where teams at our company have had to deal with excessive cognitive load?