RailsConf 2024 Countdown — Behind the Scenes with Kevin Murphy

In this episode of 'Ruby For All', hosts Andrew and Julie welcome guest Kevin Murphy, Software Developer at Pubmark and member of the RailsConf program committee. The discussion kicks off with Andrew and Julie catching up, then transitions into an in-depth conversation about the RailsConf planning process. Kevin and Julie, the Speaker Liaison, share insights into the workings of the program committee, the selection criteria for conference talks, and the challenges and rewards of organizing RailsConf. Additionally, Kevin elaborates on his role in the committee, the theme for this year's conference, and his goals for impact, and Julie looks forward to supporting speakers and managing workshops. The episode emphasizes the importance of volunteer contributions to the success of RailsConf and encourages attendees to express their gratitude to the organizers, and to go check out all the details at RailsConf.org and buy your tickets now!  Press download to hear more! [00:00:15] Andrew and Julie catch up, Andrew overslept after finishing a project, Julie was up late watching videos, and Andrew recommends the show “Invincible.”[00:02:22] Kevin introduces himself and explains why he likes working with Ruby on Rails. [00:03:37] Kevin discusses the role of the RailsConf program committee, explains their responsibilities, including reviewing proposals and scheduling talks. [00:05:10] We learn what Kevin looks for in a conference talk proposal, emphasizing relevance to the theme and potential audience interest. Julie shares her perspective on reviewing proposals, considering both her emotional response and broader interests. [00:07:38] Kevin shares his first experience on the committee and discusses the time commitment involved and talks about the fairness of reviewing all proposals at once after the submission deadline. [00:11:03] Julie expresses her difficulty with the proposal reviewing process, suggesting that a grading scale might have been more effective for her. Kevin reflects on the surprises of the reviewing process and the difference between his perceptions and the rankings generated by the review system. [00:12:41] Julie adds that the difficulty in having to reject good talks due to overlapping topics or because they might fit better at another conference like RubyConf,[00:13:09] Andrew asks if the proposers receive feedback on why their talks may be more suited for RubyConf, and Kevin explains that if they ask, Ruby Central will make their best effort to provide it.[00:14:47] What’s been the most rewarding part of this experience for Kevin and Julie? Kevin finds the opportunity to impact the community through the program committee rewarding, and Julie says she’s waiting to see the full impact of her role as Speaker Liaison, which involves making speakers feel supported and pairing them with mentors.[00:16:24] Kevin and Julie both explain how they were invited to join the program committee by Ufuk, who’s a member of the Ruby Central board, and Julie brings up a previous episode with Kevin on conference speaking. [00:17:52] Andrew asks what Kevin and Julie think the hardest part of will be being on the program committee at the conference. Kevin hopes his committee responsibilities won’t impact his conference experience too much, and Julie anticipates the challenge of not having as much personal downtime during the conference due to her responsibilities. [00:19:41] Kevin reflects on the subjective nature of selecting talks and how different perceptions among committee members can affect decisions. He emphasizes that rejected talks are not necessarily of poor quality but may not fit due to other reasons.[00:21:02] Julie inquires about Kevin’s role on the program committee and how he feels so far. His role involves scheduling and organizing accepted talks and workshops, reviewing and giving feedback on rejected proposals, and just being available.[00:22:00] Julie’s role is Speaker Liaison, helping speakers with their needs and feeling special, and helping with scheduling workshops. Kevin clarifies the concept of tracks at conferences and since there aren’t any this year, the goal is to align all talks with the overall theme of building with Rails. Julie mentions a blog post written by Kevin about the absence of tracks at RailsConf.[00:23:28] Kevin shares his aspirations for his impact on RailsConf: ensuring a safe, educational experience for attendees, seeing first-time speakers succeed, and enjoying the mentorship process. Julie describes her motivation for becoming a Speaker Liaison: to provide a supportive experience for speakers. [00:25:03] RailsConf is happening in Detroit, May 7-9. Kevin expresses his excitement for various aspects, including the strong program and meeting friends, and urges everyone to visit RailsConf.org, check the schedule, and get tickets. [00:28:19] Find out where you can follow Kevin online. Panelists:Andrew MasonJulie JGuest:Kevin MurphySponsors:HoneybadgerGoRailsLinks:Andrew Mason X/TwitterAndrew Mason WebsiteJulie J. X/TwitterJulie J. WebsiteKevin Murphy WebsitePubmarkRuby for All Podcast-Episode 50: The Art of Conference Speaking with Kevin MurphyTracks Not At RailsConf 2024-by Kevin MurphyRailsConf-Detroit May 7-9, 2024RailsConf ScheduleRailsConf SpeakersInvincible: Season 2 (Amazon Prime) (00:00) - Introduction and Casual Catch-Up (02:22) - Guest Introduction: Kevin Murphy on Ruby and Rails (03:37) - Inside the RailsConf Program Committee: Roles and Responsibilities (05:10) - What Makes a Great Conference Talk? Selection Criteria Explored (07:38) - Behind the Scenes: Reviewing Conference Proposals (11:03) - Challenges in Proposal Review: Fairness and Surprises (12:41) - Rejection Reasons: When Good Talks Don’t Make the Cut (13:09) - Feedback for Rejected Proposals: Bridging to RubyConf (14:47) - Rewarding Aspects of Program Committee Work (16:24) - Joining the Program Committee: Invitations and Insights (17:52) - Preparing for RailsConf: Expectations and Challenges (19:41) - The Subjectivity of Talk Selection: A Committee Perspective (21:02) - Roles Deep Dive: Organizing Talks and Supporting Speakers (23:28) - Goals and Aspirations for RailsConf Impact (25:03) - RailsConf 2023 Preview: What to Expect in Detroit <...

