As much as I hate looking at colleges and grades, and try not to let them influence my hiring decisions, I see a correlation between both quality of school and academic record and job performance. Correlation does not mean causation, and it’s a heuristic and not a rule. Many individuals are exceptions to this heuristic. However, when hiring and faced with a lot of applicants, we need to make decisions based on whatever signals are available.
One example is sloppy resumes with grammar and spelling mistakes. What does spelling have to do with coding? Both require care and attention, and your resume reflects how much care and attention dedicate to things.
I do agree about the virtues of a resume that shows that it has been put together with care and attention.
But don't forget that while coding, the IDE, compiler, or whatever will correct your spelling mistakes in a very short feedback loop, with hardly any penalty for your output rate. That might mean that your dyslexic super programmer has never learned the value of carefully going over each text before submission.
> has never learned the value of carefully going over each text before submission.
Exactly. Proofreading and double checking is a valuable skill/habit. I would consider the programmers that learned this to be better programmers. I’d venture a guess that those that learned this early on got better grades. I can use the grade as an aggregate proxy score of a bunch of different abilities and habits. Many of those are helpful at work.
One example is sloppy resumes with grammar and spelling mistakes. What does spelling have to do with coding? Both require care and attention, and your resume reflects how much care and attention dedicate to things.