Hi is it not Pseudocode.

I find Pseudocode point less. Had the argument with the teacher 20 years ago. Because my hand writting sux big time its ugly looking writting.

So the teacher made a demand that I sit for the test in Pseudocode and if I failed Ill be out of the course. So I said ok.

Did the ugly Peudocode with my best ugly writting and passed. I was allowed to continue the c course.

I find Pseudocode point less.

Pseudocode is, I think, useful for communicating the broad strokes of an implementation or algorithm to others. Admittedly I'm not sure of how commonly such communication is called for, but should the occasion arise, it seems like a useful skill to have available.

How is this (which I'd catagorize as de-linting), an important skill? Does it raise your productivity in any way?

I'm not sure that I've done that exercise that Onigiri describes, but it occurs to me that reducing such small mistakes--even ones that might be caught by automatic tools--might make one a bit more productive by reducing the time spent responding to such mistakes, even via an automated tool. I won't advocate never using automated tools or IDEs, but as an temporary exercise I could see such manual debugging of small mistakes potentially increasing one's overall coding speed.

By analogy, I recall that when I was being taught to touch-type part of the training involved placing a box over the keyboard and my hands. Now, typing with a box over the keyboard is likely to be a nuisance as a general practice, but, if I'm not much mistaken, doing so while learning to touch-type discourages one from looking at the keyboard, and thus aids in teaching one to type without doing so.