On this episode of "Ruby for All," hosts Andrew and Julie catch up with Julie returning after a bout of strep throat, and then share their excitement about having guest Bobbilee Hartman, the founder of Rails Camp West USA, joining them.  Bobbilee discusses the origins of Rails Camp, its unique unplugged experience, and the variety of activities attendees can engage in, from coding retreats to outdoor adventures like hiking zip-lining, and kayaking.  She also shares the logistics of organizing such an event, the sense of community it fosters among tech professionals, and how it differentiates from traditional conferences by offering a more personalized, inclusive, and memorable experience. The episode also touches on the challenges and joys of planning such an event, future locations, and the benefits of sponsoring, Press download to hear more! [00:00:39] Bobbilee explains her history with tech community events and Rails community, mentioning her shift to developer relations, the start of Rails Camp, and her personal interests.[00:01:27] Andrew expresses his long-standing interest in Rail camp since college, and Bobbilee details the Rails Camp US experience. [00:08:01] Bobbilee talks about the evolution of Rails Camp, its sponsorship, and the organization, including the scholarship program, location changes, food arrangements, and personal outreach for ticket sales and promoting the event. [00:13:19] Andrew inquires about the unique benefits of Rails Camp’s style of conference. Bobbilee discusses the small size of Rails Camp, how it caters to different communication styles, and facilitates community through organic interactions rather than traditional networking.  [00:15:35] Addressing Julie’s concerns about attending unfamiliar events, Bobbilee emphasizes that most attendees come alone, and the event’s structure in small groups makes it welcoming for newcomers. She mentions various options for lodging and activities, accommodating different comfort levels and financial situations. [00:17:56] Bobbilee explains the intense planning involved in Rails Camp, finding new venues each year, working with new partners, and sourcing local items for goodie bags. [00:19:55] Bobbilee shares her personal rewards from organizing Rails Camp, such as staying connected with the tech community, helping sponsors, and maintaining relationships as life becomes busier. [00:22:17] Andrew talks about his own experiences with big conferences and appreciates the small group activities and inclusiveness at Rails Camp. Bobbilee explains how meals and activities are organized to ensure inclusivity and engagement, and she details her vigilance in ensuring all participants feel included. [00:24:20] We learn that Rails Camp is being held in Cascade, Idaho this year. The venue is a top-rated summer camp with numerous activities, located on a private lake, and Bobbilee expresses a desire to include whitewater rafting as an activity and is seeking a sponsor if anyone is interested. [00:27:13] Julie is curious about the venue selection process, and Bobbilee explains that she uses a combination of her saved lists, summer camp directories, and Google Maps to ensure venues are in suitable locations. [00:31:46] Bobbilee leaves listeners with the idea that Rails Camp is a simple, all-inclusive experience for those seeking an alternative to big conferences, emphasizing easy logistics and a variety of activities available. [00:33:26] The conversation wraps up with Bobbilee discussing sponsorship opportunities with various benefits attached to different levels of support. Panelists:Andrew MasonJulie J.Guest:Bobbilee HartmanSponsors:HoneybadgerGoRailsLinks:Andrew Mason X/TwitterAndrew Mason WebsiteJulie J. X/TwitterJulie J. WebsiteBobbilee Hartman WebsiteBobbilee Hartman X/TwitterBobbilee Hartman LinkedInRails Camp USA X/TwitterRails Camp West Rails Camp West Registration (00:00) - Bobbilee's Tech Community Journey (01:27) - Rails Camp US Experience Overview (08:01) - Evolution and Organization of Rails Camp (13:19) - Unique Benefits of Rails Camp (15:35) - Making Rails Camp Welcoming for Newcomers (17:56) - Intense Planning and Logistics of Rails Camp (19:55) - Personal Rewards of Organizing Rails Camp (22:17) - Appreciation for Rails Camp's Inclusiveness (24:20) - Venue Details for Rails Camp 2024 (27:13) - Venue Selection Process (31:46) - Rails Camp: A Simple, All-Inclusive Experience (33:26) - Sponsorship Opportunities Wrap-Up

