171–180 of 207 posts
FYI Israelis are not on holiday - our holidays are on whole different dates. Hire Israelis and experience no down time while working with Silicon Valley level talent
Every Saturday they will convince you that they have a list..... When it actually just a calendar matrix..and steal your land
Earlier quoted context omitted.
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.
> but western culture is very hesitant to say "sorry" This is very wrong. Eastern/Asian culture with its obsession with saving face is the culture where saying sorry is anathema.
Years ago we started to get basic introduction into Chinese culture, so that we could better navigate situations with a Chinese customer. This helped to better understand requirements and defuse certain situations. I've NEVER experience Chinese or Indian companies go to the same length, instead they will frequently attempt to bullshit their way out of situations or be offended that you believe that their product/service might in some way be at fault and they sure as hell won't apologize for it, under any circumstances.
Earlier quoted context omitted.
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.
> but western culture is very hesitant to say "sorry" This is very wrong. Eastern/Asian culture with its obsession with saving face is the culture where saying sorry is anathema.
Earlier quoted context omitted.
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.
> but western culture is very hesitant to say "sorry" This is very wrong. Eastern/Asian culture with its obsession with saving face is the culture where saying sorry is anathema.
Ever been to Japan?
It's crazy to want to fight someone who is trying to help you, but lots of people end up in crazed states when hammering away at projects behind their computer terminals.
Taking a step back even further, I think that requiring any form of software support or correspondence with software makers is a completely alien concept. I have done it under 5 times in more than 30 years of using computer software and writing documentation.
No doubt that countless people encounter show stopping software issues for which they cannot find alternative tools, workarounds, or workflows, but I find that it's almost always better to just go shopping at these junctures, rather than enter into some kind of chain of correspondence hoping that someone out there in the ether might possibly one day fix your problem.
Yeah, we discourage production changes starting first or second december week, and start freezing changes third december week until it's frozen solid fourth december week until second week of january. December tends to be hell for our customers, so stability should be a priority there. And honestly, no one wants to work on holidays. So lets just wrap everything starting in december, maybe use the third week for some…
It's a similar concept to not deploying on Fridays. If you're afraid to introduce changes due to some arbitrary timing, perhaps it's worth focusing on the source of that uncertainty.
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 ...
https://youtu.be/hVimVzgtD6w https://www.ted.com/playlists/474/the_best_hans_rosling_talk...
Meanwhile a huge number of us (non-religious? introverted kernel compiling cave dwellers?) treat this period no differently than any other week in the year. I'll be here keepin the servers runnin :horns: It's actually my favorite time of the year. Everyone is gone, it is quiet, and I can get shit done.
Yeah, we discourage production changes starting first or second december week, and start freezing changes third december week until it's frozen solid fourth december week until second week of january. December tends to be hell for our customers, so stability should be a priority there. And honestly, no one wants to work on holidays. So lets just wrap everything starting in december, maybe use the third week for some…
I completely acknowledge it's utopian but isn't it a better goal to target continuous stability, or at least semi trusted process for when things inevitably break? It's a similar concept to not deploying on Fridays. If you're afraid to introduce changes due to some arbitrary timing, perhaps it's worth focusing on the source of that uncertainty.
We always should target better stability, but no matter how good your system and incident response are, if your goal is to minimize customer disruption during a certain time window, or avoid dealing with incidents on weekends, minimizing production changes is the simplest and most effective measure