Ruby Rogues

Sponsors

• Sentry use code “devchat” for $100 credit
• Datadog
• React Native Radio

Panel

• David Kimura
• Andrew Mason

With Special Guest: Paul TarjanEpisode SummaryPaul Tarjan works for Stripe specializing in developer productivity. In the past, he has owned his own company and worked for Facebook. In today’s episode, the panel is talking about Sorbet, a gradual type checker for Ruby that Paul built. Paul talks about how Sorbet fits in the Ruby community and how it works. The two parts of Sorbet are the runtime type check and the static typecheck. Paul talks about how introducing Sorbet at Stripe has changed the way they approach coding. He talks about some of the performance impacts of adding Sorbet, how it differs from other type checkers, and how it was received in the Ruby community. Paul delves into how developers are notified if Sorbet fails a type check while checking a class. The panel discusses ways to convince reluctant team members that introducing a type checker like Sorbet will improve their code, and Paul talks about his experience implementing it at Stripe. He talks about what he sees for the future of Sorbet. The show finishes with the panel discussing similar projects in other languages and their opinions on React in light of Paul’s former employment with Facebook.  Links

• Stripe
• Sorbet
• Sorbet Rails
• Sorbet Static
• Ocra
• mypy
• TypeScript
• Sorbet.run 
• Flow
• React

Follow DevChat on Facebook and Twitter PicksAndrew Mason:

• Stimulus Reflex

David Kimura:

• Pingverse

Paul Tarjan:

• Follow Paul https://paultarjan.com/
• Sorbet

Special Guest: Paul Tarjan.

Advertising Inquiries: https://redcircle.com/brands

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.

Sponsors

• Sentry use code “devchat” for $100 credit
• Datadog

Panel

• David Kimura
• Andrew Mason
• Charles Max Wood

With Special Guests: Julian FahrerEpisode Summary Julian Fahrer has been a guest on Devchat shows before and recently did a workshop at RailsConf about Docker. He specializes in teaching people about Docker and has his own course, LearnDocker.online. Julian begins by giving suggestions for those considering Dockerizing their Rails applications. He talks about why Docker is a good choice to be used in a local development environment and gives some advice for those who might have trouble running Docker in development. He talks about where Docker fits within the development or production environment. He talks about synchronizing code between development and production and running tests. He advises listeners on how to get started with Docker. He talks about using a Docker registry to build and push images. They discuss how to deal with things once you move to production and how to use containers when considering microservices. Julian talks about debugging in Docker. They finish by talking about Docker’s compatibility with frameworks besides Rails and how services talk to each other in Docker.  Links

• JSJ 340: JavaScript Docker with Julian Fahrer
• EMX 10: Docker with Julian Fahrer
• Docker
• Heroku
• Alpin.io
• Ubuntu
• Docker Sink
• OSXFS
• Spring
• Webpacker
• AWS 
• PostgreSQL
• Elasticsearch
• Kubernetes
• Scripts to Rule Them All
• LearnDocker.online

Follow DevChat on Facebook and Twitter PicksAndrew Mason:

• Alsop Metal Art Dual Monitor Arms 
• Mental health days

David Kimura:

• Arcade buttons
• Mini Dewalt air compressor

Julan Fahrer:

• Alexander Technique
• Railswithdocker.com
• Blitz
• Donner
• Follow Julian at Codetales.io and @jufahr

Charles Max Wood: 

• Four Corners Monument
• Dallas Children’s Museum

Special Guest: Julian Fahrer.

Advertising Inquiries: https://redcircle.com/brands

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.

Sponsors

• Sentry use code “devchat” for $100 credit
• Datadog

Panel

• David Kimura
• Andrew Mason
• Nate Hopkins

With Special Guests: Taylor JonesEpisode SummaryTaylor Jones works remotely for Heroku in technical support. He talks about some of the most common issues he helps customers with and what issues he saw when Webpacker was introduced. The panel talks about their experience using Webpacker and how it has influenced their usage of React and Ruby. They talk about the importance of creating maintainable applications and the possible effects of using primarily new technology versus tried and true methods. It is important to keep architecture consistent, so that if you have to debug something old, you still know your way around. They discuss the forward progress in the Rails community and how the need for a JavaScript framework has decreased. They discuss improvements in adding elements from other languages into your code, especially since Webpacker added a way to manage JavaScript assets to the community. They discuss the impact Webpacker has had on application maintainability. For a more sustainable app, they suggest reducing the number of gems and dependencies in your application, and over all knowing what you’re putting in your app.Links

• Heroku
• Webpacker
• React
• Slack
• jQuery
• Ember
• Broccoli.js
• Stimulus
• Turbolinks
• Bootstrap
• Conductor
• Zoom

Follow DevChat on Facebook and Twitter PicksAndrew Mason:

• Migration Builder by Jason Swett demo video

