Nice article about anti-patterns in communicating about and solving technical problems. They're particularly relevant for DS teams since much DS work does not produce value on its own; it needs to be understood and internalized by someone else to be useful https://ansonwhitmer.com/four-communication-techniques-for-solving-technical-problems/ …
-
-
maybe knowledge sharing is to data science as abstraction sharing is to software engineering? it feels like often times the culprit behind software systems behaving poorly is that we represent the same concept / process in slightly different and incompatible ways across systems
-
That's a really great point. It makes me think about how much grief is caused by different understandings of what a "user" is, especially when that gets baked into different metrics and goals
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

