Should be cleared up now. Sorry about that.
I'm always surprised you have the time to respond in these threads, jgrahamc.
Cloudflare Experiencing Latency Issues
51–60 of 69 posts
Re: Cloudflare Experiencing Latency Issues
#52Re: Cloudflare Experiencing Latency Issues
#53Earlier quoted context omitted.
This is a fair statement. Didn't use to be this way - I blame the participation trophy era of kids.
You're engaging in it yourself right now by using euphemism/implication to suggest a certain type of person instead of just saying "whiny, overly sensitive children" (which I assume is what you mean). You should remove the plank from your own eye, first. You don't get to blame others for your voluntarily chosen courses of action.
There is a difference between euphemism and idiom, nicknames and handwave identifiers.
Re: Cloudflare Experiencing Latency Issues
#54Earlier quoted context omitted.
This reminds me of the younger generation sometimes perceiving messages ending in a period as rude. I'm also sometimes surprised by how effectively a simple statement like "I don't want to spend money on that" can shut down even a pushy salesman. Or even the simple "No." can work wonders.
> This reminds me of the younger generation sometimes perceiving messages ending in a period as rude. I've never seen any comments regarding a single period, but I've seen comments (and sometimes agree with them) regarding the perceived rudeness when ending messages in ellipses. "Good job..." seems almost sarcastic compared to "Good job.".
[deleted]
Re: Cloudflare Experiencing Latency Issues
#55Earlier quoted context omitted.
And yet I'm learning about this outage from HN. How did that happen?
Aviate Navigate Communicate. They did all three of those in the space of a few minutes (if you were checking their status page - which you can subscribe to by the way).
That rule is great for one single person (a pilot). In corporate incident management we can do better, and not blocking communication because you're overwhelmed with keeping the system up; in fact proper incident management workflows designate different people with different roles and delegates communication duties to a dedicated person if possible.
Re: Cloudflare Experiencing Latency Issues
#56Earlier quoted context omitted.
Is there a particular reason you perceived their response as "scolding?" It just looks like a straightforward answer.
In my experience, a lot of Americans interpret direct, no-wasted-word statements as aggressive or confrontational. Euphemism and indirect implication is the norm in American communication, much to my dismay. It can wrap around to extremes sometimes, too. https://sneak.berlin/20191201/american-communication/
Interesting: IME, it's the Americans who are called rude and overly direct. Go to Japan and give it a try, for example.
Edit: Reading your link: First, that's well-written and insightful; thank you.
However, it seems like a common (young, if I dare guess) frustration with human communication, especially among geeks (if I dare guess, here on HN, and including myself as one): Communication is not transmission of information, but a social interaction. You have to think about all these other things (where many geeks feel out of their depth), and in fact those other things are more consequential than the information (with which many geeks feel very confident). In other words, it sucks to have all the information, to be a master at it, and find that it doesn't matter so much.
Tip: Don't try to dismiss it; it's human nature and won't change; learn the skills. 'Skill' #1: learn to not objectify the other party (they aren't an endpoint device in your communication network), and the best tools for that: curiosity about them - about their unique universe in their mind, their own wants and perspectives, completely unrelated to yours - and compassion: they have a difficult life too. (Of course, that's just my perspective! :) )
Re: Cloudflare Experiencing Latency Issues
#57Earlier quoted context omitted.
Aviate Navigate Communicate. They did all three of those in the space of a few minutes (if you were checking their status page - which you can subscribe to by the way).
That rule is great for one single person (a pilot). In corporate incident management we can do better, and not blocking communication because you're overwhelmed with keeping the system up; in fact proper incident management workflows designate different people with different roles and delegates communication duties to a dedicated person if possible.
> That rule is great for one single person (a pilot). In corporate incident management we can do better, and not blocking communication because you're overwhelmed with keeping the system up; in fact proper incident management workflows designate different people with different roles and delegates communication duties to a dedicated person if possible.
I agree with you, but Cloudflare seem to have done exactly what you're describing in this instance?
Re: Cloudflare Experiencing Latency Issues
#58Earlier quoted context omitted.
In my experience, a lot of Americans interpret direct, no-wasted-word statements as aggressive or confrontational. Euphemism and indirect implication is the norm in American communication, much to my dismay. It can wrap around to extremes sometimes, too. https://sneak.berlin/20191201/american-communication/
This is a fair statement. Didn't use to be this way - I blame the participation trophy era of kids.
> I blame the participation trophy era of kids.
As one Gen Y/Zer once commented: Those trophies weren't handing out themselves, and they weren't the kids' idea. Whose idea were they?
Re: Cloudflare Experiencing Latency Issues
#59Re: Cloudflare Experiencing Latency Issues
#60Earlier quoted context omitted.
I really like it when people in your position at such a big company post on here, even if it is a brief comment like this. Thank you!
I would have posted faster but I was too busy doing my own little bit of debugging which consisted of 1. dig @1.1.1.1 jgc.org 2. nc -v 104.22.11.223 80 3. curl -v https://jgc.org/cdn-cgi/trace 4. curl -v https://jgc.org/ Hmm #1 was fast so network is routing OK. Hmm #2 was fast so TCP is OK. Hmm #3 was fast so I know (because I worked on that code) that this code path is good. Hmm #4 is slow so that means component X…
you often do you code these days?