9 weeks · 5 Oct – 7 Dec
The Pragmatic Programmer, 20th Anniversary Edition
David Thomas & Andrew Hunt · Get the book
-
✓
A Pragmatic Philosophy Done
Before any technique comes an attitude. Own your work, your mistakes, and your growth. -
✓
A Pragmatic Approach Done
Good design is whatever makes the next change cheaper. This chapter gives you the habits that keep code easy to change. -
✓
The Basic Tools Done
Your tools set the ceiling on how fast you can think in code. This chapter is about owning them instead of fighting them. -
✓
Pragmatic Paranoia Done
You can't write perfect software, so write code that notices when things go wrong and says so loudly. -
✓
Bend, or Break Done
Requirements always change, so code has to bend. This chapter is about coupling, and how to keep it low enough that change doesn't break you. -
6
Concurrency This week
Most concurrency bugs come from two things, hidden ordering assumptions and shared mutable state. This chapter shows how to design both out. -
7
While You Are Coding Opens 16 Nov
-
8
Before the Project Opens 23 Nov
-
9
Pragmatic Projects Opens 30 Nov
Reading along? Join the club to discuss each week's prompts with other developers.