Rank #1: 9: Tools That are Well Built Will do it for us!
We’re still time travelling, Sam has since left DigitalOcean, but in this episode, he talks about his experiences there.
Sean talks about his experiences managing the crates.io team, and incidents on an open source project with volunteer time. Sam talks about his experiences scaling go programs, and processes vs threads, as well as why kubernetes makes the trade offs between goroutines and processes pretty unimportant.
Feb 11 2019
Rank #2: 6: The Podcast After the Last Podcast
This week Sean is joined by former cohost Derek Prior. After a brief reflection on the end of The Bike Shed, we discuss WebAssembly and what it means for the future of the web as well as native sandboxing. Finally, we catch up on what Derek has been doing since leaving The Bike Shed.
Corrections from this episode:
- Emscripten and the LLVM backend were mixed up. Emscripten is not part of LLVM, and Rust moved from Emscripten to the LLVM backend.
- Virtually every time Sean said "unprivileged" he meant to say "privileged"
Oct 23 2018
Rank #3: 3: Almost 0% Chance it's a Bug
In this episode of The Yak Shave, Sean shares the most nightmarish debugging experience he has had in a long time. rails_fast_attributes was down to one failure, which manifested itself as a test where a query was expected to run 269 times, but only ran 265 times. After testing, troubleshooting, and finding the root cause, he determined that it was actually behaving completely fine.
Sep 28 2018
Rank #4: It's not a Pyramid, it's a Diamond
Sean and Sam talk all about testing. Sam created an ideal testing pyramid based on personal experience and from talking with test thought leaders, such as Justin Searls. The testing pyramid has “integrated” at the top, and “isolated/unit” at the bottom, along with a wide base and X axis for the number of tests you should be writing. Write as few integration tests as possible, although you may write some that you don’t keep. Isolated tests refer to where the only thing you are executing is one file or function’s worth of code. Then, there’s some tests to never write. You should be able to look at a test and know instantly if it’s correct or not. Whether using a pyramid or bowtie scheme, teams should embrace testing, rather than hate it.
Dec 04 2018
Rank #5: 8: Vulnerability
Yak Shave - Episode 8
This episode was recorded on October 21st 2018. We thought it best to get this to you, even though it's a little stale :)
Remember that dark, scary time in October 2018 when GitHub went down? Sean is joined by Derek once again to discuss what they've been up to. Sean not only experienced frustration with GitHub’s downtime, but Crates.io's dependency on it. There’s been a lot of heated discussions in the community about Crates.io’s policies, or lack thereof. Specifically, focus has been put on crate name squatting - the practice of uploading an empty crate to reserve the name. Sean wants to prevent or eliminate such disruptive and malicious behaviors and actions that force action to be taken and policies to be revised or created. Do not disrupt service to make a point. It wastes everybody’s time! Sean had a stressful week and knows he will not always agree with users. But, in the future, he promises to remain engaged and responsive. Fortunately, Derek had a good week - thanks to the Suggested Changes feature he released for GitHub.
Feb 04 2019