|May 28th, 2018
t and what is a
+. When writing
calculations, however, there's often a lot less redundancy and so
it's more worth it to make sure distinctions aren't being lost. One
way to handle this would be to have clean handwriting overall, but
what I do instead is use glyphs that are more robust and remain
distinct even if written poorly. 
Here are what I do with some tricky glyphs:
It's nice if these are clear to other people, but the main goal is for them not to be confused with each other. Things to help this:
iincludes a right hook
tincludes a right hook
1is a straight line
Ihas top and bottom lines
zhas a cross
7has a cross
and still be able to read back what I wrote. This is also something I need when transcribing whiteboard coding interviews at work: 
You might notice that I don't use this for the
int. It's just for variables.
 I don't think this is original to me, but it's also something I picked up gradually as I realized that certain forms were more reliable.
 Yes, candidates write code on whiteboards, we transcribe it on paper, and then we type it into a computer for others to review. Someday candidates will write on laptops, I guess, but it was weird that we were doing it in 2010, and we're still doing it in 2018, so who knows.