4 ms·
> you learn how people interact with one another and you can learn to model your own communication based off of that. This strikes me a little like "By reading
by bobbiechen 6y ago
> you learn how people interact with one another and you can learn to model your own communication based off of that.
This strikes me a little like "By reading lots of good code, you can learn to model your own code based on that". It probably helps, but a lot is dependent on context.
The blog post goes into this with the long quote about choosing tools and techniques for an appendectomy. How do you capture that sort of context in an email thread? Annotations like "Based on X and Y factors, I chose to write Z", where X and Y are not explicit in the email text?
I haven't looked too closely, but it seems to me that the primary value of these email threads (in terms of learning communication) is to provide a body of real-world examples - but there also needs to be applied experience (with feedback) with written communication for the lessons to really sink in.
- Alex3917 6y ago> The blog post goes into this with the long quote about choosing tools and techniques for an appendectomy. How do you capture that sort of context in an email thread? I mean in terms of our tool, the knowledge is either already in an email or it isn't. It's meant for retaining knowledge that's already being created anyway. You certainly could purposely capture knowledge in email for the purpose of being viewable and searchable in our tool (and some people do), but in that case there may be other better tools.