3 ms·
Based on a non-scientific study, I think the spatial thinkers do great with concurrency, the visual thinkers do okay, and everyone else is in real trouble. Whic
by hinkley 4y ago
Based on a non-scientific study, I think the spatial thinkers do great with concurrency, the visual thinkers do okay, and everyone else is in real trouble. Which reminds me, I need to interview my developer friend with aphantasia about how he feels about concurrency.
Concurrency should be the sizzle and not the steak, otherwise you're reducing the diversity of your team rather substantially. Good people are hard enough to find. Driving the people you have away doesn't generally end well.
- deleted 4y ago[deleted]
- toast0 4y agoI wouldn't say I have aphantasia, but I don't know that I think of computers in a visual way, although kind of maybe. I'm not great at writing concurrent code with locks and shared memory (messaging passing is much easier for me to do well; but message passing is almost exclusively built upon locks and shared memory, so my hands are forced). But I'm pretty good at debugging concurrency problems of either type. It's all about thinking about the sequence of events of an individual thread of execution and not making assumptions that things would necessarily stay the same between steps... and then trying to line up how another thread could make those things happen. I don't line the threads up visually, but I guess you could?