This is the final episode of Reading Notes.

THANK YOU for joining me on this journey.

This Thursday at 7 pm eastern we wrap up Code That Fits in Your Head by Mark Seemann and look at what we've taken away from this book.

You can sign up for free at BookClub.dev.

As always happy reading

This week we look at chapter 16 the last chapter in Code That Fits in Your Head by Mark Seemann.

Join us for the discussion of this chapter Thursday at 7 pm eastern. You can sign up for free at BookClub.dev

This week we look at chapter 15 The Usual Suspects in Code That Fits in Your Head by Mark Seemann.

Resources

• Guide Refactorings With Behavioral Code Analysis (YouTube)
• The Pragmatic Programmer (Amazon)
• Code Complete (Amazon)
• Clean Code (Amazon)
• Software Design X-Rays (Amazon)
• Your Code as a Crime Scene (Amazon)

Join the companion discussion at 7 pm eastern this Thursday. You can sign up for free at BookClub.dev.

Happy Reading

This week we look at chapter 14 Rhythm in Code That Fits in Your Head by Mark Seemann.

Because we are building software for the long term we get the advantage of seeing different rhythms and patterns develop in how we work as individuals, as teams, and even in the code.

I hope you'll join us as we discuss the ideas from this chapter in our free companion discussion. You can sign up for free at BookClub.dev.

Until next time happy reading.

This week we look at chapter 13, Separation of Concerns in Code That Fits in Your Head: Heuristics for Software Engineering, by Mark Seemann.

This chapter is mainly about the composition and decomposition of code. Mark recommends that we aim towards creating a functional core with an imperative shell and shows us some of the advantages of this approach.

We'll discuss the ideas from this chapter on Thursday at 7 pm Eastern. You can sign up for free to join this conversation at BookClub.dev.

I hope to see you there and until next time happy reading.

This week we look at chapter 12 Troubleshooting of Code That Fits in Your Head by Mark Seemann.

Mark shares a bunch of different techniques for troubleshooting. The most intriguing one is using StackOverflow as a rubber duckie.

Resources

• The Pragmatic Programmer (Amazon)
• Rubber Duckie (Amazon)
• Code That Fits in Your Head (Amazon)

Join the free companion discussion Thursday at 7 pm eastern BookClub.dev

This week we are looking at chapter 11 of Editing Unit Tests of Code That Fits in Your Head: Heuristics for Software Engineering by Mark Seemann.

This week Mark mentions three books in the chapter

• Working Effectively with Legacy Code (Amazon)
• Refactoring (Amazon)
• xUnit Test Patterns (Amazon)

We'll be talking about these books as well as other ideas from this chapter on Thursday in the free companion discussion at 7 pm Eastern. You can sign up for free at BookClub.dev.

Happy reading!

This week we look at chapter 10 Augmenting Code in Code That Fits in Your Head by Mark Seemann.

Resources:

• Strangler Fig Pattern
• Semantic Versioning

Join the free companion discussion this Thursday at 7 pm Eastern. You can sign up at BookClub.dev.

This week we look at chapter 9 Teamwork in Code That Fits in Your Head by Mark Seemann.

We'll be discussing the ideas in this chapter this Thursday at 7 pm Eastern. You can sign up for free at BookClub.dev

This week we look at API Design or chapter 8 of Code That Fits in Your Head by Mark Seemann.

We talk about two concepts this week

• poka-yoke or the idea of mistake-proofing
• Writing for our readers

Mark includes a Hierarchy of Communication

1. Guide the reader by giving APIs distinct types.
2. Guide the reader by giving methods helpful names.
3. Guide the reader by writing good comments.
4. Guide the reader by providing illustrative examples as automated tests.
5. Guide the reader by writing helpful commit messages in Git.
6. Guide the reader by writing good documentation.

We'll be discussing these ideas and more this Thursday at 7 pm eastern in the free companion discussion.

You can sign up for free at BookClub.dev.

I hope to see you there and until next time happy reading.