In this episode of 'Ruby for All', host Andrew is joined by guest Drew Bragg to talk about the ins and outs of the Sin City Ruby conference. Drew provides a comprehensive breakdown of the event, highlighting the mix of technical and lifestyle talks presented, the benefits of regional conferences for building community and networking, and the unique atmosphere that smaller, regional conferences offer. Additionally, the episode covers the importance of Ruby and Rails in current technology, personal experiences with speaking and organizing community events, and thoughts on the future of regional programming conferences. The conversation concludes with Drew emphasizing the value of these gatherings in strengthening the Ruby community and encouraging participation in future events. Hit download now to hear more! [00:00:29] Drew introduces himself and tells us what he does, and Andrew explains why he didn’t attend the conference and what he did instead. [00:02:45] Drew talks about his game show-style talk he gave, which is interactive and challenges attendees’ knowledge of esoteric Ruby syntax. [00:05:31] Andrew brings up seeing Jason’s talk and the attendee makeup at Sin City Ruby, noting many new faces and speculating on the impact of regional conferences bringing in local attendees who might not travel to larger conferences. [00:07:51] Andrew asks about the speakers’ dinner, which Drew describes as a communal eating experience. [00:11:42] Drew explains the first day began with a forced socialization event which Drew found more pleasant in a smaller conference setting.[00:12:44] Andrew inquires about the style of talks at Sin City Ruby, wondering if there was a particular focus. Drew describes the conference as having a mix of topics with some technical, business-related, and lifestyle-oriented tasks related to Ruby and Rails. [00:14:01] Drew mentions enjoying Stéfanni Brasil’s talk, Jason’s live coding dressed as Elvis was very entertaining and hilarious, and Obie Fernandez’s closing keynote offering a different perspective on AI’s impact on the industry.[00:15:40] Regarding lack of recordings at the conference, Drew sees benefits form a speaker’s perspective, and acknowledges that recordings can be valuable for review and as a portfolio asset. [00:18:41] Drew prefers speaking at smaller conferences for the close-knit atmosphere and better audience interaction but acknowledges that larger conferences have their own advantages.[00:21:12] Andrew asks what went well with this conference, and Drew explains he appreciates the laid-back nature and mentioned the relaxed atmosphere set by organizer Jason Swett made the event feel more like a meetup.[00:24:23] Drew shares that he didn’t find any aspect of the conference that didn’t go well and praises the simplicity of regional conferences like Sin City Ruby.  He emphasizes the convenience of Vegas as a conference location. [00:25:40] Discussing Vegas itself, both Andrew and Drew enjoyed visiting Hoover Dam and the overall experience of connecting with people with shared interests in Ruby.  They also touch on having fun people-watching and the vibrant environment of “Old Vegas.”[00:27:55] Drew’s takeaway from the conference is the reaffirmation of Ruby and Rails’ potential and expresses enthusiasm for the talks he attended, singling out Tom Rossi’s as particularly energetic and engaging. [00:31:01] Drew promotes the idea of attending or organizing local conferences for their intimate nature and the connections they foster. He gives a shout-out to several upcoming Ruby conferences. [00:32:05] Find out where you can follow Drew and his podcast online.Panelist:Andrew MasonGuest:Drew BraggSponsors:GoRailsHoneybadgerLinks:Andrew Mason X/TwitterAndrew Mason WebsiteJulie J. X/TwitterJulie J. WebsiteDrew Bragg X/TwitterDrew Bragg MastodonDrew Bragg WebsiteCode and the Coders who Code it Podcast Sin City Ruby 2024 (00:29) - Sin City Ruby: Drew’s Introduction (02:45) - Game Show Talk: Testing Ruby Knowledge (05:31) - New Faces at Sin City Ruby (07:51) - Speakers' Dinner: A Communal Experience (11:42) - Forced Socialization: Networking Made Easy (12:44) - Talk Styles: Technical to Lifestyle (14:01) - Highlight Talks: From Elvis to AI (15:40) - The No-Recording Debate (18:41) - Small vs. Large: Conference Dynamics (21:12) - What Made Sin City Ruby Shine (24:23) - The Simplicity of Regional Conferences (25:40) - Vegas Adventures: Beyond the Conference (27:55) - Ruby’s Vibrant Future and Energetic Talks (31:01) - The Value of Local Conferences (32:05) - Following Drew: Online and Beyond

In this episode of "Ruby for All," hosts Andrew and Julie take us through a journey of debugging, from dealing with weather-induced moods to squashing tricky bugs in their code. They touch on the challenges of debugging without audio guidance, leveraging logs for troubleshooting, and the logical approach to handling errors in Ruby or JavaScript. They dive into the variations of different debugging tools, such as Pry and the Rails Logger, and the complexities of transitioning to new debugging gems. Andrew recounts a perplexing bug only replicable in production and details his process and concluding the issue. As they navigate the intricacies of problem-solving, they contemplate the worth of fixing minor bugs versus prioritizing major ones, drawing on real-life examples from their experiences. Andrew wraps up with a reminder of the importance of teamwork in debugging, while they both acknowledge the reality that sometimes, a bug might just remain unfixed. Join them as they share insights and laughter, reminding us of the human element in the world of code. [00:00:54] Andrew describes the bug issue he had and the difficulties of debugging it without audio in the screen recording, and Julie shares her own debugging challenges on her new team. [00:02:00] Let’s talk about debugging, as Andrew explains different types of bugs and shares his process for understanding and reproducing bugs. Julie emphasizes the importance of understanding the product and the expected behavior to replicate and debug issues. [00:03:31] Andrew describes his approach to getting unstuck during debugging, which includes revisiting the problem statement and using logs to trace the issue. [00:05:14] Andrew asks Julie if she can replicate her bug in production and suggests using logs for troubleshooting. Julie talks about her approach to errors, which differs as she doesn’t typically see the red Rails error page in her work. They discuss how to deal with JavaScript errors and the importance of reading error messages. [00:08:57] Julie inquires why some developers may overlook details in error messages, and Andrew suggest that assumptions and a form of panic might play roles and discusses when he’s more likely to Google error messages, especially regarding dependencies. [00:13:22] Andrew explains why he prefers using the ‘Rails Logger’ over ‘puts’ for debugging. He also mentions using Overmind and tmux for viewing Rails logs.[00:14:39] Julie draws a parallel between ‘puts’ debugging and JavaScript’s console.log debugging. Andrew confirms they are similar, and he shares his transition from using Pry to the official debug gem and the difficulty of changing old habits. [00:16:30] Andrew clarifies that binding.irb now uses the debug gem by default in Ruby 3, he discusses the usefulness of Pry’s context-switching feature, and he outlines additional steps for effective debugging. [00:19:52] There’s a conversation on using git for tracking code changes and git-bisect for isolating commits that caused issues, and questioning assumptions, reading documentation, and getting a second opinion or sleeping on the problem. [00:23:17] Andrew discusses the mindset required for effective debugging: patience, persistence, and the willingness to step away and return to a problem. Julie describes a very specific bug affecting a small number of users questioning with her manager whether it’s worth the effort to fix it. [00:25:43] Back to Andrew’s story about a bug that he couldn’t replicate in development, but could in production, and he details his process and realization that it was a display issue in the front-end. [00:31:09] Julie relates to Andrew’s difficulty in replication bugs in development and suspects filtering differences in production. Andrew suggests troubleshooting methods for errors related to data discrepancies. [00:33:11] Andrew shares a tip about using data to back up arguments when trying to convince others during decision-making, and Julie recounts realizing the low impact of the bug she’s working on and it it’s worth the effort. Panelists:Andrew MasonJulie J.Sponsors:HoneybadgerGoRailsLinks:Andrew Mason X/TwitterAndrew Mason WebsiteJulie J. X/TwitterJulie J. WebsiteOvermindtmuxIRBgit/git-bisect (00:54) - Debugging Dilemmas: Screen Recordings Without Sound (02:00) - The Debugging Process: Understanding & Reproducing Bugs (03:31) - Unstuck Strategies: Logs & Revisiting the Problem (05:14) - Logs for Troubleshooting: Rails vs. JavaScript Errors (08:57) - Overlooking Error Messages: Assumptions & Panic (13:22) - Rails Logger vs. Puts: Debugging Preferences (14:39) - Debugging in JavaScript: Console.log Similarities (16:30) - Ruby Debugging Evolution: Pry to Debug Gem (19:52) - Git Tricks: Code Tracking & git-bisect (23:17) - Debugging Mindset: Patience, Persistence & Breaks (25:43) - Production Bugs: Front-end Display Issues (31:09) - Replicating Bugs: Development vs. Production (33:11) - Data-Driven Decision Making: Convincing with Evidence

