I'm exactly the type of person that thinks everything would be better if there was just a ~Central Data (Science) Strategy~, but to play devil's advocate for a moment--how many engineering teams actually have coherent guiding policies that underpin all decisions and activities?
-
-
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
Show this thread -
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.
Show this thread -
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?
Show this thread -
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.
Show this thread -
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
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.

