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.
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.
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.
Way to inadvertently eliminate basically anybody who is neurodiverse. Most of the great engineers I know, myself included, had absolutely shit university records because brains don’t always do what they want to and university is rarely a motivating factor for people As the other commenter mentioned, rarely are the motivators the same between university and a job.
> Of course, we are not recruiting PHDs to do backend work, but people who did decently well in school are usually nice to work with.
What does someone’s grades have to do with how nice it is to work with them? I know people that aced their classes and are complete sociopaths, and I know people that dropped out of high school and are lovely to work with.
> There are brilliant dropouts, of course, but they are not the norm.
You say they exist, but you’d never consider them according to the rest of your comment.