3 ms·

> Well, if you're building a thing that's doing hundreds of millions in revenue, that might be a big deal. But you? You're a team of one! You rollback that bad

by monksy 6y ago

> Well, if you're building a thing that's doing hundreds of millions in revenue, that might be a big deal. But you? You're a team of one! You rollback that bad deploy and basically no one cares! Human lives, customer faith in product, GDPR violations, HPPA violations, data, time/resources in space missions https://medium.com/@ryancohane/financial-cost-of-software-bugs-51b4d193f107 https://medium.com/@ryancohane/financial-cost-of-software-bu... https://en.wikipedia.org/wiki/Mars_Climate_Orbiter https://en.wikipedia.org/wiki/Mars_Climate_Orbiter

mercer 6y ago
> But you? You're a team of one! You rollback that bad deploy and basically no one cares! I somehow doubt that comparing this 'team of one project' to the Mars Climate Orbiter leads to any useful conclusions. It's a nice bit of hyperbole though!
- monksy 6y ago
  Rollbacks can create data loss. Also, rollbacks are not always a viable option. Anyways..this was to address the issue of a bug. I took the comment of "it's just a team of one" as a way of trying to justify not putting your engineering due diligence into delivering a product to the customer.
  - moreaccountspls 6y ago
    > not putting your engineering due diligence into delivering a product to the customer. Yes. This is exactly what this person should do. Stop worrying about arbitrary rules and just deliver the damn product already. A hacky, shitty, unfinished product in your customer's hands that can be iterated on beats one that never got shipped at all every day of the week.
  - mercer 6y ago
    > Rollbacks can create data loss. Also, rollbacks are not always a viable option. I've delivered a number of products (in the early days of my career) to clients where data loss happened and while not fun, it also didn't significantly harm the product or piss off said client. I saw my responsibility primarily to do the best I could and clearly communicate potential risks to the client. > I took the comment of "it's just a team of one" as a way of trying to justify not putting your engineering due diligence into delivering a product to the customer. That I do agree with, but 'due diligence' is a very vague concept. I guess honest communication about the consequence of various choices is perhaps the core aspect? And of course 'engineering due diligence', in my opinion, includes making choices that might lead to an inferior result from a 'purely' engineering perspective.
moreaccountspls 6y ago
I don't understand your point. We're specifically talking about a one person company.

by monksy 6y ago

mercer 6y ago

> But you? You're a team of one! You rollback that bad deploy and basically no one cares! I somehow doubt that comparing this 'team of one project' to the Mars Climate Orbiter leads to any useful conclusions. It's a nice bit of hyperbole though!

monksy 6y ago
Rollbacks can create data loss. Also, rollbacks are not always a viable option. Anyways..this was to address the issue of a bug. I took the comment of "it's just a team of one" as a way of trying to justify not putting your engineering due diligence into delivering a product to the customer.
- moreaccountspls 6y ago
  > not putting your engineering due diligence into delivering a product to the customer. Yes. This is exactly what this person should do. Stop worrying about arbitrary rules and just deliver the damn product already. A hacky, shitty, unfinished product in your customer's hands that can be iterated on beats one that never got shipped at all every day of the week.
- mercer 6y ago
  > Rollbacks can create data loss. Also, rollbacks are not always a viable option. I've delivered a number of products (in the early days of my career) to clients where data loss happened and while not fun, it also didn't significantly harm the product or piss off said client. I saw my responsibility primarily to do the best I could and clearly communicate potential risks to the client. > I took the comment of "it's just a team of one" as a way of trying to justify not putting your engineering due diligence into delivering a product to the customer. That I do agree with, but 'due diligence' is a very vague concept. I guess honest communication about the consequence of various choices is perhaps the core aspect? And of course 'engineering due diligence', in my opinion, includes making choices that might lead to an inferior result from a 'purely' engineering perspective.

moreaccountspls 6y ago

I don't understand your point. We're specifically talking about a one person company.