Ruby Rogues

Charles M Wood
undefined
Jul 9, 2019 • 33min

RR 420: Stimulus

SponsorsSentry 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 RedisGreenPanelCharles Max WoodDave KimuraAndrew MasonEpisode 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.LinksStimulusCocoonReactGatsbyCapybaraCypressStimulus controllersBuilding Something RealDrifting Ruby episodeJohn Beatty Stimulus tutorialjQuery Follow DevChat on Facebook and Twitter PicksDave Kimura:Raspberry Pie 4Charles Max Wood:Women’s World CupFox SportsAndrew Mason:SurfingStimulus workshop at RailsConf  Advertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.
undefined
Jul 2, 2019 • 47min

RR 419: Microservices and Storyscript with Steve Peak

SponsorsSentry use code “devchat” for $100 credit Triplebyte offers $1000 signing bonus RedisGreenPanelCharles Max WoodDave KimuraAndrew MasonWith 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. LinksStoryscriptSlackMicroservice.guideKubernetesStripe APIHub.storyscript.ioJson Machine BoxDockerKafkaKongDevise  Follow DevChat on Facebook and Twitter PicksDave Kimura:Sidecar from macOS CatalinaCharles Max Wood:2 episodes a week of JavaScript JabberNetlify CMSSteve Peak:Follow Steve on Twitter @iopeakSpecial Guest: Steve Peak. Advertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.
undefined
Jun 25, 2019 • 1h 10min

RR 418: The Life and Death of a Rails App with Olivier Lacan

SponsorsSentry use code “devchat” for $100 credit Triplebyte offers $1000 signing bonus RedisGreenPanelCharles Max WoodDavid KimuraNate HopkinsAndrew MasonWith 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. LinksLambdaDependabotPeoplecodePluralsightTrackableParanoiaDiscard  Rails for Zombies Follow DevChat on Facebook and Twitter PicksAndrew Mason:Wild Sardines from Wild PlanetDavid Kimura:5K screens from LGCharles Max Wood:PluralsightNew Show: Adventures in DevOpsButcher BoxHotels.com  Nate Hopkins:Keynote speech from RailsConfOlivier Lacan:OatleyHorizonzerowaste.com  Adobe Lightroom CCSpecial Guest: Olivier Lacan. Advertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.
undefined
Jun 18, 2019 • 17min

RR 417: The Devchat.tv Mission and Journey with Charles Max Wood

SponsorsSentry use the code “devchat” for 2 months free on Sentry small planTriplebyte offers a $1000 signing bonusRedisGreenCacheflyPanelCharles Max WoodEpisode SummaryCharles talks about his journey as a podcaster and his mission with Devchat.tv. Devchat.tv  is designed to home podcasts that speak to all developer communities. Charles also plans Devchat.tv to host shows for technologies that are on the verge of a breakthrough and will be a lot more widely available in the near future such as Artificial Intelligence (AI), Internet of Things (IoT), Virtual Reality (VR) and Augmented Reality (AR). There are new shows being added continuously to reach out to new communities, some examples of which are: a Data Science show, a DevOps show and an Open Source show.As a kid, Charles would record his own shows on a tape recorder. He was always interested in technology. While studying Computer Engineering at Brigham Young University, he worked in the University's Operations Center. Upon graduation, he started working for Mozy where he was introduced to podcasts. Listen to the show to find out the rest of Charles' story, some of the lessons and tips he learned throughout his journey and the evolution of the shows on Devchat.tv.If there isn't a show for your community and you would like there one to be, reach out to Charles. Also if there was a podcast about a programming related subject that ended abruptly and you would like it to continue, reach out to Charles. Devchat.tv would like to host these podcasts.LinksCharles' TwitterEverywhereJS JavaScript CommunityEverywhereRB Ruby and Rails CommunityFind Your Dream Job As A DeveloperDevchat.tv on FacebookDevchat.tvPicksEverywhereJS JavaScript CommunityEverywhereRB Ruby and Rails CommunityNetlifyEleventyhttps://github.com/cmaxw/devchat-eleventyAdvertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.
undefined
Jun 11, 2019 • 50min

RR 416: The Difference between Devise and Warden with Leonardo Tegon

