Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
When our tests fail all we get is output in a terminal. Testing is core to the culture of Ruby, and the tools are sophisticated, but something big is missing from the workflow. Namely, a powerful debugger. Integrating Pry creates an interactive, enjoyable TDD workflow. In this talk, I'll recount the somewhat unique development experience that made me a believer. I'll demonstrate with Pry a responsive and immersive TDD cycle, taking a test to green before it exits its first run. Joel Turnbull is a Code Designer at Gaslight. He's been a staple in the Cincinnati development community for over 10 years. This is his first presentation at a Rails Conf. Help us caption & translate this video! http://amara.org/v/FG1D/
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 the presentation titled "Debugger Driven Development with Pry," Joel Turnbull discusses how integrating Pry into the Ruby development workflow enhances the test-driven development (TDD) process. He emphasizes that while many Ruby developers tend to avoid using debuggers, this behavior stems from the lack of effective tools prior to Pry. Joel advocates for a shift in mindset, using debuggers not just to fix software but to facilitate the software building process itself. Key Points Discussed: - **Pry as a Game-Changer**: Joel introduces Pry as a powerful alternative to the Interactive Ruby Shell (IRB), offering runtime interaction features that improve development efficiency. - **Enhanced Introspection**: Pry offers advanced introspection capabilities, allowing developers to ask detailed questions about their code and object states without the burdensome effort required in IRB. - **Workflow Features**: He showcases features like syntax highlighting, tab completion, and the ability to drop into a runtime at any point in the application to explore and troubleshoot code. - **Real-time Debugging**: Using a demonstration of a bowling score tracking application, Joel illustrates how to use binding.pry to pause code execution and analyze live data, reactively editing and improving the code. - **Tools for TDD**: Joel connects the benefits of Pry to TDD, explaining how the iterative process of writing tests, observing failures, and fixing code is well supported by Pry. He highlights a feature that allows automatic creation of method definitions and class structures in response to errors, thereby streamlining the development process. - **Conclusion**: Joel emphasizes that successful programming requires embracing the runtime environment of tools like Pry. He argues that using a debugger while building software can lead to a more productive and engaging development experience, while also enhancing focus by minimizing context switching. In conclusion, Joel asserts that developers should embrace Pry as an innovative tool in their workflow, combining it with the effectiveness of TDD to create a seamless and enjoyable coding experience. He encourages developers to leverage Pry not just to fix issues but as an integral component in their development processes, ultimately advocating for a deeper immersion in a dynamic coding environment.
Suggest modifications
Cancel
