50% is anti-big-tech and 20% is our fear of being made redundant.
82 karma · joined December 28, 2017
50% is anti-big-tech and 20% is our fear of being made redundant.
BUT: you probably need 1k+ or 10k+ requests per second to start getting advantages
Yes, many new remote positions will be created, and it is a trend which will grow. But most will (have to) stay right where they are.
I read the article with the preface: Lets suppose workimg hard is desirable. How to do this?
This is the correct reading for me
Thats why it may be a good idea to test higher risk populations or people with health issues.
It could make the ratio of absolute true positives to false positives 10x better
I am critizing myself all the time for stuff. No hurt feelings there.
Maybe its a cultural thing. I hear a lot of firing at the US. I am from Europe.
People must be held accountable to have good incentives to reduce such outtages in the future.
I do agree though that we should always be compassionate and realistic with other humans.
If they doubled down on the team after demo day, then I am with you.
Compare this with hiring. I have heard successful people say they do get 1 in 5 hires wrong, even after a process which is 10x more thorough.
But the world moved on without us.
Lets be honest: For 99.9% of users, no misuse ever happens which they care about.
I dont need more than 50 ml per session. I will have one per week, which means I have 15 weeks of pleasure with that one.
in my experience, there is no difference in how poor or rich people behave towards low-level staff.
in general, my feeling is the rich are more friendly, but it may be less genuine
And thats a helpful (if not the only one) indicator on whether there will be enough ICU beds one month from now. If not, we should consider lockdowning.
together with that, it is a great learning opportunity for the author.
all in all: not for me
Meanwhile, it will work always anyway. Thats how I would build it
For one, whats the big deal? I can put in the difficult hours and continue. Secondly, often, what is considered inefficient and stupid is not, or just cant be done better because organizations are not perfect.
Having said that, OP, I have lots of respect for your strength to go for what you want.
The details depend on your specific resume and dates, though.
Not sure if this was the norm back then, and if it is now.
Eg just have 2 caps: First cap triggers a red alarm prohibiting provisioning, or storing, of new data. The second one (when you are like 50% above the first cap) is dark red, closing down everything except storage.
Sure, decisions have to be made for every single service, but you don’t need a perfect solution if it is optional.
Eg, you could start ONLY with EC2 and will have fixed 50% of the problem.
Lots of hand waiving and describing the usual phenomena in other terms.
I will follow this thread hoping someone points out that good stuff is coming later in the text, but I doubt it.
If it’s some others fault, you can be sad but shrug it off more easily. Also, the others wont be as mad towards you.