Re:Shopify cancels all recurring meetings with over two peop...
by mindcrime on Tuesday January 03, 2023 @10:51PM
(#34241795)
handling it "async" on chat is more often than not quicker.
I'm sure there are times when it is better, and times when it isn't. I generally find that if a question is REALLY simple, then async is fine. Eg:
Q: What's the IP for the bumblefraxx gateway again?
A: 10.0.14.233
Ok, sure. Done, handled in a few seconds. But for anything that goes beyond about 2 Q/A "cycles", I generally find that a call is faster, because I can figure things out a lot faster when I can see all of the relevant details myself. Eg:
Q: The bumblefraxx gateway isn't working, can you help?
A: Did you make sure the IP is right?
Q: Yeah. Do you think the frozgibbit might be wedged?
A: ...
15 minutes later
Let's have a call so I can see this myself
/me looks at screen. Notices some trivial typo in config for bumblefraxx gateway. Problem fixed in 15 minutes and 15 seconds, when it could have been 15 seconds
I'm sure there are times when it is better, and times when it isn't. I generally find that if a question is REALLY simple, then async is fine. Eg:
Q: What's the IP for the bumblefraxx gateway again?
A: 10.0.14.233
Ok, sure. Done, handled in a few seconds. But for anything that goes beyond about 2 Q/A "cycles", I generally find that a call is faster, because I can figure things out a lot faster when I can see all of the relevant details myself. Eg:
Q: The bumblefraxx gateway isn't working, can you help?
A: Did you make sure the IP is right?
Q: Yeah. Do you think the frozgibbit might be wedged?
A: ...
15 minutes later
Let's have a call so I can see this myself
/me looks at screen. Notices some trivial typo in config for bumblefraxx gateway. Problem fixed in 15 minutes and 15 seconds, when it could have been 15 seconds