HN user

tyrex2017

82 karma
Posts4
Comments70
View on HN

access management, and scalability: can better do simultaneous writes, and use several copies horizontally

BUT: you probably need 1k+ or 10k+ requests per second to start getting advantages

How to Work Hard 5 years ago

The question you address is much more difficult to answer, if not impossible.

I read the article with the preface: Lets suppose workimg hard is desirable. How to do this?

This is the correct reading for me

Fastly Outage 5 years ago

As I replied to a sibling comment, I never thought about firing Bob. I think we can assign responsibilities without being mean or denegrate someone.

I am critizing myself all the time for stuff. No hurt feelings there.

Fastly Outage 5 years ago

I see: When I said we need to hold people accountable, you may have heard that we need to fire people. That was honestly never on my mind.

Maybe its a cultural thing. I hear a lot of firing at the US. I am from Europe.

Fastly Outage 5 years ago

I disagree. People implemented those systems, so if you are correct that it is the systems fault, then it is also a persons fault.

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.

YC never claimed to have a perfect selection process. I wouldn’t hold them accountable for the teams they pick based on a business plan and a 10 min discussion. Its just a good guess.

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.

Poor in Tech 5 years ago

i found that one weird

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

imho, for most, the biggest advantage of writing a book is to upsell consulting after that.

together with that, it is a great learning opportunity for the author.

all in all: not for me

I dont understand the OP and others who feel it is soul crushing to do stupid tasks.

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.

One optimisation: dont write into your resume that you had many jobs and stopped. Similar for college. Eg only mention IBM and fill the rest with “freelancer” or “educational projects”.

The details depend on your specific resume and dates, though.

When I was doing iOS apps around 2016, there was a simple way to request a refund if you purchased sth by mistake. I think it was a web form using your Apple id. The amount was autocredited back to you immediately.

Not sure if this was the norm back then, and if it is now.

Many comments say it cant be done, but this is disingenious. As if we were bureaucrats with no imagination:

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.

One note: For me it is much harder if I had control of the root cause because then it is my fault and I am crushing myself about how I was wrong etc.

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.