In this episode of Ruby for All, Andrew and Julie chat about their recent experiences, including a ski trip with challenges due to a storm, and discuss burnout and returning to regular podcasting. Special guest, Ryan Caldwell, a software engineer at GitHub working on Copilot, joins the conversation to discuss his work, particularly on chat-related features of Copilot.  Ryan shares insights on programming languages, leaning into his transitions between Ruby, Java, and Go, and navigating the differences between dynamically and statically typed languages.  The conversation covers the benefits and challenges of implementing type checking in Ruby with Sorbet, especially in large projects like GitHub.  Ryan advocates for learning Ruby on Rails, praises its efficiency for staring profitable projects, and provides tips for using Copilot Chat effectively.  Press download now to hear more! [00:00:23] Julie fills us in on a recent skiing trip to went on in California, the huge storm they encountered and leaving early to avoid being stranded, the broken chain on their car, and a scary moment on a slope with her kids. Andrew shares he experienced burnout but sees improvement. [00:02:47] Ryan Caldwell introduces himself and tells us what he does. [00:03:53] Andrew asks Ryan about the programming languages used for Copilot, leading to a discussion about using Go for its REST API, the manageability of the project, and Ryan’s transition from Codespaces to Copilot after paternity leave. [00:04:49] Andrew wonders why Go was chosen, and Ryan explains the team’s familiarity with Go and the language’s simplicity. [00:06:12] Ryan reflects his first programming language and journey through JavaScript, Python, Java, and Ruby, highlighting his appreciation for Ruby. He talks about learning Ruby on the job, and his fondness for Rails. [00:08:02] Ryan discusses the challenges of picking up new languages and his approach to learning through project involvement. [00:09:24] Andrew asks about the shift from dynamic to typed languages, and Ryan shares his experiences transitioning from Ruby to Go. [00:11:53] We hear about Ryan’s work on type checking with Sorbet at GitHub, and he shares that Sorbet helped find edge cases and bugs, improving the code by requiring changes to the structure to prevent these issues. [00:15:09] Ryan feels the biggest benefit of Sorbet is enforcing developers to consider boundaries and contracts between classes, which encourages thoughtful coding and design. A downside he mentions is the time and confusion involved in the migration process, particularly for team members unfamiliar with the new syntax.[00:17:11] Julie inquires if Ryan would do anything differently regarding Sorbet implementation. He reflects on the challenge of estimating the time required for implementing Sorbet, dealing with complex code, and the difficulty of refactoring legacy code without comprehensive tests. [00:18:44] Would Ryan go back to Ruby/Rails without Sorbet? He states that he would for personal projects for speed but appreciates Sorbet in team settings for defining clear code boundaries. [00:19:31] Ryan suggests that small teams should consider Sorbet if it solves a specific problem, rather than adopting it without a clear purpose. [00:21:40] Ryan discusses his pride in streamlining the authentication process across different clients in Copilot, leading to a simplified codebase for the team. A tip he shares is to provide as much context as possible when using Copilot Chat to get better responses. [00:25:35] Andrew talks about custom instructions for ChatGPT, like ensuring all output is in bullet points, and wonders if such a feature exists for Copilot.[00:28:46] Ryan advises newer developers to be intentional about what they chose to learn in software development, emphasizing the importance of investing learning time wisely. And yes, Ruby on Rails is still worth learning in 2024. [00:31:03] Find out where you can follow Ryan on the interwebs.Panelists:Andrew MasonJulie J.Guest:Ryan CaldwellSponsors:HoneybadgerGoRailsLinks:Andrew Mason X/TwitterAndrew Mason WebsiteJulie J. X/TwitterJulie J. WebsiteRyan Caldwell X/TwitterRyan Caldwell GitHubGitHub CopilotGoSorbetVisual Studio Code-GitHub Copilot Series (YouTube) (00:00) - Ski Trip and Snow Adventures (02:47) - Ryan Caldwell's Intro (03:53) - Copilot’s Language Choice (06:12) - Journey Through Programming (09:24) - Dynamic to Typed Languages (11:53) - Sorbet’s Impact at GitHub (17:11) - Reflecting on Sorbet (21:40) - Copilot’s Authentication Success (25:35) - Customizing Copilot Chat (28:46) - Learning Paths in Software Dev (31:03) - Where to Follow Ryan