David Kimura:

• Build-your-own arcade machine
• Honey 

Taylor Jones: 

• Slack Engineering Team 
• Shape Up book from Basecamp
• Follow Taylor @hiimtaylorjones

Special Guest: Taylor Jones.

Advertising Inquiries: https://redcircle.com/brands

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.

Sponsors

• Sentry use code “devchat” for $100 credit
• Datadog

Panel

• David Kimura
• Nate Hopkins
• Andrew Mason

Episode SummaryToday the panel is talking about documentation. They begin by discussing what documentation is, where it fits within an application, and if the code documents itself. They agree that documentation starts in the comments to explain what you’re doing, but if that’s your exclusive method, then a refactor is in order. They talk about where to start with documentation and different ways they’ve done it. The panel talks about the importance of documentation, especially for people just joining a team. In addition to documenting the project itself, it is important to document what different libraries do and how to interact with them. They discuss where to put this kind of documentation. They talk about documenting patterns, best practices, and procedures in addition to the ‘how to’ of a project. The conversation turns to style guidelines, what they are, and how to keep them up to date. They talk about what tools are available to generate documentation that are close to the code but outside of it that can help keep documentation up to date. The panel believes that there is a relationship between the size of your team and the necessity to document. Nate introduces the idea found in the article by Tom Preston-Werner that you should think about what you’re going to create in the code, and document it first. Links

• RDoc
• YARD 
• RuboCop
• YAML
• Slim
• ERB
• Prettier
• Pronto
• Api.rubyonrails.org
• Swagger
• Thoughtbot and Thoughtbot Playbook
• AirBNB Ruby
• Testdouble
• HoundCI
• Okonet
• API Blueprint
• Ruby on Rails API documentation guidelines
• Tom Preston-Werner article Readme Driven Development

Follow DevChat on Facebook and Twitter PicksNate Hopkins:

• Code Fund

Andrew Mason:

• SpaceVIM
• RailsDiff
• Rails Releases

David Kimura:

• Jackery Supercharger Portable

Advertising Inquiries: https://redcircle.com/brands

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.

Sponsors

• Sentry use code “devchat” for $100 credit
• Cloud 66 - Pain Free Rails Deployments: Try Cloud 66 Rails for FREE & get $66 free credits with promo code RubyRogues

Panel

• Charles Max Wood
• Andrew Mason

With Special Guests: David A. Black and Joseph Leo IIIEpisode SummaryDavid A. Black has been a Ruby user for 19 years and has been writing books about Ruby for the last 14 years. Joseph spent 12 years in software and started the company Def Method Inc. Together, they co-authored the book The Well-Grounded Rubyist, which will soon have its third edition released. They give some of the history behind The Well-Grounded Rubyist. Joseph talks about his experience being brought into the project. David and Joseph talk about how The Well-Grounded Rubyist is different from other books on Ruby. This book is helpful because a lot of people begin by understanding Ruby more than Rails, and this book talks about ways to think about Ruby and understand how it’s structure. Joseph and David talk about how The Well-Grounded Rubyist 3rd edition differs from the 2nd edition. The book has been updated so that a lot of the code and solutions for the exercises are available online and there is an additional chapter in part 3 about Ruby dynamics and how one would write functional programming with RubyThe panel discusses how important it is to learn Ruby before starting a job in Rails 2. They agree that if you are a Ruby developer, even if you’re working on Rails apps, so you should know your tools. They discuss how far down that road The Well Grounded Rubyist would get readers. They panelists talk about other books that are a natural prequel or sequel to the The Well-Grounded Rubyist. Joseph and David talk about their approach to reading books and how The Well-Grounded Rubyist should be read. Their goal in making the book was not to have people work on an overarching application while reading the book, but rather there are exercises and examples that you are encouraged to work through. There are some lessons in the book that you won’t write often, but you still need to know how to do it. While the book doesn’t have everything about Ruby, but the examples are designed to give you the best returns for you study. David and Joseph conclude by giving their final thoughts on the book.Links

• The Well-Grounded Rubyist, Third Edition
• Perl
• Programming Ruby 1.9 & 2.0: The Pragmatic Programmers' Guide (The Facets of Ruby) 4th Edition
• Practical Object-Oriented Design: An Agile Primer Using Ruby (2nd Edition) by Sandi Metz
• String mutability

Follow DevChat on Facebook and Twitter PicksAndrew Mason:

• Default Gems

Charles Max Wood:

• Good to Great: Why Some Companies Make The Leap and Others Don't by Jim Collins

David A. Black:

• Pragmatic Programmer 2nd edition
• Davidablack.net and @david_a_black on Twitter

Joseph Leo III: 

• Barbarians at the Gate
• Firehydrant.io
• @jleo3 and defmethod.com

Special Guests: David A. Black and Joe Leo III.

