It's time for our next round of our Twitter book club, and you're invited! Each week, we'll host a Twitter chat on Thursday at 6pm PT to discuss a chapter of The Programmer's Brain: What every programmer needs to know about cognition. We start with Chapter 1 on March 10.

Why join? Because learning is more fun together!

How to Participate

If you want to read along with us, here's what you need to do:

1. Pick up a copy of The Programmer's Brain.
2. Before the day of the Twitter chat, read the assigned chapter for the week. Jot down any quotes that stand out to you or questions you have.
3. On the day of the Twitter chat, hop onto Twitter between 6pm-7pm PT. Check the @DevEdBookClub Twitter account for the discussion thread.
4. Join the conversation (and tag your replies with #DevEdBookClub)! Check out what other participants are saying. Reply with your own thoughts, experiences, or questions. This is a great time to learn from each other and make new friends!

If you can't attend during the scheduled time, you can still add to the conversation after the fact. We'd love to hear your thoughts, whenever you have time to share them! We'll also update this post with links to each thread, so you can easily catch up on all the conversations in one place.

Schedule

Like to plan ahead? Here's when we're currently planning to discuss each chapter.

Part 1: On Reading Code Better

• March 10, 2022: Chapter 1 (Decoding your confusion while coding)
• March 17: Chapter 2 (Speed reading for code)
• March 24: Chapter 3 (How to learn programming syntax quickly)
• March 31: Chapter 4 (How to read complex code)

Part 2: On Thinking About Code

• April 7: Chapter 5 (Reaching a deeper understanding of code)
• April 14: Chapter 6 (Getting better at solving programming problems)
• April 21: Chapter 7 (Misconceptions: Bugs in thinking)

(April 28: No Twitter chat this week. Catch up on the reading, or have a nice break!)

Part 3: On Writing Better Code

• May 5: Chapter 8 (How to get better at naming things)
• May 12: Chapter 9 (Avoiding bad code and cognitive load: Two frameworks)
• May 19: Chapter 10 (Getting better at solving complex problems)

Part 4: On Collaborating On Code

• May 26: Chapter 11 (The act of writing code)
• June 2: Chapter 12 (Designing and improving larger systems)
• June 9: Chapter 13 (How to onboard new developers)

General Wrap-up

• June 16: General Wrap-Up / Final Thoughts

Have questions?

Leave a comment below, or reach out to us on Twitter!

See you on March 10!