In this episode of Ruby for All, Andrew and Julie discuss the intricacies of callbacks in Active Record models. They talk about their experiences, the pros and cons of using callbacks, and the issues they faced. They also share some helpful use cases for callbacks, including user authentication, logging and auditing, custom slug generation, and the concept of “hooks.”  Also, Andrew and Julie review their ways of dealing with callbacks testing and debugging in a Rails application. Press download now to hear more! [00:02:32] Let’s learn about “callbacks” in Rails as Andrew explains what they are and uses an example of a blog post to explain how a callback might function when saving a post. [00:03:56] Julie inquires if Tiptap can be used in a browser for apps and they discuss before-save callbacks in a post model and how they can be used to extract and save a title.[00:06:19] Andrew elaborates on the three different types of callbacks: before, after, and around callbacks, and gives examples of each. [00:10:06] They discuss practical uses for before-validation callbacks, such as setting default values. [00:11:12] Andrew clarifies the concept of “hooks” in programming, comparing it to callbacks. [00:12:18] Julie asks for examples of actions taken after validation versus before validation. [00:13:19] Andrew talks about how a file upload, an after-create callback can be used for processing the file such as generating thumbnails or updating related resources. He lists examples use cases for callbacks like hashing passwords before saving to the database during user authentication, triggering email notifications after a comment is posted, and logging and auditing activities like user sign-ups or errors. [00:15:57] Julie is curious about whether deleted accounts really remove all user data or just make it as inaccessible, noting some services offer a soft delete option with a time window to recover the account. Andrew has not yet encountered the fallback log issue he set up but explains how before-destroy callbacks could be used to implement a time-based soft delete system. [00:17:19] Andrew describes using before-create callbacks for generating custom slugs for blog posts automatically. [00:17:54] Andrew recalls a discussion at RailsConf about the diverse opinions on using callbacks, with some developers strongly against them and others in favor. He acknowledges that while callbacks can simplify complex operations, they can also make debugging difficult and can become problematic if used excessively or inappropriately. [00:23:00] Julie asks Andrew where he stands on the use of callbacks, and he positions himself in the middle, closer to using them when appropriate. [00:25:16] Andrew emphasizes being cautious with callbacks and explains that callbacks are useful when certain actions need to happen automatically without explicit instruction every time a record is saved.[00:27:40] Andrew discusses the challenges of testing callbacks, as they can require additional setup in tests and slow down the test suite.  He concludes that callbacks are an integral part of Rails, he advises against using them as the first solution and recommends weighing their pros and cons carefully. Panelists:Andrew MasonJulie J.Sponsors:HoneybadgerGoRailsLinks:Andrew Mason X/TwitterAndrew Mason WebsiteJulie J. X/TwitterJulie J. WebsiteActive Record CallbacksTiptap (00:00) - Intro and Topic Overview (02:32) - Introduction to Callbacks in Rails (03:56) - Discussing Before-Save Callbacks and Tiptap (06:19) - Types of Callbacks: Before, After, and Around (10:06) - Uses for Before-Validation Callbacks (11:12) - Hooks vs Callbacks (12:18) - Practical Use Cases for Callbacks (15:57) - Soft Delete Options and Before-Destroy Callbacks (17:19) - Generating Custom Slugs with Before-Create Callbacks (17:54) - Diverse Opinions on Using Callbacks from RailsConf (23:00) - Andrew's Not an Expert (25:16) - Caution and Appropriate Use of Callbacks (27:40) - Challenges of Testing Callbacks

