On Thursday, October 20, 2022 at 7:59:40 AM UTC-5 Edward K. Ream wrote: > It's time for me to see what's next after Leo. I won't be happy not > programming :-) >
My first thought was to create a tracer/debugger that would allow me to study python programs without modifying the source code. But this plan would be foolish. Debuggers slow down programs dramatically. Worse, debuggers operate at the statement level. Instead, my usual strategy is to modify the source code to gather "interesting" data. This is perfectly safe, provided I use git to manage the sources! So a more effective strategy is: - Ask questions whose answers would provide insights. - Add statements to help answer those questions. - Be alert for bespoke tools to augment tracing statements. - Repeat as necessary. Those bespoke tools might create or reveal patterns, so look for new pattern-producing tools. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/e77dbf1f-7b26-46a2-92a9-9f496d6e7ee0n%40googlegroups.com.
