3 ms·
is this "friction" to just the same as the traditional orthogonal relationship between developers and operational teams? One want to introduce new features int
by kazen44 6y ago
is this "friction" to just the same as the traditional orthogonal relationship between developers and operational teams?
One want to introduce new features into the system, the other has the job of maintaining stability so the service is actually available to it's users.
in my opinion a good metric on how "fast to move" is hard to define. The "Move fast and break things" that is popular in sillicon valley does not work when your services are used by critical systems. (Think, water supply. power supply, medical etc). But moving too slowly has the disadvantages of being (too late) to market.
It's a very fine balance to strike, if not impossible to reach.
- tayo42 6y agoI think its more like ordering food in a restaurant then dev and ops. Where the platform team is the restaurant and the workers are some of the engineers and the customers/eaters are the users of the platform. Kitchen needs to cook in a certain way, cant be doing a million substituions the waiter can only do so much, customers can't cut the line if its busy, should have made a reservation.