In today’s episode, Andrew and Julie dive into the topic of onboarding onto new teams.  Julie discusses her latest venture of switching teams, and Andrew sheds light on the innovative “Shape Up” method by Basecamp that’s shaking things up in the project management world, and why he prefers this over Agile. There’s talk of the dreaded technical debt, and how to keep it in check, plus the perks of pair programming and the need for a solid support system at work. Besides tackling these workplace issues, they also touch on the challenge of maintaining personal relationships in a remote working environment, keeping old team ties strong, and why asking questions is key to professional growth. Press download now to hear more! [00:01:45] Julie gives us an update on the changes at her work, transitioning from a consumer team to a platform team. She mentions that her old team is shifting from two-week sprints to a new process called “Shape Up,” which Andrew explains it as a product/project management philosophy from Basecamp, focusing on a six-week cycle.[00:03:08] Andrew details the process of shaping a feature, setting boundaries, identifying risks, and then pitching it. [00:04:25] Julie inquires about the involvement of engineers in the shaping and betting processes, and Andrew describes how it works at Podia, and how they used Flipper. [00:06:33] Andrew discusses the “cool down” period after a project cycle, which at Podia involves monitoring for bugs and wrapping up the project details rather than no scheduled work. [00:07:42] The topic of technical debt is addressed, with Andrew acknowledging its inevitability and the importance of staying on top of it through practices like support weeks.[00:10:54] Andrew expresses preference for the Shape Up process over Agile, appreciating the longer time frames, collaborative problem-solving with designers, and a less stressful experience with more planned projects. [00:12:14] Julie shares her transition to a new team and the challenges of ramping up, contrasting it with her experience from two years ago and feeling the pressure to not ask basic questions due to her years of experience.[00:13:53] Julie discusses the pressure she feels to ramp up quickly on her new team, acknowledging its self-imposed. Andrew and Julie talks about the onboarding process, where Julie notes the benefit of scheduled pair programming sessions with teammates as a key part of her learning. [00:15:44] Andrew shares Podia’s onboarding method, which involves acting like a user of the application to understand its various parts. Julie reflects on the complexity of her new team’s codebase and the challenge of understanding how services interact. [00:17:51] Andrew suggest creating a service diagram to visualize service interactions, something he found useful in previous jobs.  Julie considers the idea and mentions the potential benefits of a detailed visual representation of the service interactions for her understanding. [00:19:48] Julie and Andrew discuss the social dynamics of joining a new team with established relationships and the extra challenge of doing it so remotely. Andrew shares similar experiences and the importance of being inclusive to new team members. [00:21:59] Andrew shares how he’s an introvert by nature, and Julie and Andrew both agree on the importance of asking questions and having supportive seniors and leaders who encourage a culture of inquiry. [00:26:05] Julie talks about maintaining relationships with her old team and the value of keeping professional connections active, even after moving to a new team or company. Panelists:Andrew MasonJulie J.Sponsors:HoneybadgerGoRailsLinks:Andrew Mason X/TwitterAndrew Mason WebsiteJulie J. X/TwitterJulie J. WebsiteShape UpFlipper (00:00) - Intro and Topic Overview (01:45) - Julie's Team Transition and Shape Up Method (03:08) - Andrew on Shaping a Feature in Shape Up (04:25) - Engineer Involvement in Shaping and Betting (06:33) - Podia's "Cool Down" Period After Project Cycles (07:42) - Addressing Technical Debt (10:54) - Preference for Shape Up Over Agile (12:14) - Julie's Transition and Ramping Up Challenges (13:53) - Onboarding Process and Pair Programming (15:44) - Podia's Onboarding Method (17:51) - Creating a Service Diagram for Understanding Interactions (19:48) - Social Dynamics of Joining a New Team Remotely (21:59) - Importance of Asking Questions and Supportive Culture (26:05) - Maintaining Relationships with Old Teams

