3 ms·

> doesn't want to work and prefers doing something else It's possible, but that's really what the interview process is supposed to be for. In programming, thi

> doesn't want to work and prefers doing something else It's possible, but that's really what the interview process is supposed to be for. In programming, this is kind of a necessity, because from the outside, deep work looks exactly like "loafing". You can't threaten, harass, cajole or otherwise motivate somebody to actually mentally focus on something the way you could, say, threaten to chop off their hands if they stop digging for diamonds. You might want to, but even you would eventually have to conclude that it didn't work. Ultimately, you have to trust the people responsible for doing the work.

Psychlist 4y ago
> {programming} from the outside, deep work looks exactly like "loafing". Worse, from the outside causing major problems that will only show up later looks exactly like typing really intently. I remember one horrible problem I had dumped on me where I spent a week reading stuff online and doodling. Once I had a doodle I liked I threw together a multithreaded user authentication system in a week then spent a week making sure it actually worked. CIO was very impressed but afterwards admitted the first week drove him quietly insane. Luckily my team leader kept saying "that's what thinking looks like". Some managers completely miss point of thinking, and not just when other people are doing it /s