3 ms·

If you are not providing critical infrastructure and people will not die, it's just you losing money, because your business is structured in a wrong way. You di

If you are not providing critical infrastructure and people will not die, it's just you losing money, because your business is structured in a wrong way. You did it to yourself and should not expect people on salary to bear the cost of your wrong decisions. If you do provide critical infrastructure and people will die, it's also not my problem, because there will be a law requiring you to hire an SRE and a regulator to fine you to hell for not doing a good job too. Being a founder is your 24h job and you made a gamble to make big money in a capitalistic game. I didn't, I'm fine with making 5 liters of borscht on weekend and eating it through most of the week. It's not even WLB, it's not what I have signed up in this life.

alephnerd 3y ago
You're entitled to your opinion, just like I am entitled not hire you and hire an Israeli, Czech, Pole, or Indian for the same salary (and I have). Btw, I'm in the cybersecurity space, so a Tier 1 escalation generally means nation state attack or business stopping attack on a customer. > You did it to yourself and should not expect people on salary to bear the cost of your wrong decisions. Plenty of escalations are due to bugs. It's good to operate on a blameless model, but if I followed your model I'd gladly put the blame on engineers like you if the cause was found to be a dependency issue or a misconfiguration issue. Ofc, in the real world peers and I operate on a blameless model. Shit happens, but we need to fix our mistakes asap if they are made.
- Muromec 3y ago
  Sure, escalations are result of mistakes people make. This is why businesses exists -- they have processes, quality control and all that stuff that ensures reliable outcome while consisting of individually unreliable things. That's the whole point and that's what you are supposed to get right. There are different strategies, and hiring people from exploitable jurisdictions is one. As all obvious strategies it has downsides and it will also stop working at some point in future which may be irrelevant for you.
- deleted 3y ago
  [deleted]
- seba_dos1 3y ago
  If you want people to be available on call, hire and pay them for an on-call job. As simple as that.

alephnerd 3y ago

You're entitled to your opinion, just like I am entitled not hire you and hire an Israeli, Czech, Pole, or Indian for the same salary (and I have). Btw, I'm in the cybersecurity space, so a Tier 1 escalation generally means nation state attack or business stopping attack on a customer. > You did it to yourself and should not expect people on salary to bear the cost of your wrong decisions. Plenty of escalations are due to bugs. It's good to operate on a blameless model, but if I followed your model I'd gladly put the blame on engineers like you if the cause was found to be a dependency issue or a misconfiguration issue. Ofc, in the real world peers and I operate on a blameless model. Shit happens, but we need to fix our mistakes asap if they are made.

Muromec 3y ago
Sure, escalations are result of mistakes people make. This is why businesses exists -- they have processes, quality control and all that stuff that ensures reliable outcome while consisting of individually unreliable things. That's the whole point and that's what you are supposed to get right. There are different strategies, and hiring people from exploitable jurisdictions is one. As all obvious strategies it has downsides and it will also stop working at some point in future which may be irrelevant for you.
deleted 3y ago
[deleted]
seba_dos1 3y ago
If you want people to be available on call, hire and pay them for an on-call job. As simple as that.