Adding debugger(s)

[raghubetina]

In content v3, I would like to emphasize using debuggers much more heavily than we have in the past.

But I myself am confused about the state of debuggers. There's the new built-in Ruby Debug, and the stuff we're used to:

https://github.com/pry/pry

https://github.com/pry/pry-rails

https://github.com/deivid-rodriguez/pry-byebug

The old stuff, together, provides pretty good ergonomics. Should we use that, or should we switch to the new Ruby Debug? It has some cool VSCode integrations, we which can use now that we're using official VSCode?

Need to investigate how all these interact, and what a good set of them to use in each of our phases is.

@jelaniwoods @bpurinton Any thoughts/preferences?

[jelaniwoods]

I think we'll want pry/pry-rails already for the rails console overrides, so I'm leaning towards using those on that reason alone.

[bpurinton]

I'm curious what you mean exactly by "emphasize using debuggers". How do we do that currently? Is this just the steps where we open a rails console (database querying) or irb (early Ruby projects) terminal and run some line-by-line code? Or is this truly new content that you haven't shown before, like in this lesson with binding.pry?

[jelaniwoods]

I'm not sure if there was ever written content for using debuggers, but I do remember around when I first joined we sometimes showed binding.pry in class.