I believe this is reasonable advice but I believe it can be simplified even further.
Live-coding in an interview be it in a text editor (shitty or otherwise - those web based platforms can be really painful and slow to use when sharing a screen with zoom, e.g.) or on a whiteboard is a skill, and I’m not sure it is one that is worth optimizing for because I’m not sure that this particular skill really has much to do with day-to-day software development. I am sure it doesn’t hurt to be able to perform in a foreign environment with someone judging you over your shoulder but I hope dev work in general possesses as little of this type of work as possible.
But you can simplify the problem considerably and ask someone to solve a fairly easy problem in just about any live coding fashion. To wit: I learned Java in school, spent some time at a job using other languages, then interviewed for an intermediate software developer position. The hiring manager asked me to write fizzbuzz in Java. I had never heard of the fizz buzz problem and I hadn’t written Java in some time. Still, I was able to successfully solve the problem with a minimum of difficulty (though admittedly a maximum of nerves). He asked me a few questions about how to improve the solution, and I mumbled some stuff about combining string concatenation statements instead of simply appending to the string, something which made him nod his head sagely and that I still consider to be a largely useless micro-optimization, but the main thing, the important part, is that I demonstrated some coding ability in a matter of minutes, right in front of his eyes.
It’s something that sticks with me and I think it’s a valuable type of interview question.
I got the job.
https://en.wikipedia.org/wiki/Fizz_buzz