"How to see what's going on"

[jennybc]

I recommend that you gather all the "visibility", "printing", and "debugging" strategies in one place and make it very discoverable. One of my tidy eval learning challenges is that my usual tricks for play and inspection don't work and I can't easily remember the official strategies, like qq_show().

[jennybc]

I also feel like there are more tips that aren't about a specific function, but rather just a thing one can do while developing a function. I'll try to return here with specific examples, as I re-encounter them.

[lionel-]

Using browser() within tidy eval functions to discover the environment.

Could have some qq_show() mode that colourises bindings as a function of where they are found.