Episode 54: Code Style and Community with Sam Phippen and Justin Searls

Code Style and Community with Sam Phippen and Justin Searls
TableXI is now offering training for developers and products teams! For more info, email [email protected] or visit http://www.tablexi.com/workshops.
Guests
Sam Phippen (https://twitter.com/samphippen): Developer Advocate at Google and member of the RSpec (https://github.com/rspec) Core Team
Justin Searls (https://twitter.com/searls): Cofounder of Test Double (http://testdouble.com/)
Summary
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/54 or on Twitter at @tech_done_right
Notes
02:21 - Code Style
Bikeshedding (https://en.wiktionary.org/wiki/bikeshedding)
Standard JS (https://standardjs.com/)
standard Ruby Gem (https://rubygems.org/gems/standard)
rubocop (https://github.com/rubocop-hq/rubocop)
Hash Rockets are good actually (https://samphippen.com/hash-rockets-are-good-actually/)
Sandi Metz: Why We Argue Style (https://www.sandimetz.com/blog/2017/6/1/why-we-argue-style)
09:46 - Choosing Ruby: Community Standards vs Style
14:59 - Evaluating Code Samples for Developer Positions
- Gilded Rose Refactoring Kata (https://github.com/emilybache/GildedRose-Refactoring-Kata)
21:04 - Ruby Format
29:05 - Selecting Rules For Standard
35:38 - Discrepancies in Rails View Template Files
- haml-lint (https://github.com/brigade/haml-lint)
39:10 - What happens if these projects aren’t successful?
- Why's (poignant) Guide To Ruby (https://poignant.guide)
Previous Justin/Sam Episodes:
Part I: Episode 004: In The Testing Weeds (http://www.techdoneright.io/004-testing-with-sam-and-justin)
Part II: Back in the Testing Weeds with Sam Phippen and Justin Searls (https://www.techdoneright.io/33) Special Guests: Justin Searls and Penelope Phippen.

Code Style and Community with Sam Phippen and Justin Searls

TableXI is now offering training for developers and products teams! For more info, email [email protected] or visit http://www.tablexi.com/workshops.

Guests

Sam Phippen: Developer Advocate at Google and member of the RSpec Core Team
Justin Searls: Cofounder of Test Double

Summary

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/54 or on Twitter at @tech_done_right

Notes

02:21 - Code Style

Bikeshedding
Standard JS
standard Ruby Gem
rubocop
Hash Rockets are good actually
Sandi Metz: Why We Argue Style

09:46 - Choosing Ruby: Community Standards vs Style

14:59 - Evaluating Code Samples for Developer Positions

Gilded Rose Refactoring Kata

21:04 - Ruby Format

29:05 - Selecting Rules For Standard

35:38 - Discrepancies in Rails View Template Files

haml-lint

39:10 - What happens if these projects aren’t successful?

Why's (poignant) Guide To Ruby

Previous Justin/Sam Episodes:

Part I: Episode 004: In The Testing Weeds

Part II: Back in the Testing Weeds with Sam Phippen and Justin Searls

Special Guests: Justin Searls and Penelope Phippen.