Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
By, Godfrey Chan Every once a while, Rails might behave in strange ways that you did not expect, and it could be difficult to figure out what is really going on. Was it a bug in the framework? Could it be one of the gems I am using? Did I do something wrong? In this session, we will look at some tips, tricks and tools to help you debug your Rails issues. Along the way, you will also learn how to dive into the Rails codebase without getting lost. The next time you a mysterious bug finds its way into your Rails applications, you will be well-equipped to pry open the black box yourself!
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In his talk at RailsConf 2015, Godfrey Chan explores the often mysterious and complex inner workings of Ruby on Rails, emphasizing the importance of debugging skills for developers. He begins by welcoming attendees and sharing his personal journey within the Rails community, including his contributions to the Rails core team. The theme of the talk is to demystify Rails and provide practical debugging strategies for developers facing unexpected issues. **Key points discussed include:** - **Understanding the 'black box' of Rails:** Chan explains that many developers perceive Rails as magical, but with the right understanding, it’s just a framework with conventions and sensible defaults. - **Initial debugging steps:** He encourages developers to check documentation, ensure they are using the latest version of Rails, and emphasizes the importance of understanding the stack trace when an error occurs. - **Utilizing the stack trace:** The stack trace is introduced as a powerful debugging tool; Chan explains how to interpret the stack trace to track where errors originated. - **Advanced debugging techniques:** Chan discusses various methods, including using 'put' statements for debugging, raising custom errors to track code execution, and leveraging the debugger provided with Rails, such as 'byebug.' - **Examining Rails code:** He suggests opening up gems and the Rails codebase using 'bundle open' to investigate the source of issues, noting that understanding the code can often lead to identifying the problem. - **Reproducing bugs:** Chan advises creating a new Rails app or using simplified examples to replicate issues. This can help determine if a problem lies within Rails itself or in the additional gems used. - **Engagement with the community:** He encourages participation in community events like office hours for collaborative troubleshooting and contributions to Rails. The conclusion emphasizes that debugging is a crucial skill for any developer working with Rails, positioning it as an ongoing learning process rather than a one-off challenge. Chan reminds attendees that the conference offers resources and community support for further engagement and learning opportunities. Throughout the talk, Chan's passion for the Rails framework and its community is evident, aiming to empower developers to tackle the inevitable challenges they face in their coding endeavors.
Suggest modifications
Cancel
