6 ms·
> Hire people who can and are willing to read. Also make sure they are able to read more than the first few words of the first sentence…(from bitter experience
by no-s 4y ago
> Hire people who can and are willing to read.
Also make sure they are able to read more than the first few words of the first sentence…(from bitter experience)
- ratww 4y agoReading is a huge problem with certain developers. It's not only documentation, which they ask for but never read. They also won't read error messages, and ask seniors for help on almost every situation. (But the most infuriating thing is when they assume the error message doesn't have any info, and when sharing the screen you have to repeatedly ask them to not navigate away because you're reading it)
- BeetleB 4y ago> (But the most infuriating thing is when they assume the error message doesn't have any info, and when sharing the screen you have to repeatedly ask them to not navigate away because you're reading it) Oh yeah - this drives me nuts, although I've seen it more from laypeople than developers. Some people are hard wired to just hit Enter for any informational window that pops up on the screen. I've talked to people who have no idea they're getting errors: "I just hit Enter so I can get to the program."
- ratww 4y agoI kinda understand when laypeople do it, can't really blame them. I guess developers who do it got the habit from their layperson days.