Coding
fib(50) never finishes.
It doesn't rewrite your code. It asks you back, then draws the tree.
Inside the film
What it shows
A recursive fib(50) never seems to finish. Instead of rewriting the code, DuckyHelper asks a question back, then draws the call tree right next to the code: fib(4) calls fib(3) and fib(2), fib(3) calls fib(2) again, and the repeats pile up. Spot the repeats, and the fix is yours to make.
The DuckyHelper part
In this film, it sees what is on the screen and draws on it and it asks a question back, so you do the thinking. That is DuckyHelper on any screen: press one key in any app and ask.
- Press fn on a Mac, or Ctrl+Shift+Space on Windows and Linux, in any app.
- Ask your question out loud, the way you would ask a person next to you.
- Watch it explain on your screen or on the blackboard, then answer its question back.
