Instead of reading the article I will tell you why the docs are wrong. It's because most teams don't incentivize writing documentation and a lot of them just don't care. The team guru's job security is predicated on knowing the answer to everything so it's a losing proposition for them. If you write good docs about one of these topics, don't be surprised if they try to find a way to punish you for it.
If you're in an SWE job, only write documentation if someone tells you to. Otherwise, just give up.
I host my own email. I also have a gmail account, that I've had since the beta.
I cannot tell you how many times I have encountered a person that asks for my email and then looked at me confused when it didn't end in gmail, outlook, or something, and then ask me for another email, as if only that would be good enough.
I think lesser known TLDs are the problem. I have had a .net domain and used the email address (and its self hosted these days, which has been a problem with sending to hotmail) and have never had it rejected or confuse anyone.
ON the other hand I had a website with a ccTLD and one guy kept trying to add .com to it - his own country's ccTLD!
I do this often when corresponding with businesses/companies and I've been asked before if I have a similar business or am in their line of work also...
I own my own domain in the .us TLD, and I've been using it for my email for the past 20 years. When I applied for an "Electronic Travel Authorisation" (ETA) to enter Great Britain earlier this year the app flat-out rejected my email address as invalid.
Usually, when that sort of thing happens, I just choose to take my business elsewhere or use my time in a different way. However it really ups the ante when a nation-state refuses entry based on that category of technical incompetence.
When it comes to nation-state I wouldn't consider this example as technical incompetence. I would bet 99% of people with personal email addresses/personal email servers will "just use my old Gmail instead". I'm pretty certain its easier for nation-state to subpoena Gmail or Yahoo, or probably use direct backdoors that don't even require official subpoena, rather than deal with your own email hosting contraption.
I wanted to take a look at Boomi.com but couldn't sign up with gmail, turned on email forwarding for a parked domain to get past it. Stupid behaviour if you are trying to sell a product.
I had websites state that the address was invalid because I didn't have an MX record, despite it not being an RFC requirment.
Also, a lifetime ago, had Hurricane Electric (https://he.net) refuse to accept a sign-up because... I only had one MX record. I added an additional record pointing the same IP, but they weren't happy.. So I allocated an additional ipv4 address to the same server, just to satisfy them.
You really should have an MX record though. Fallback to A is deprecated and really should have been removed by now.
HE provides professional network services and probably, perhaps even contractually, requires you to have two different ways to reach you. Everyone at that level has quick ways to get in contact with all their business partners, usually a phone number that's active 24/7.
Really? I've never really had this. I occasionally get a "huh, is this right?" in person but even that is rare now. And in the past decade, I've had my email rejected by a form maybe, once? twice?
And most of the confusion in person seems to be down to my choice of TLD: .es and .io (I'm neither from Spain nor the Chagos Archipelago).
I've taught people to start with surface mount before. It's really worse depending on what you're soldering. A lot of people doing hardware hacking will get tons of mileage just out of being able to solder on a chip with a soic-8 package. That's easy enough that you can learn it on day 1.
I'm honestly passionate about this topic. For a while, around the time that urinals started to appear without water, I dealt with some serious splashback issues. I forget when I started aiming for the back of the urinal. I'm assuming that's the deflection angle the paper discusses. At one point I realized, I was sometimes getting some pretty bad splashback. Perhaps because I stood close to the urinal. So I asked a colleague. He said he aims for the hole, and was confused why anyone would piss on the back of the urinal. I started doing that -- problem solved. I am for a direct hit, every time. The problem is that some urinals have a protector over the hole to prevent really smart people and children from putting paper towels in there. That thing is dome shaped, and multiplexes the stream like a lawn sprinker.
All of this, would not be necessary, if there were water at the bottom of the urinal.
I don't have much success with using the LLM to make changes to a big legacy codebase. Instead, I use the LLM to gripe about things I don't like in the code. Usually, it is a brilliant commiserator.
If you're in an SWE job, only write documentation if someone tells you to. Otherwise, just give up.
reply