I personally prefer the former as you can visually see the return one level of indentation below function name. It shows a guaranteed result barring no early-exits. Something about having the return embedded lower just seems off to me.
One suggestion is to allow for HJKL or WASD movement. Arrow keys are fine and intuitive, but not in the best location. I remember playing nethack years ago and it had the HJKL system.
It was also called "Hungry Cat Picross" until Nintendo trademarked "Picross" and went after everything branded with it. This actually caused me to learn about the nonograms as I had assumed the type of puzzle was always called picross.
We bought a cheap standalone bug zapper and put it on the counter and it has been a life saver for the fruit flies. Ours come from bananas, we think, and washing them after bringing them home from from the store seems to help some too.
The best part is, working from our offices in separate rooms, my wife and I will hear a zap and both shout "Good job bug zapper!"
For anyone else who was initially confused like I was:
On first look, I thought the solution had to involve exploiting commands over telnet to inject a mult command.
It took me until looking at part 2 to realize it involved actually modifying the source code (which makes sense in retrospect).
If you are looking to actually try and solve it, keep that in mind and don't look at part 2 :)
The "pre-order" label is mostly due to supply chain delays. Currently there is a ~month lead time. I ordered mine back in late January and it is arriving this week.
Although I'm not sure of the rate, people have reported getting banned from google services without notice for seemingly no apparent reason. And there is little recourse to unlocking their account.
It's something I personally don't worry about, but something to consider when relying on their services for backing up data.
There are vim bindings in most (if not all) popular IDEs so learning the base keystrokes can be lifted up to these at a later point.
They did explain that they based there decision based off the most popular command line editor (based on a stack overflow survey). Although it would probably be good to at least reference other popular / useful ones for exploratory purposes, for a quick overview course I think focusing on vim makes ample sense.