Wrong but useful. Working @Twitter, tweeting about data science and people management.
"Wait, it's all her views?" 
"Always has been"
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
It's obvious how org size matters. If there's more people to do the work, it's easier for it to get done even without detailed planning. You don't have to manage your resources carefully because there's more redundancy
Clearer expectations for the profession is also pretty straightforward. SWEs are less likely to be asked to do something that's outside their skillset because the average tech employee as a fairly good idea of what the skillset of an engineer actually is.
More standardized patterns of collaboration across teams, though--this is one that is IMO underrated in the Data. How many differences in approach or opinion are smoothed over in the SWE world by doing things your own way and then jamming it through some protocol or API?
That agreed-upon form of contact, that common language--it means it's easier to away with having a bunch of unrelated and maybe even contradictory plans, so long as you plan for the right form of communication between two systems or services.
It's probably better if you have a centralized strategy and a shared set of design principles for your engineering org, but standardization atones for so many sins. Maybe standardization is the strategy that data teams really need
It's ridiculously common for the same team if not individuals to be expected to do a bit of data engineering, a bit of forecasting, and a bit of product/corporate strategy, simply because that's just all Analytics, right? 
press f to pay respects
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