In this episode of Ruby for All, Andrew and Julie welcome special guests, James Garcia, Eric Halverson, and Caleb Mitchell, all part of The Agency of Learning run by Dave Paola. Today, they share their unique journeys into software development, ranging from music to technical support backgrounds, and their involvement in The Agency of Learning.  They discuss the value of the Ruby community, the joy of coding in Ruby, and the complexities of keeping up with Rails in a fast-paced tech environment. The conversation also touches on the importance of community in learning and how to get involved in the Ruby ecosystem, wrapping up with practical advice on handling race conditions in coding projects. Press download now to hear more! [00:00:13] Julie wonders if Andrew launched his feature and he mentions a setback due to architectural challenges. Julie relates to his issues sharing she faced a race condition blocking a release. [00:01:24] Julie mentions the Ruby for All Book Club and three guests joining them, who are a part of that club, where they are reading, The Well-Grounded Rubyist. [00:02:02] Eric, Caleb, and James introduce themselves and talk about their backgrounds. [00:05:36] What is The Agency of Learning? Eric shares his view and experience as an amazing ride, and James describes it as a “finishing school” for new programmers.[00:09:17] Andrew inquires about the unique challenges faced by Caleb due to his music background. Caleb discusses the time management challenges of balancing music and programming. [00:11:41] Julie’s interested to understand the guests’ experiences and challenges at The Agency of Learning. Caleb talks about the challenges of working with large, preexisting codebase. James adds to Caleb’s points, discussing the learning experiences with different production apps. [00:13:50] Andrew asks Julie about her experience working for Ruby for Good projects, and she expresses her enthusiasm for Ruby for Good. Andrew tells us what he did with contributing and praises Ruby for Good and encourages listeners to contribute. [00:14:43] Eric tells us about his current career position, and he describes a personal existential crisis following an intense project for a Rails conference, which led to a period of burnout and a shift in focus back to Ruby fundamentals. [00:18:08] Eric shares advice from Cody Norman, a lead at The Agency of Learning, about pursuing what inspires you. Andrew relates to Eric’s return to fundamentals and shares a perspective on learning Rails and Ruby.[00:19:41] Andrew asks about the hardest part of learning Rails in 2023. James discusses the challenge of keeping up with front-end updates in Rails, specifically Hotwire and Turbo Drive.  Caleb talks about the challenge of focusing learning on an era with abundant resources and highlights Launch School and The Odin Project as helpful resources. Eric reflects on the complexity of Rails and strategies learning it. [00:24:21] Julie asks the guests if they would recommend Rails to others or change their own journey. Caleb states his positive experience with Ruby and Rails, suggesting it as a good starting point.  James enjoys Rails and believes it helped him understand programming fundamentals, Eric speaks highly of Ruby and Rails and values the community. [00:27:15] Julie mentions that Ruby’s appeal kept her in software engineering and would recommend it as a first language. Andrew reflects on advising his brother on programming languages, highlighting the clarity Ruby brought him after learning Java.[00:29:20] Eric credits Julie for highlighting the importance of community in learning to program and James emphasizes reaching out for help in the Ruby community, praising its supportive nature. [00:30:53] Andrew asks for advice on how to join the Ruby community.  James tells us to connect through Twitter, Discord, and conferences. Caleb recommends reaching out to study or work with others, leading to lasting relationships. Eric started with podcasts, moved to Twitter, then conferences.[00:34:09] Julie shares two Discord groups for joining the Ruby community: The Ruby Learning Center and the GoRails Discord. [00:34:24] Find out where you can follow Eric, Caleb, and James online. [00:35:26] Andrew explains and gives an example of a race condition, since Julie had one at work that was driving her crazy.  Panelists:Andrew MasonJulie J.Guests:James GarciaEric HalversonCaleb MitchellSponsors:HoneybadgerGoRailsLinks:Andrew Mason X/TwitterAndrew Mason WebsiteJulie J. X/TwitterJulie J. WebsiteEric Halverson X/TwitterEric Halverson LinkedInJames Garcia X/TwitterJames Garcia LinkedInCaleb Mitchell LinkedInCaleb Mitchell Neovim-GitHubThe Agency of LearningRuby for GoodCody Norman X/TwitterDave Paola X/TwitterRuby for All-Episode 37: The Agency of Learning with Dave PaolaThe Well-Grounded Rubyist by David A. BlackLaunch SchoolThe Odin ProjectThe Ruby Learning Center DiscordGoRails Discord ServerRace condition (00:00) - Intro and Welcome (00:13) - Julie's Setback and Race Condition Issue (01:24) - Ruby for All Book Club Mention (02:02) - Introduction of Eric, Caleb, and James (05:36) - The Agency of Learning Explained (09:17) - Caleb's Challenges Balancing Music and Programming (11:41) - Guests' Experiences at The Agency of Learning (13:50) - Julie on Ruby for Good Projects (14:43) - Eric's Career Position and Return to Ruby Fundamentals (18:08) - Eric on Inspiration and Learning Rails and Ruby (19:41) - Hardest Part of Learning Rails in 2023 (24:21) - Guests' Thoughts on Recommending Rails (27:15) - Julie and Andrew on Ruby's Appeal (29:...

In this episode of Ruby for All, Andrew and Julie reconnect after a three-week break to share how they spent their vacation and their plans for the new year, as Julie talks about her family’s newest addition, a Whippet named Lucy, and Andrew getting plenty of rest, some rock climbing, and a hot yoga class. Then, they dive into the topic of burnout, sharing their personal experiences and strategies for managing burnout effectively. They discuss looking forward to Ruby 3.3, upcoming conferences, and a collective aim to level up their careers. Join Andrew and Julie as they kick off the new year with optimism and hit download now![00:00:17] Andrew and Julie catch up and discuss their Christmas breaks. Julie reveals they have a new family dog and Andrew reveals he would like to get a dog one day. [00:02:10] Andrew discusses his restful break, hibernating, visiting Virginia, rock climbing, and enjoyed a hot yoga class. [00:04:50] Over break, Julie started reading the book, “99 Bottles of OOP” by Sandi Metz and catching up on conference talks. She considers redoing her app with Turbo and Rails. [00:05:56] Andrew started reading “Practical VIM” but he’s ready to switch to Neovim. He’s been reading multiple books, trying to regain his love for reading, and he sets goals to read more and started using book summaries on Blinkist.[00:07:30] Andrew and Julie reminisce about their childhood reading habits. Julie talks about her struggles with reading comprehension and trying to pick it up again.[00:10:36] Andrew discusses his experience with speed reading techniques and explains how speed reading doesn’t necessarily impact his ADHD. He discusses extracting key points from books without reading every word. [00:12:37] Julie feels burned out from work and finds reading “99 Bottles of OOP” refreshing, and she expresses her ongoing burnout and asks Andrew’s thoughts on this.Andrew shares his personal warning signs of burnout, which includes losing the joy of programming, neglecting health, and feeling stuck and discouraged. [00:15:06] Julie acknowledges the importance of recognizing burnout signs and relates to the difficulty in identifying them, especially when juggling work and family. Andrew shares the challenge is addressing burnout once it’s recognized, emphasizing the need to focus on self-care and potentially making changes if the job is the cause.[00:16:11] Andrew suggests restoring sleep, exercise, and diet are crucial first steps to combat burnout, and he shares strategies for improvement, like focusing on sleep and reducing screen time.[00:17:56] Julie has replaced watching stimulating YouTube videos before bed with reading to cut down on screen time. Andrew set a goal for less screen time in 2024. [00:20:06] They shift the conversation to Ruby 3.3 and upcoming conferences and which ones they would like to attend. [00:21:13] Julie inquires if Andrew’s desire to focus on becoming a better engineer is about “leveling up.” Andrew agrees and expresses feeling stuck in his career for the past couple of years and is now ready to advance. [00:21:41] Julie questions if Andrew has a plan for achieving his career growth. Andrew explains he intends to improve his database skills, particularly Postgres and architecture, dive into security, and learn more about iOS development.[00:22:10] Some personal goals Andrew wants is to increase his typing speed and become more proficient with the home row typing method. Panelists:Andrew MasonJulie J.Sponsors:GoRailsHoneybadgerLinks:Andrew Mason X/TwitterAndrew Mason WebsiteJulie J. X/TwitterJulie J. Website99 Bottles of OOP by Sandi MetzPractical VIM by Drew NeilNeovimHigh Performance PostgreSQL for Rails by Andrew AtkinsonThe Programmer’s Brain by Felienne HermansBlinkist (00:00) - Intro and Welcome (00:17) - Catching up and Christmas breaks (02:10) - Andrew's restful break and activities (04:50) - Julie's reading and app plans (05:56) - Andrew's reading goals (07:30) - Childhood reading habits (10:36) - Andrew on speed reading (12:37) - Burnout and Julie's struggles (15:06) - Recognizing and addressing burnout (16:11) - Strategies for combating burnout (17:56) - Reducing screen time (20:06) - Ruby 3.3 and upcoming conferences (21:13) - Career growth and leveling up (21:41) - Andrew's career growth plan (22:10) - Personal goals and typing speed

In this episode of Ruby for All, host Andrew kicks things off with a warm welcome and well wishes to his absent co-host, Julie. Then he welcomes guest, Bhumi Shah, a self-taught web developer who transitioned from doing low-level embedded software for implantable medical devices.  She shares her journey of learning Ruby on Rails, her love for teaching, and her approach to learning as well.  Bhumi also talks about her ideas for creating accessible educational content, such as an audio-only technical content platform and a unique onboarding concept for junior developers joining a new company.  As the conversation wraps up, Andrew expresses his admiration for Bhumi’s insights, hoping that her story and ideas will motivate others to engage in content creation. Hit download now to hear more! [00:00:24] Bhumi details her self-taught journey into web development with Ruby on Rails and discusses her passion for teaching throughout her career and aims to pursue it more actively. [00:02:24] Bhumi shares her inspiration with teaching from Chris Oliver of GoRails and reflects on the importance of building a reputation and trust over time before monetizing content. She discusses her initial discomfort with identifying as a content creator and her journey towards embracing that aspect of her professional identity, and her current challenge with figuring out how to charge for her educational content. [00:04:13] Andrew comments on the coolness of being a content creator and his own struggle with this identity despite creating substantial content. He suggests Podia as a platform for hosting courses. [00:05:01] We hear what motivated Bhumi from Chris’s story as she tells us the importance of focusing on the beginning of one’s journey and the gradual process of building an audience and credibility. [00:06:31] Bhumi discuss the challenges and potential discouragement in charging for content. She feels that it’s too early and she needs people to first know and trust her. [00:08:33] Andrew reflects on setting realistic goals for course creation and the difficulties of publishing content. Bhumi shares her sporadic content creation history and her resolve to maintain consistency going forward. [00:12:18] Andrew asks Bhumi about her research preferences and prompts Bhumi to discuss her learning approach where she shares her philosophy on learning technical skills by aiming to become “friends” rather than “acquaintances” with technologies, using CSS as an example. [00:13:26] She explains her strategy for tackling new topics like Turbo and Hotwire, focusing on practical application and “just-in-time learning” to solve immediate problems and “follow-on learning” to deepen her understanding later. She also mentions engaging in “intentional learning” or “deliberate learning” through reading programming books and taking courses. [00:15:21] Andrew shifts the conversation to teaching and asks Bhumi what she enjoys in teaching. She finds joy in seeing the moment of understanding in others and sharing her rewarding experience with mentorship on the Indie Hackers platform.[00:17:28] Andrew tells us he experiences joy when he sees other people experience joy which is why he mentors. He shares his own challenge of being naturally curious but not a deep learner, which affects his approach to teaching and sharing knowledge.  [00:18:59] Bhumi asks Andrew about his perceived barriers to sharing content, prompting a discussion about perfectionism. Andrew describes his struggle with publishing content that meets his high standards. [00:23:36] Andrew asks Bhumi about her preferences for mediums, and she expresses her comfort with writing, particularly in her newsletter format, which excludes links to encourage focused reading. [00:29:52] Andrew reflects on the challenge of discussing code through audio and suggests a narrative approach to sharing technical content, focusing on problem-solving stories which can engage listeners. He references Darknet Diaries Podcast as an example of combining narrative storytelling with technical details, which helps listeners learn through context. [00:27:09] Bhumi proposes a podcast idea centered around debugging stories which Andrew expands on, and she shares another idea related to onboarding junior developers, suggesting that companies should hire a contractor as a full-time mentor to support new developers during their initial months. Andrew praises her idea![00:31:37] Andrew acknowledges the cost concern but emphasizes the long-term benefits of junior developers learning effective problem-solving. Bhumi highlights the importance of teaching developers how to teach themselves and become self-sufficient.[00:32:30] As a final message, Bhumi encourages listeners to give feedback to content creators, noting the positive impact it has on them.[00:33:32] Find out where you can follow Bhumi and her work online. Panelist:Andrew MasonGuest:Bhumi ShahSponsors:GoRailsHoneybadgerLinks:Andrew Mason X/TwitterAndrew Mason WebsiteJulie J. X/TwitterJulie J. WebsiteBhumi Shah X/TwitterOne Ruby Question NewsletterIndie HackersPodiaHow Rails.env works with EnvironmentInquirer & StringInquirer-by Bhumi Shah (GoRails)Chris Oliver X/TwitterDarknet Diaries (00:00) - Intro and Welcome (00:24) - Bhumi's Journey into Ruby on Rails (02:24) - Inspiration and Building Trust in Content Creation (04:13) - Andrew's Thoughts on Content Creation and Podia (05:01) - Bhumi on Building an Audience (06:31) - Challenges in Charging for Content (08:33) - Setting Goals for Course Creation (12:18) - Bhumi's Learning Approach (13:26) - Tackling New Topics in Web Development (15:21) - Teaching and Mentorship (17:28) - Andrew's Approach to Mentoring (18:59) - Overcoming Perfectionism in Content Sharing (23:36) - Medium Preferences for Content Sharing (27:09) - Discussing Code through Audio and Storytelling (29:52) - Debugging Stories and Onboarding Junior Developers (31:37) - Importance of Teaching Developers Self-Sufficiency (32:30) - Encouraging Listener Feedback (33:32) - Follow Bhumi and Her Work