4 ms·
> I don't understand, you can still clarify assumptions via chat, or grab someone when they're available for a quick voice chat if writing a wall of text will b
by sneak 3y ago
> I don't understand, you can still clarify assumptions via chat, or grab someone when they're available for a quick voice chat if writing a wall of text will be unbearable or inefficient. That's communication 101
Most people are super duper slow typers.
Remote is less efficient unless most/all of your staff can touch type at a high rate of speed.
I don't hire people who can't type, but most people never learned.
- someweirdperson 3y ago> I don't hire people who can't type, but most people never learned. Do you require formal touch typing explicitly, or a certain minimum wpm (how fast?), or both? Do you include iportant charcters (for coding) in the test?
- sneak 3y agotyping speed for coding is irrelevant. the bottleneck with coding is not data entry. the important thing is that they can type at a high rate of speed. i personally type at around 120wpm which is excessive, but anyone who doesn't type 40-50wpm is obviously not sufficiently skilled as a remote worker.
- deleted 3y ago[deleted]
- novok 3y agoIMO if speed is really an issue then whisper can take care of that. It's pretty good and fast.
- sneak 3y agoSo far, we have not seen that. People opt for meetings where they can speak versus using tools to become better at communicating via text.