SponsorsSentry use code “devchat” for $100 credit Triplebyte offers $1000 signing bonus Cloud 66 - Pain Free Rails Deployments Try Cloud 66 Rails for FREE & get $66 free credits with promo code RubyRogues PanelCharles Max WoodDavid KimuraDavid RichardsAndrew MasonWith Special Guest: Leonardo TegonEpisode Summary Leonardo Tegon is a software developer at Plataformatec, the company that created Devise. Leonardo talks about how he ended up at Plataformatec and shares a little bit about the talk he gave about alternative authentication methods. He talks about the difference between Devise and Warden. Some of the panelists have had some issues with cache warming in Warden, and  Leonardo shares ways to get around it. They talk about authentication strategies used in Warden and Devise and different strategies that tap into hardware.  Leonardo talks about some of the features coming to Devise, although their primary focus is on maintenance. He talks about the work that goes into such a long-standing project, especially concerning maintaining the integrity of the code but also allowing for progress. They talk about some of their favorite features of Devise. Devise is easy to set up and very functional, but also intimidating. When a library is so big and does so much, it has to make some assumptions. Leonardo talks about how they decide what goes into the library at this point and how easy is it for new maintainers to contribute to the project. Leonardo ultimately wants to make it easier for people to jump in.LinksDeviseWardenCache warmingMagic email linkWrapperWebAuthInFollow Leonardo on Twitter and GitHub @tegonl Follow DevChat on Facebook and Twitter PicksLeonardo Tegon:Teach by learning, lead by teaching by Beth SajevoFluent Forever: How to Learn Any Language Fast And Never Forget It by Gabriel Wyner Andrew Mason:Rethinking the View Layer with Components by Joel HoxleyRepo for the talkDavid Kimura:Water pressure gauge testerOther World Computing RAMCharles Max Wood:RepurposeNew shows coming: Adventures in DevOps, Data Therapy, Sustain Our Software, Adventures in Block Chain, Adventures in .netDavid Richards:CalTopoSpecial Guest: Leonardo Tegon. Advertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.
undefined
Jun 4, 2019 • 1h 16min

RR 415: Code Free Developer Interview with Pete Holiday

