5 ms·
if you have the right company setup, headcount, and culture then you can absolutely build a world where teams can be allowed to force “perfection” over time, ev
by dastbe 5y ago
if you have the right company setup, headcount, and culture then you can absolutely build a world where teams can be allowed to force “perfection” over time, even with amazing levels of automation.
i think the interesting thing is that while you’d think that is the ideal everyone should strive for, the reality is that’s inapplicable or detrimental to run most businesses that way.
- oblio 5y ago> build a world where teams can be allowed to force “perfection” over time, even with amazing levels of automation. I'm confused, did you mean "without" instead of "with"? Also: > i think the interesting thing is that while you’d think that is the ideal everyone should strive for, the reality is that’s inapplicable or detrimental to run most businesses that way. Why would you say that is?
- dastbe 5y agoi meant with. google has built some really great tools for minimizing toil when pushing major changes across a codebase. even then, there’s a nontrivial overhead that is borne across the company. > Why would you say that is? many/most businesses don’t have the margins/scale/time to focus on it. in a lot of businesses (amazons included) the goal for the business is to try as many things as fast as possible and scale that which works and abandon what fails. the goal of infrastructure there is to get out of the way and enable the layers above to build things as naively and simply as possible with little to no churn.
- emodendroket 5y agoI think we see a good reason here: normal people don't think "this API is so beautiful," they think "these clowns are making me do a migration yet again."