141–150 of 207 posts
Earlier quoted context omitted.
They'd need a goy on-call to flick the switch.
As I wrote in another comment, most Israelis in tech are not religious and take on call duties during Saturdays and religious holidays
If you’re atheist or of a religion that isn’t relevant then why do you care? There’s no spiritual meaning. It’s just a day off. Get off the fence and own your convictions.
Always be kind, and say it’s your fault. If you don’t do it for the sake of the person you are asking for help, do it because it works better. That’s the most practical advice [0] ever given by Hans Rosling [1], the Fact master himself: > In fact, I have the secret to how to get the best help immediately from any customer service, like the phone company or the bank or anything. I have the best line, it always works.…
I'm going to try that's but will need more information about Hans Rosling to get through the identity verification ...
Always be kind, and say it’s your fault. If you don’t do it for the sake of the person you are asking for help, do it because it works better. That’s the most practical advice [0] ever given by Hans Rosling [1], the Fact master himself: > In fact, I have the secret to how to get the best help immediately from any customer service, like the phone company or the bank or anything. I have the best line, it always works.…
I think this works great sometimes, but I've been in plenty of situations where "I messed up" leads to being railroaded into the "boilerplate tech support" discussion tree. "Did you try doing X", "Did you confirm that Y is Z", "Make sure your VPN is working, try installing a new config", and finally "That's strange, double check all your parameters, there may be a typo in there somewhere"
Earlier quoted context omitted.
My dad once took apart his motorcycle to change out a cylinder seal. He put it all back together and it wouldn't start. The mechanic at the shop heard the story, and then checked one thing: indeed my dad had forgotten to refuel it. That tech support tree is always worth checking.
He took apart a motorcycle because the gas tank was empty?
Earlier quoted context omitted.
> Always be kind, and say it’s your fault. I do this with internal teams at work. I've found approaching other teams with issues with their library/framework in a "this could be our mistake" manner really helps in keeping them from getting defensive and stonewalling.
Saying, "I'm sorry; I've made a mistake" is the killer disarming technique for even the most emotional conflict. Not sure if it's our pride or fear of liability but western culture is very hesitant to say "sorry" - other than the fake one "I'm sorry if anyone interpreted my actions|remarks|words as ..." - that doesn't count.
It could go both ways. I can never change though; saying sorry is too simple for me
On call sucks so badly. At this point of my life, I firmly believe that there's not enough amount of money that can compensate the mental suffering it implies. Even more if the company you work for has this mentality of "deal with it" without making improvements, which was my case in the last period I did on call and what made the camel's back to break for me. Nowadays I simply refuse it. For those who are still on t…
You might be under the impression that what makes you qualified for various positions in software development is primarily your technical acumen and ability to work with other technically-capable engineers.
You’d be wrong.
While a certain minimum of capability is required to do your day-to-day work, what your value really consists of is in grinding yourself against the piercing pincers of elusive bugs and razor-wire bundles of bullshit code until something resembling progress is made. You are not a problem-solver, you are a problem-endurer.
https://web.archive.org/web/20160317234837/https://medium.co... -> Point 4
non-internet-connected data center Woah. That sounds wild. If you are allowed to share: What industry / company? I would like to hear more about that setup!
Earlier quoted context omitted.
> Always be kind, and say it’s your fault. I do this with internal teams at work. I've found approaching other teams with issues with their library/framework in a "this could be our mistake" manner really helps in keeping them from getting defensive and stonewalling.
Saying, "I'm sorry; I've made a mistake" is the killer disarming technique for even the most emotional conflict. Not sure if it's our pride or fear of liability but western culture is very hesitant to say "sorry" - other than the fake one "I'm sorry if anyone interpreted my actions|remarks|words as ..." - that doesn't count.
To give a really grotesque example, there is an country run by autocrats that carelessly unleashed a plague on the world because they prioritized their self image over taking descisive action to prevent an epidemic.