Advertising Inquiries: https://redcircle.com/brands

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.

Sponsors

• Sentry use code “devchat” for $100 credit
• Cloud 66 - Pain Free Rails Deployments: Try Cloud 66 Rails for FREE & get $66 free credits with promo code RubyRogues

Panel

• Charles Max Wood
• Andrew Mason

With Special Guest: Daniel PritchettEpisode Summary Daniel Pritchett started doing Ruby in 2012. Lately he has been working on publishing a book on building Chatbots in Ruby using a framework called Lita and does infrastructure for a startup called Gremlin. Gremlin reaches out to servers and tries to find weak spots so that you can be proactive about solving these problems and be better prepared when fires do start. Daniel’s real purpose in joining the show today was to talk about his book Build Chatbot Interactions. Daniel talks about what he defines as a chatbot. His book teaches you how to program a chatbot with a dozen or so different chatbot skills. Daniel talks about his first community chatbot, @elvis on #memtech IRC, which picked up immediate contributions from local developers. Daniel istructs listeners how to host chatbots and some of the skills that people can pull together for a chatbot from his book. The panel talks about things they would like to do with chatbots, as well as some of the drawbacks and things you have to be careful with. Each skill in Daniel’s book can be a stand-alone skill, or they can be combined. Daniel talks about what convinced him to write a book instead of doing tutorials online. If you would like to purchase the book, click here. Source code for all the book exercises can be found here. Links

• Lita
• Huebot
• Coffee Script
• Chatbot
• Azure Functions
• Heroku
• AWS

Follow DevChat on Facebook and Twitter PicksAndrew Mason:

• Lazy Docker

Charles Max Wood:

• Azure Functions

Daniel Pritchett: 

• Asciinema
• Serverless
• Doctoc
• Follow Daniel on Twitter, Github, and his personal blog and portfolio
• Most of the book’s code is also here

Special Guest: Daniel Pritchett.

Advertising Inquiries: https://redcircle.com/brands

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.

Sponsors

• Sentry use code “devchat” for $100 credit
• Cloud 66 - Pain Free Rails Deployments: Try Cloud 66 Rails for FREE & get $66 free credits with promo code RubyRogues
• RedisGreen

Panel

• Charles Max Wood
• Nate Hopkins
• Andrew Mason

With Special Guest: Kir ShatrovEpisode SummaryToday’s guest Kir Shatrov is a production engineer on Shopify based in London, UK. Today, he and the panel are discussing capacity planning. Kir believes that capacity planning becomes a priority when your company starts losing money and your customers are suffering. When someone does get to the point of scaling their app, it’s important to look at the limitations of the hosting service. It is also important to remember that scaling is not a job that ever completes.Kir talks about his experience and time with Shopify and what types of changes have happened in the four years he’s been with the company. Kir explains that when Shopify was founded about 12 years ago, they were some of the first contributors to Rails, and Rails was just a zip file they shared over an email. This is important to know because the monolith code for Shopify has never been rewritten, so they put a lot of care into keeping it working. He talks about some of the techniques Shopify uses to avoid splitting into microservices when scaling their organization and how the multiple instances of the database is structured and managed from an opps point of view. He talks about what aspects of Shopify are open source and the approach to the architecture of the background jobs system.The panel discusses what should be done if you want to scale your project and move away from background jobs. Kir talks about what criteria his company uses to determine what moves to a background job and when it is too much to background something. The show finishes with Kir sharing some of his favorite tips, tricks, and approaches he’s used at Shopify. Links

• Heroku
• Digital Ocean
• Sidekiq
• Shopify job iteration
• Redis
• PostgreSQL
• Resque
• Strace 
• RB Spy
• RB Trace
• New Relic
• Data Dog
• Fat Free CRM

Follow DevChat on Facebook and Twitter PicksNate Hopkins:

• Open source
• Cats (Maine Coon and Russian Blue)

Charles Max Wood:

• 75 Hard challenge

Kirill Shatrov: 

• Ruby Hack Challenge
• Follow Kirill Shatrov @kirshatrov on Twitter and @kirs on Github

Special Guest: Kir Shatrov.

Advertising Inquiries: https://redcircle.com/brands

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.

Sponsors

• Sentry use code “devchat” for $100 credit
• Cloud 66 - Pain Free Rails Deployments Try Cloud 66 Rails for FREE & get $66 free credits with promo code RubyRogues
• RedisGreen

Panel

• Charles Max Wood
• Dave Kimura
• Andrew Mason

