Penelope Phippen is a Developer Advocate at Google. She's British, but she lives in New York now. She's known for being Justin Searls at Ruby Conferences as well as her work as a member of the RSpec core team. She describes herself as having a love hate relationship with computers
October 9th, 2019 | 49 mins 52 secs
After the discussions on testing and design in episodes 68 and 69, I had so much I still wanted to talk about in testing, design, and teaching testing and design. So I convened a panel with previous Tech Done Right Guests Avdi Grimm, Betsy Haibel, and Penelope Phippen to help me think through all these topics. I was very happy to have all of them on the show, and I think it's a great conversation. Stay tuned until the very end for an update about the show.
January 30th, 2019 | 47 mins 16 secs
code, communication, developer
On this episode, we’ve got Sam Phippen and Justin Searls back for their third round on the show. Both of them have been working on new Ruby tools to better standardize your team’s style and code formatting. We talk about why they’ve decided these tools are important, what their philosophy of coding style is, how coding style relates to the Ruby community, and how they evaluate code when given a code sample to look at.
We’d like to hear from you. How does your team handle differences of opinion in code style? Let us know at
techdoneright.io/54or on Twitter at
March 28th, 2018 | 41 mins 27 secs
I'm back in the testing weeds with Sam Phippen, lead maintainer for RSpec-Rails, and Justin Searls, co-founder of Test Double and author of testdouble.js. We talk about long-running test suites: are they bad, or just misunderstood? Does parallel CI solve all testing speed problems, or just some of them? Then we move to a wider view, what does it mean to test your library as part of a larger ecosystem. And, how can we leverage coverage or CI information to make for more useful testing tools over the lifetime of a project.
February 22nd, 2017 | 49 mins 16 secs
Sam Phippen, Justin Searls, and Noel Rappin spend this episode talking about the value of test-driven development (TDD) as well as its cost. They discuss the kinds of problems that developers are likely to have after they learn TDD and attempt to apply it to a large application. Learn why Rails is both great and terrible for automated testing, and how testing can influence the structure of your code.