3 ms·
Because a lot of work needs sync and is inefficient to do in an async manner. Even for software engineers, let alone other people centric roles. Most obvious ex
by RestlessMind 4y ago
Because a lot of work needs sync and is inefficient to do in an async manner. Even for software engineers, let alone other people centric roles. Most obvious example would be designing nuances of a complex system. That discussion is needed at least once every 4-6 weeks and I wish we are around a whiteboard at that time.
- mejutoco 4y agoAsync work is more difficult, but not more inefficient. It is the difference between putting a lot of work into an email that perfectly explains something, vs shooting a quick email and offload the effort to the recipient. In this case communication ability is crucial, since it requires written documents. Many people (managers and developers) lack the discipline, patience, and incentives to adopt this style of work.
- RestlessMind 4y ago> Many people (managers and developers) lack the discipline, patience, and incentives to adopt this style of work. Correct. So what do we do then? Changing people is hard. And communication styles are ingrained after a certain age. Also, even the best communicators are finding it hard to do some tasks async, like designing a complex system.
- mejutoco 4y ago> like designing a complex system If kernel devs can do it so can 90% of companies, if there is a will. This seems to me like a culture matter that needs to come from the top, though.