RR 369: How Ruby 2.5 Prints Backtraces and Error Messages with Vishal Telangre
Jul 03, 2018•43 min
Episode description
Panel:
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.
- Dave Kimura
- Eric Berry
- Catherine Meyers
- Vishal intro
- BigBinary posts a lot of blogs
- Write about the experiences that they encounter while working
- Plan-free Fridays
- Is there any type of motivation or culture that adds to people wanting to provide so many blog posts?
- Suggestions for someone trying to get into blogging
- Vishal’s blog posts at BigBinary
- Start with a simple topic
- Your blog post doesn’t have to “change the world”
- Blogging about new things coming up
- Ruby 2.5 backtrace
- His blog post
- Changes to backtrace in Ruby 2.5
- Makes debugging convenient
- Huge change for companies who do logs
- Effect of change from a developer standpoint
- Time saved
- Mixed sentiments on this change
- When this features is enabled
- And much, much more!
- Ruby 2.5 prints backtrace and error message in reverse order
- BigBinary
- Ruby on Rails
- Kuberernetes
- Elm
- Vishal’s blog posts at BigBinary
- Vishal’s GitHub
- Vishaltelangre.com
- @suruwat
- Developer conundrum
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.