SponsorsSentry use code “devchat” for $100 creditTriplebyte offers $1000 signing bonusCloud 66 - Pain Free Rails Deployments Try Cloud 66 Rails for FREE & get $66 free credits with promo code RubyRogues PanelCharles Max WoodDave KimuraAndrew MasonNate Hopkins With Special Guest: Pete HolidayEpisode SummarySpecial Guest Pete Holiday is the director of engineering at a company called Samsara and specializes interviewing software engineers. The panel begins by talking about some of the trends they see in tech interviews, specifically the move towards code-heavy interviews. Pete does not think take home tests accurately simulate a work environment, and shares his preferred technique. The panel discusses the most important things to look for in an interview, such as how good of a fit they will be with the company culture. They discuss the importance of hiring junior developers, some of the ethics of internships and compensating for take home projects.They turn the conversation to interview questions and what should be asked to evaluate a candidate. They go through some potential questions and methods for coming up for interview questions. Pete shares the interview process he designed. The panel talks about the importance of resumes. On the subject of resumes, they discuss how to avoid unconscious bias and maintain diversity in the workplace. They give a few tips for people being interviewed, such as doing interviews to keep you skills fresh, even if you aren’t necessarily looking for a job.  The show ends with the panel recapping the most important points of their discussion. They emphasize that as the interviewer, it is imperative that you know what you want and are looking for in a new hire. When you’re doing the interviews, tech skills are important but the fit with the company is more important, and it’s your job to get all of the right information out of the candidate. People interviewing are encouraged to proofread their resumes, ask questions to find out if the company is a right fit, and not be afraid to ask for some accommodations in an interview. Links Bootstrap SassDevisePunditFriendly IDGlassdoor Follow DevChat on [Facebook](https://www.facebook.com/DevChattv/? tn =%2Cd%2CP-R&eid=ARDBDrBnK71PDmx_8gE_IeIEo5SnM7cyzylVBjAwfaOo1ck_6q3GXuRBfaUQZaWVvFGyEVjrhDwnS_tV) and TwitterPicksAndrew Mason:Rails ERD gem Dave Kimura: Plant UMLDrill propeller Charles Max Wood: Find Your Dream Coder JobEverywhereRB Nate Hopkins: HamiltonHamilton Lottery app Pete Holiday: Follow Pete on TwitterThe Manager’s PathHow F*cked Up is Your ManagementJennifer Tu on ConfreaksSpecial Guest: Pete Holiday. Advertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.
undefined
May 28, 2019 • 55min

RR 414: Docker Talk

SponsorsSentry use code “devchat” for $100 credit Triplebyte offers $1000 signing bonus Cloud 66 - Pain Free Rails Deployments Try Cloud 66 Rails for FREE & get $66 free credits with promo code RubyRogues PanelCharles Max WoodAndrew MasonDave KimuraDavid RichardsEpisode SummaryToday the panel is talking about the many applications of Docker. They talk about where Docker fits into the development lifestyle and what kind of applications Docker can help with. Dave goes over some of the some of the Docker terminology, how to set up some basic scenarios, and some of the difficulties often encountered by first time users. They talk about how to make sure you’re putting together a Docker file correctly.The panel agrees that Docker had a different workflow from other systems, and discuss some of the tradeoffs of using docker. They mention some specific use cases for docker and what it’s like to migrate to Docker. Dave cautions listeners that databases needs to exist outside of Docker or Kubernetes. Dave and Andrew argue whether or not Docker belongs in the developer environment.The panel discusses ways to maintain productivity when introducing Docker and give some advice to programmers who are new to using Docker. They talk about cases where using Docker can be very helpful. They wrap up by talking about how to get started with Docker in your CI/CD and how to run tests with Docker.LinksDockerMicroservicesKubernetesISO fileDocker imagesBundlerUbuntuRed HatAlpine LinuxSinatraPodwrenchSidekickForemanCI/CDAWSAzureDigitalOceanElastic BeanstalkGoogle CloudRedisCloud Native Development Follow DevChat on Facebook and Twitter PicksAndrew Mason:Rails Flip FlopDave Kimura:Cloud Native DevelopmentDewalt Flexvolt circular sawCharles Max Wood:Everywhere RBDavid Richards:Warren Buffet's letters to his shareholdersAdvertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.
undefined
May 21, 2019 • 1h 7min

RR 413: When Your Tools Interrupt Your Coding Process

SponsorsSentry use code “devchat” for $100 credit Triplebyte offers $1000 signing bonus Cloud 66 - Pain Free Rails Deployments Try Cloud 66 Rails for FREE & get $66 free credits with promo code RubyRogues PanelCharles Max WoodDavid RichardsAndrew MasonNate HopkinsDavid KimuraEpisode SummaryIn this episode of Ruby Rogues, the panel discusses how having too many tools in your code can make things more complicated. They talk about if the processes and tools that hurt productivity should be taken out. They question if outdated but harmless tools should be updated for newer ones that have more functions.They discuss the difficulty with adopting new tools since the setup process takes time away from production. They each talk about their different editor setups. The necessity of all this different tools is questioned. They note that there is a trend to take a good thing that solved a real-world problem and introduce it into places that it doesn’t need to be, making development more complex. It is advised that programmers focus on shipping an application rather than just writing the code in order to simplify tooling. They discuss whether backend as a service systems are part of the problem. They advise tech companies to consider if they are ever going to sell or migrate when considering a new tool. The panel talks about if it’s possible to end up fighting against the tools that have always been used rather than infrastructure or coding tools. They conclude by agreeing that it is important to be candid within companies to prevent this overtooling   LinksVimEmaxHomebrewGit RepoPaperspaceDockerVS CodeCoderStackBlitzCodeSandboxJupiterKubernetesGraphiteStatsD Follow DevChat on Facebook and Twitter PicksNate Hopkins:Screen sharing with Mac messagingThe Band of BrothersAndrew Mason:CakebrewDavid Kimura:Brew Bundle DumpSuperstoreCharles Max Wood:TSA Pre CheckClearDavid Richards:Great at Work: How Top Performers Work Less and Achieve More by Morten T. Hansen Advertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.
undefined
May 14, 2019 • 50min

RR 412: Asynchronous Jobs on Client Side and Server Side

SponsorsSentry use the code “devchat” for 2 months free on Sentry small planTriplebyte offers a $1000 signing bonusRedisGreenCacheflyPanelDave KimuraAndrew MasonSummaryDave Kimura starts the episode by defining asynchronous jobs; he and Andrew Mason discuss the differences between server side and client side asynchronous jobs. They discuss use cases and address scenarios for which asynchronous jobs can be used for. Dave answers Andrew’s questions about tools, gems, and libraries. Dave expresses his love for Active job and advocates for Gitlab. The panel discusses overuse and misuse of asynchronous jobs and times when it is better not to use this tool. Dave shares what he thinks makes a good microservice; he and Andrew discuss where people go wrong with microservices.Links https://github.com/javan/wheneverhttps://github.com/moove-it/sidekiq-schedulerhttps://github.com/ondrejbartas/sidekiq-cronhttps://github.com/renderedtext/render_asynchttps://edgeguides.rubyonrails.org/active_job_basics.htmlhttps://www.facebook.com/RubyRogueshttps://twitter.com/rubyroguesPicksAndrew Mason:https://github.com/igorkasyanchuk/rails_pdfDave Kimura:Levi’s walletAdvertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.
undefined
May 7, 2019 • 56min

RR 411: What causes Ruby memory bloat? with Hongli Lai

SponsorsSentry use the code “devchat” for 2 months free on Sentry small planTriplebyte offers a $1000 signing bonusRedisGreenCacheflyPanelCharles Max WoodDave KimuraEric BerryJoined by Special Guest: Hongli LaiSummaryEric Berry starts by sharing how Phusion and Phusion passenger changed his career and thanks Hongli Lai for his work. Hongli talks about where Phusion is now and shares what's new with passenger 6. The panel compares passenger and puma and Hongli explains why passenger is the better choice. The panel wonders about deployment strategies and Hongli shares what he has seen done with Passenger.Hongli discusses the article he wrote about memory bloat. He starts by explaining why he wrote the article. The panel discusses what causes memory bloat and how to identify memory bloat versus memory leaks. Hongli explains how the system memory allocator works and why people are using Jemalloc instead. The panel discusses Jemalloc and wonders why Ruby doesn’t adopt Jemalloc. Hongli shares his magic solution for solving the memory bloat problem and other tips for managing memory.Linkshttps://www.phusionpassenger.com/https://github.com/phusion/passenger-dockerhttps://devchat.tv/ruby-rogues/rr-403-rails-needs-active-deployment-with-stefan-wintermeyer/  https://blog.phusion.nl/2019/03/14/what-causes-ruby-memory-bloat/https://www.joyfulbikeshedding.com/blog/2019-03-14-what-causes-ruby-memory-bloat.htmlhttps://www.joyfulbikeshedding.com/blog/2019-03-29-the-status-of-ruby-memory-trimming-and-how-you-can-help-with-testing.htmlhttps://en.wikipedia.org/wiki/Lars_Bak_(computer_programmer)https://twitter.com/honglilaihttps://www.facebook.com/RubyRogueshttps://twitter.com/rubyroguesPicksDave Kimura:LEGO Marvel Super Heroes Avengers: Infinity War The Hulkbuster Smash-Up 76104 Building Kit (375 Piece)Samsonite Explore Eco 2-Piece Softside SetHongli Lai: https://www.blinkist.com/https://euruko2019.org/Eric Berry:Codefund.iohttps://devchat.tv/ruby-rogues/Charles Max Wood:Open source sustainability podcasthttps://podwrench.com/Podcast assembly linePodcast Laboratoryhttps://mybuild.techcommunity.microsoft.com/home#top-anchorOz conhttps://elixirconf.com/2019https://finconexpo.com/https://podcastmovement.com/https://go.2000books.com/Special Guest: Hongli Lai . Advertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/ruby-rogues--6102073/support.

The AI-powered Podcast Player

Save insights by tapping your headphones, chat with episodes, discover the best highlights - and more!
App store bannerPlay store banner
Get the app