3 ms·
> Effectively I always asked them what they think the code "should" do and what the results should be. https://rubberduckdebugging.com/ https://rubberduckdebug
by datenhorst 7y ago
> Effectively I always asked them what they think the code "should" do and what the results should be.
https://rubberduckdebugging.com/ https://rubberduckdebugging.com/
- duxup 7y agoPretty much, just warming them up to get them into debug mode ;) For me I (and the customer) all thought we knew what it should do, but it's always good to spell it out for everyone so we all understand when / or even if we're seeing an exception. Lots of "Woah hey is that what the protocol really says?" moments too.