Code with Jason

In this episode I talk with Dave Copeland, author of Sustainable Web Development with Ruby on Rails, about organizing Rails code. Dave and I discuss why although many Rails developers are used to it, putting code in Active Record models isn't always the best move. We also share the various tactics we prefer to use in order to keep Rails code organized.

Links:

• Sustainable Web Development with Ruby on Rails
• Dave Copeland on Twitter

In this episode I talk with Mike Rogers about how to Dockerize Rails applications. We talk about the difference between Dockerizing for development and Dockerizing for production, mount volumes, performance trade-offs, and more.

Links:

• Mike's Ruby Starter Kits
• Mike Rogers on Twitter

In this episode I talk with Jason Charnes about StimulusReflex. Jason and I cover what StimulusReflex is as well as some of the core concepts of the technology.

Links:

• Interactive Rails with StimulusReflex
• Jason Charnes on Twitter
• Official StimulusReflex documentation

In this episode I talk with Yoseph Radding, founder of Shuttl, about Courier Configuration Manager.

Links:

• Courier Configuration Manager
• Shuttl

In this episode I talk with Tyler Williams, Software Engineer at Home Game Poker, about the contents of a blog post he recently wrote entitled Heuristics for Object-Oriented Design in Ruby. Tyler and I discuss some of the ideas in his blog post, most of which came from Sandi Metz's book Practical Object-Oriented Design in Ruby (POODR).

Links:

• Tyler's blog post
• Intro to logical arguments for programmers

In this episode I talk with Nate Berkopec, author of The Complete Guide to Rails Performance. Nate and I discuss Puma, front-end performance and building command-line interface (CLI) apps.

Links:

• Speedshop
• Nate Berkopec on Twitter

In this episode I talk with Molly Struve, Site Reliability Engineer at Forem, about a variety of topics including performance, monitoring, types of incidents, dividing time between incident response and preventative work, and, of course, horses.

Links:

• Forem
• dev.to
• Molly Struve on Twitter
• [email protected]

This is another How I'd Build It episode, where listeners send in their feature requirements and we discuss them on the show. In this one we talk about a sailing application where there's a need to keep track of whether members' payments are up-to-date. Adam and I also talk about the YAGNI principle as well as why it's not possible to have high-quality code without tests.

Links:

• Small Batches Podcast
• YAGNI
• How I'd Build It Submission Form

It's commonly accepted that it's better to deploy frequently than to only deploy once in a while. However, an obstacle to achieving this ideal is when you have a long-running feature that can't be released until it's all the way done. In this episode Matt Swanson and I talk about the solution to this problem: release toggles, also known as feature flags.

Links:

• Matt Swanson on Twitter
• Boring Rails
• Martin Fowler's Feature Toggles Article

In this episode I talk with CJ Avilla, Developer Advocate at Stripe about integrating Stripe with web applications using Stripe Checkout. We also digress into mechanical keyboards and the challenges of keeping APIs up to date.

Links:

• Stripe Checkout Docs
• Sample of Stripe Developer Office Hours
• CJ Avilla on Twitter
• CJ's CODE Keyboard
• Stripe Developers on Twitter
• Stripe Developer Resources
• Stripe IRC Channel
• Stripe Support