The standard document may say one thing, but what people do in the real world is the real standard. If your software has issues with the world's most popular IMAP server, you need to adjust your software to be compliant with the standard.

I'm personally more sympathetic to your actual conclusion, but it's odd how often a single argument can be used to support two conflicting beliefs.

[1] https://en.wikipedia.org/wiki/List_of_tornadoes_and_tornado_...

I grew up on the edges of the New Madrid fault area and, while earthquakes were never discussed, we did tornado drills about every two months while in school. After I entered the workforce, that got closer to once a year, but you were still expected to have a plan and supplies. It was basic emergency preparedness, like any sensible person. Granted, big F5 tornados are rare, but small ones were common enough to not even be noteworthy.

Having left that region as an adult, it was a small culture shock meeting people who never had this kind of training. After all, the places I've visited all experience tornados, though not as often as my old home town. Still, the usual attitude I encounter is "I've never seen a tornado - they don't happen here". It's true that tornados don't happen often, just like my birthplace hasn't seen a serious earthquake in my lifetime, but they do happen.

I guess that's why I'm curious about your experiences. I've never been to Japan and I've read enviable reports of your disaster preparedness, but I honestly have no idea how your schools and culture handle tornados.

The founder was very public with other companies in the area about both his policy of firing 10x developers and hiring any warm body that could put a resume in his hand. He told stories at local business meetings of the various people he hired who couldn't find a computer and were fired on the same day. So, when you found out what the corporate culture was like after about a month on the job, you had two options.

1. Stay on for a year. This cemented to every hiring manager that you were a 1x developer (because you kept the job), but absolutely not a 10x developer. You might get a junior developer position somewhere else, but never more than that. 2. Immediately quit the job. You now had a one month stint at the firm on your resume. Every hiring manager in town knew that 5% of people with a short stint were good developers and the remaining 95% were people who just finished "COBOL for Dummies". You'd best just leave the gap in your resume if you didn't want your resume in the trash.

1. The employee was a vain troublemaker who had over-value what they were worth in the market. Firing them would not only remove an inefficiency from the system (as they were likely not to work as hard if they believed that they were underpaid), but it would also helpfully remind the other developers that they were all expendable.

2. The employee was a 10x developer who was vital to the company processes and could command a much higher salary somewhere else. Even if you gave them a raise today, they could be hit by a bus tomorrow. The best course of action was to simply rip off the band aid. Fire the employee, have security immediately escort them from the building, and begin triage to ensure that the critical systems that they wrote/managed could be handled by the next resume in HR's pile.

The line I will always remember is: Developer are like eggs. They are heavily undervalued, but also will crack under too much pressure. Thankfully, like eggs, you can buy them for cheap in packs of twelve, so it doesn't matter if you break a few.

I once had a teacher claim that people who claimed to have aphantasia were lying, because those people have read books and it is impossible to read a book without picture the scene in your mind's eye. Are you citing the same source that she was?

I'm still not sure what I'm supposed to be holding onto. Do I briefly cover my head with my arms, then stop covering my head to hold onto the table? Do I hold onto my head while I cover it? Do I cover my loved one's head and they cover mine, sharing our last moments in a loving hold?

Now I'm beginning to wonder if I made a massive assumption that I would be covering my head with my hands. That's what I would do during a tornado, but maybe I'm supposed to be covering my head with a blanket so my hands are free for the hold on part?

Honestly, my facetious hold my bladder advice seems more apropos than anything I've managed to come up with for part three.

"Traffic is unusually heavy right now due to an accident on Kirkwood. If you want to pick up a pizza from Avers and be home by six, you should leave work in the next seven minutes."

Was it creepy? Hell yes, but at least it was useful. The companies haven't cut back on spying on me, but, in an effort to pretend that they aren't, they've stopped sharing the useful information with me. Instead, they keep it to themselves to mine for the perfect car advertisement to send to a guy who doesn't have a license.

Is it because the word "pig" implies that the victim hasn't kept Kosher and that the scam is god's punishment for that? Is there a general consensus that people who are "butchered" deserve to be murdered? This stigma was obvious and immediate for you, but I'm not picking it up. I don't wish to perpetuate the stigma, but you haven't shared what it is.

I'm obviously missing some context or nuance here, since you're the second person to identify the connotation. Is it the "pig" part?

The web interfaces for both Jitsi and Zoom fail to recognise my web camera. I've gone through the permissions settings a dozen times and Firefox says that it sees camera, but it only displays a black feed. Vivaldi correctly accesses the camera on both sites.

imascientist.org.uk makes it "impossible" to sign up for outreach sessions under Firefox. The div with the sessions has a `max-width` parameter, but the contents are significantly larger than this width, resulting in the buttons being outside the rendering area and inaccessible. I have to go into the dev tools and edit the CSS every time I open the page.

These are just the issues that I've dealt with today. Don't get me wrong - I'm literally typing this in Firefox at this moment. However, it doesn't help anyone to pretend that these issues never pop up. I simply feel that the benefits outweight these annoyances.

The sad part is that many employees have come to the rational and correct solution that the above is not true. Out of the people I've known, more have lost their jobs to the results of C-suite malfeasance (e.g embezzling, illegal behaviour) than have ever lost their jobs to their own actions.

Conversely, unless the organisation you work for is exceptionally incompetent, your own personal failures shouldn't put them out of business. Think about all the cancelled Google projects. If the devs that worked on them had just come into work and played Minecraft all day, Google would still be in business. My personal opinion is that, if the Google Reader devs had never delivered a product, Google would be better off today than it actually is because it wouldn't have such a devoted community angry at it for killing off a beloved product.

The navel gazing framework discussion is like selling your own lotto tickets. If someone's number actually comes, you're on the hook for millions of dollars and probably broke for life. However, a person with a risk taking mentality will recognise that the odds of someone winning the lotto is tiny and, barring that outcome, selling your own lotto tickets is free money.

The school was then always disappointed by by their performance in mathematics competitions. After all, the other teams were "wasting" their times unimportant reading about algebra, geometry, and combinatorics while our team was "practicing" math with hours of manual long division nightly.

The practice is certainly vital, but it's useless without a good text to guide you. Unless you're lucky and grab a good one on the first go, you'll need to read a few texts to find the good one.

I'd say that reading is as important to learning mathematics as breathing. You'll be a lousy mathematician if you spend all your time focused on your breathing, but you'll be worse one if you skip breathing entirely.