Episode SummaryToday’s topic is the Stimulus library. Stimulus is actually a JavaScript framework and library, but it’s also built by Basecamp, so it works really well in Rails. There is a demand for rich client side interactions, and Stimulus fills in some of the gaps. The panelists talk about some of their experiences with Stimulus versus jQuery. They talk about different use cases for Stimulus, how it works, and how it can help your project. One of the main draws of Stimulus is that the amount of code needed to implement a feature with Stimulus is very small comparatively. Also, frameworks like React weren’t created for Rails, and so adding React to a Rails application can be quite painful. Stimulus follows the Rails philosophy to keep things simple and unobtrusive, so if you ever found that Stimulus was not a right fit for your application, extracting it would be a major overhaul.Links

• Stimulus
• Cocoon
• React
• Gatsby
• Capybara
• Cypress
• Stimulus controllers
• Building Something Real
• Drifting Ruby episode
• John Beatty Stimulus tutorial
• jQuery

Follow DevChat on Facebook and Twitter PicksDave Kimura:

• Raspberry Pie 4

Charles Max Wood:

• Women’s World Cup
• Fox Sports

Andrew Mason:

• Surfing
• Stimulus workshop at RailsConf

 

Advertising Inquiries: https://redcircle.com/brands

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.

Sponsors

• Sentry use code “devchat” for $100 credit
• Triplebyte offers $1000 signing bonus
• RedisGreen

Panel

• Charles Max Wood
• Dave Kimura
• Andrew Mason

With Special Guest: Steve PeakEpisode Summary Today’s guest Steve Peak has been an entrepreneur and developer for a decade specializing in building tools. He built the company Codecov, one of the top performers in the github ecosystem. His next project is Storyscript, first and only top level programming language that focuses on business logic. The panel begins by discussing what a microservice is and what makes a good one. One of the difficulties with microservices that there is no standardization, and that’s where microservice.guide can help.  The panel talks about some of the issues of having too many microservices and Steve offers Possible solutions. Steve delves into some of the abilities of Story Script in stringing together multiple services in different languages and how it can simplify things. They talk about if it’s possible to have too many microservices and when does a microservice become a monolith microservice. They talk about the possibility of inflating the production environment with unneeded memory by using microservices. Steve offers advice on how to go from poor decisions to responsible decisions when using microservices, how Storyscript can help when multiple microservices are in use, and where he sees the industry heading. Links

• Storyscript
• Slack
• Microservice.guide
• Kubernetes
• Stripe API
• Hub.storyscript.io
• Json 
• Machine Box
• Docker
• Kafka
• Kong
• Devise 

Follow DevChat on Facebook and Twitter PicksDave Kimura:

• Sidecar from macOS Catalina

Charles Max Wood:

• 2 episodes a week of JavaScript Jabber
• Netlify CMS

Steve Peak:

• Follow Steve on Twitter @iopeak

Special Guest: Steve Peak.

Advertising Inquiries: https://redcircle.com/brands

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.

Sponsors

• Sentry use code “devchat” for $100 credit
• Triplebyte offers $1000 signing bonus
• RedisGreen

Panel

• Charles Max Wood
• David Kimura
• Nate Hopkins
• Andrew Mason

With Special Guest: Olivier LacanEpisode SummaryOlivier Lacan joins the panel again. He currently works for Pluralsight. Today they are talking about the spectrum of creating a Rails app, or any app, from the birth of the idea to the death of the project. They stress the importance of planning for updates. Olivier talks about his experience in maintaining Code School, which has now been incorporated into Pluralsight. David also shares his experience with the life and death of a project. They talk about technical debt and the trouble that it can create, and the importance of making your Rails application maintainable. Olivier talks about his experience when Code School was acquired by Pluralsight. The panel discusses the inevitability of the end of an application and different ways of managing company integration. They talk about ways to plan for shutting down a project. One of the best ways to make integration easier is to clean up your code and always be considering what data needs to be kept and what can be truncated. They discuss some of the issues around storing customer data and respecting individual privacy. The panel talks more about sunsetting, or the ending of an app. People often think that shutting down an app doesn’t have any impact, but it is important to give customers time to adjust to change, as Olivier found out with Code School. Dave talks about different reactions that one could have when change happens. The panel talks about some of the emotional implications of having to destroy something that you’ve worked hard on for a long time. Ultimately, your project isn’t where you should put your self-worth, because projects will come to an end. When things do end, it’s important to look back at where you’ve come from and the impact that you’ve had on people. Links

• Lambda
• Dependabot
• Peoplecode
• Pluralsight
• Trackable
• Paranoia
• Discard 
• Rails for Zombies

Follow DevChat on Facebook and Twitter PicksAndrew Mason:

• Wild Sardines from Wild Planet

David Kimura:

• 5K screens from LG

Charles Max Wood:

• Pluralsight
• New Show: Adventures in DevOps
• Butcher Box
• Hotels.com 

Nate Hopkins:

• Keynote speech from RailsConf

Olivier Lacan:

• Oatley
• Horizonzerowaste.com 
• Adobe Lightroom CC

Special Guest: Olivier Lacan.

Advertising Inquiries: https://redcircle.com/brands

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.