51 ms·

Everyone that works in development is literate but not everyone that works in development has good reading comprehension or is good at generating meaningful pro

Everyone that works in development is literate but not everyone that works in development has good reading comprehension or is good at generating meaningful prose at a keyboard. Many people who work in development just don't like to read and consider it a chore. I think an interesting interview question would involve reading. "What were the last 3 things you have read to learn something?" "Do you read for enjoyment?" Based on the results you could group people in terms of how they relate to text.

ctvo 5y ago
In my experience a key characteristic of a good software engineer is their ability to handle dense, technical texts. We do it all the time, from academic papers (less often) to documentation (every other hour). Not liking to read (?!), and thinking it's a chore, because we're only humans, will mean you won't do it unless forced and will either lack a deep understanding of a subject or reach for someone else to do it for you (RTFM). Not a fan of the often repeated, flawed [1], "we have different modes of learning" mantra that sometimes comes with these discussions too. That myth is so hard to debunk likely because of this very issue! 1 - https://www.theatlantic.com/science/archive/2018/04/the-myth-of-learning-styles/557687/ https://www.theatlantic.com/science/archive/2018/04/the-myth...