recentpopularlog in


« earlier   
Myoepithelial cells are a dynamic barrier to epithelial dissemination | JCB
The mammary epithelium is composed of an inner luminal and surrounding myoepithelial cell layer. The presence of cancer cells beyond the myoepithelium defines invasive breast cancer, yet the role of the myoepithelium during invasion remains unclear. We developed a 3D organotypic culture assay to model this process through lineage-specific expression of the prometastatic transcription factor Twist1. We sought to distinguish the functional role of the myoepithelium in regulating invasion and local dissemination. Myoepithelial-specific Twist1 expression induced cell-autonomous myoepithelial cell escape. Remarkably, luminal-specific Twist1 expression was rarely sufficient for escape. Time-lapse microscopy revealed that myoepithelial cells collectively restrain and reinternalize invading Twist1+ luminal cells. Barrier function correlated with myoepithelial abundance and required the expression of α-smooth muscle actin and P-cadherin. We next demonstrated that myoepithelial cells can restrain and recapture invasive cancer cells. Our data establish the concept of the myoepithelium as a dynamic barrier to luminal dissemination and implicate both smooth muscle contractility and intercellular adhesion in barrier function.
myoepithelial_cells  invasion  twist  luminal_cells 
april 2019 by Segalllab
Switch from Slack to Twist: A Calmer, More Organized Way to Collaborate
ML: Probleme dann, wenn (1) apriori eine Chat-Kultur besteht, die man eher kanalisieren muss (statt umgekehrt: anregen); (2) wenn man das als community-kanal und intranet-ersatz missversteht. es muss PROJEKT-bezogen sein, d.h. teams müssen alle 3 monate "sterben".

SLACK hat eine chat-umgebung und darin channels. MS Teams hat eben projekte. (Andere Kritiker sagen: Es ist besser, alle Konversationen an Trello/Planner-artige Strukturen zu hängen. Also nicht die Konversation/Thema ist das Interface, sondern Arbeitspaket/Task. Für welche Art von Projekten trifft das zu?)

But when we tried to collaborate on projects, Slack felt disorganized, even a bit chaotic:
It was hard to find specific conversations a day later (much less a week or a month). We wasted time searching for important decisions, ideas, and files
Our team felt like we had to be online 24/7 so we wouldn’t miss anything. We were chained to Slack and couldn’t find the time to focus
As a remote team, we couldn’t make decisions together. Our North American team would be sleeping while those in Europe and Asia were online, and vice versa

We needed to stay digitally connected, but without the jumbled conversations and always-on distractions. That’s why we built Twist: a calmer, more organized place to work together.

If your team is feeling distracted and overwhelmed by real-time chat, use this guide to make the jump from Slack without losing the hard-earned momentum and culture you’ve built along the way.
office365:teams:kurs  twist  slack  threaded:conversation 
january 2019 by MicrowebOrg

Copy this bookmark:

to read