One way our team has dealt with this question in a highly serverless-oriented and infrastructure-as-code-driven (how's THAT for buzzword soup) environment is to explicitly separate stateful resources from stateless,…
Very interesting concept, thanks for sharing! Context and intent are critical when trying to understand code - this looks like a useful way to capture that. Merging the call stack display with the "debugger" is IMHO a…
I'm fairly sure that reveal.js URLs are hackable... the slide number is added to the URL as an anchor. Setting that in your URL bar might be a simple way to jump around to various slides. Also, ESC brings up a slide map…
One way our team has dealt with this question in a highly serverless-oriented and infrastructure-as-code-driven (how's THAT for buzzword soup) environment is to explicitly separate stateful resources from stateless,…
Very interesting concept, thanks for sharing! Context and intent are critical when trying to understand code - this looks like a useful way to capture that. Merging the call stack display with the "debugger" is IMHO a…
I'm fairly sure that reveal.js URLs are hackable... the slide number is added to the URL as an anchor. Setting that in your URL bar might be a simple way to jump around to various slides. Also, ESC brings up a slide map…