Understanding Handwriting Source Code on Paper [Closed]

Do you want to improve this question?Update your question, Edit this post to be answered with facts and quotes.

Closed 7 years ago.

I'm not sure if it's the right question, but I'd like to post it.

The other day, there was a programmer's recruitment test where he had his source code hung on paper.
I know that there used to be a coding sheet and a hand-drawn habit.
Rumor has it that you might get caught on paper in an exam.

If you actually try it, it's very difficult, and if you spell a function by hand, it doesn't come out, or you don't know the number of parentheses,
I can't imagine how many lines it will take, so I want to rewrite it many times, but I give up writing it by hand because it takes too much time.
In the end, I couldn't write a satisfactory code, and I was like, "It would be a crime to implement this kind of excrement code."

How can I write the code on paper as well as I can?
Do you have any tips?

There is also the question of whether this test is meaningful in the first place.
How do you feel?