441: The Pickaxe Book with Noel Rappin

The Bike Shed

For a long time, Programming Ruby was the authority in the developing world. Now, a much-needed update has been published. During this conversation, we are joined by Noel Rappin, who shares how his frustration at the idea of static type in Ruby motivated him to investigate why he felt this way, as he published his findings in The Pickaxe Book. We discuss how this book differs from previous material he has published, explore a recent blog post series that explored the idea of failing fast, and address the widespread opinion that developers should take a simpler approach that is more accessible. Noel also explores the responsibility of understanding how readers consume material and the importance of providing thorough context as an author, how Programming Ruby became the most significant programming reference, and the surprising journey that led Noel to realize he was able to provide an updated version of the theory in it. Next, we dive into some of the more opinionated blog posts Noel has posted and the harshest feedback he has received in response to them. You’ll also hear about his research and learning during the act of writing the book. Join us today to hear all this and more.

Key Points From This Episode:

Noel Rappin’s recently published work, The Pickaxe Book, on current versions of Ruby.
The inception of the book during discussions about the collision of Sorbet and Ruby.
How his background made him comfortable with the idea that there are no static types.
A recent blog post series and how it answered a question about failing fast.
Considering whether developers pursue simpler things that are more accessible to a wider range of coders.
The problem of thoroughness and longevity in writing instructional material.
Developing awareness of how readers consume and contextualize theory and opinion.
How Programming Ruby became the most significant programming reference.
Noel’s updated version of this material in his latest book.
His blog posts on real-life applications of Ruby and the feedback he receives.
How he goes about framing blog posts as opinion or instruction.
Determining what community consensus is.
The bewilderment that often accompanies onboarding sessions.
Research and learning leading up to writing and publishing the book.
Feedback and reviews on the book.

Links Mentioned in Today’s Episode:

[Noel Rappin](Noel Rappin)
[Noel Rappin on X](Noel Rappin on X)
[Programming Ruby](Programming Ruby)
[How Not to Use Static Typing in Ruby](How Not to Use Static Typing in Ruby)
[David Copeland Talk](David Copeland Talk)
[Better Know a Ruby Thing](Better Know a Ruby Thing)
[How To Manage Duplicate Test Setup, Or Can I Interest You in Weird RSpec?](How To Manage Duplicate Test Setup, Or Can I Interest You in Weird RSpec? )
[Better Know a Ruby Thing: On The Use of Private Methods](Better Know a Ruby Thing: On The Use of Private Methods)
[Standardrb](Standardrb)
[Rails Test Prescriptions](Rails Test Prescriptions)
[Programming Ruby: A Pragmatic Programmer’s Guide](Programming Ruby: A Pragmatic Programmer’s Guide)
[The Bike Shed](The Bike Shed)
[Joël Quenneville on LinkedIn](Joël Quenneville on LinkedIn)
[Support The Bike Shed](Support The Bike Shed)

Support The Bike Shed