3 ms·
I know that this is how the common thinking goes, but this is also the same thinking that those "big bad corporations" use, and that the "big bad government" us
by didibus 7y ago
I know that this is how the common thinking goes, but this is also the same thinking that those "big bad corporations" use, and that the "big bad government" uses, etc.
My point is that we're no better. Do we stop and think... Hum, what's happening to that 0.0001% Did they just miss some important email from the USCIS about some mandatory thing they needed to do? Will that get them deported? What if they missed a memo from their boss? Etc. And in the case of the article here, does it mean that a few dozens of people haven't been paid in a few weeks?
By reducing everything to some number, I feel it disconnects us and trivializes things.
I don't know that I have an answer. But I find that it is interesting how I think everyone in a company can somehow wash their hands on issues the company is causing by adopting this kind of mentality. Well, given the constraints we had, we went for the big fish only. It's almost some kind of oppression by the majority. Majority of users get their new features while a minority suffers.
I think it's easy to start scape goating left and right: well our team isn't given enough resources, well we missed out on profit targets so had to cut back, well investors are pulling out, well government imposes all these regulations on us, well voters wants us too, etc.
So I guess we're all a victim of the system and no one is to blame or could have done anything about it.
Maybe I'm being a bit cynical, but it's something I've been asking myself more. Could I actually do something about it at my work? At least when it comes to engineering systems without such error, maybe just thinking about impact one such failure could have, I can push a little harder, I can consider it a little more.