3 ms·

I think this goes in line with companies as a whole as well. I work at a place where features are pushed at a very very high speed and we have realized that the

I think this goes in line with companies as a whole as well. I work at a place where features are pushed at a very very high speed and we have realized that the tradeoff is us missing pretty crucial edge cases in our development. Now i’m not sure if people have worked in a place where they shipped products fast but were able to minimize bugs but i’d love to hear how your company achieved that. Is it even possible? Does it all come down to hiring to suit your fast paced needs?

foolfoolz 2y ago
it depends on the business and industry. at some phases in a business’s life you need to get features out more than stability. some industries are more sensitive to bugs than others. it’s not a one size fits all approach. to shift the culture from “fast” to “safe” is mostly a team-based effort because not all teams need to shift. and even within a team you may have experimental and mature products. i’ve seen this shift happen successfully multiple times. it must come from leadership. C-level and down. even if it’s just for one team. or one product. you need the buy in all the way up. and then your people in the chain will adapt to changing expectations
calebio 2y ago
Is it fair to say that also in your experience, those crucial edge cases/misses accumulate over time, making it even harder to ship things? I've found this a lot in data systems where folks glue stuff together as fast as possible to "ship", while missing the huge glaring issues with the foundation that they've built on top of wet, sliding mud.
- kwakubiney 2y ago
  Yeah pretty fair to say. The company is in a domain where accuracy is very important and crucial because we deal with people’s money, but most products are also in a market where competition is high so moves must be made quickly.I have not been there for long but it seems in the beginning, the foundation laid because of fast shipping culture has caused all these problems.

foolfoolz 2y ago

it depends on the business and industry. at some phases in a business’s life you need to get features out more than stability. some industries are more sensitive to bugs than others. it’s not a one size fits all approach. to shift the culture from “fast” to “safe” is mostly a team-based effort because not all teams need to shift. and even within a team you may have experimental and mature products. i’ve seen this shift happen successfully multiple times. it must come from leadership. C-level and down. even if it’s just for one team. or one product. you need the buy in all the way up. and then your people in the chain will adapt to changing expectations

calebio 2y ago

Is it fair to say that also in your experience, those crucial edge cases/misses accumulate over time, making it even harder to ship things? I've found this a lot in data systems where folks glue stuff together as fast as possible to "ship", while missing the huge glaring issues with the foundation that they've built on top of wet, sliding mud.

kwakubiney 2y ago
Yeah pretty fair to say. The company is in a domain where accuracy is very important and crucial because we deal with people’s money, but most products are also in a market where competition is high so moves must be made quickly.I have not been there for long but it seems in the beginning, the foundation laid because of fast shipping culture has caused all these problems.