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/ …
-
-
Which brings us back to communication. Making sure all the DS on your team have the same baseline mental models goes a long way towards enabling effective collaboration across seemingly unrelated work streams.
Show this thread -
Anyway, developing a shared mental model of your company's problem space IS a serious part of the Data Science profession. I don't know if it's accurate to say knowledge sharing is to data science as peer review is to software engineering, but I feel like there's something there.
Show this thread
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.

