My brother was/is allergic to peanuts, and it was first noticed in ... 1978 I think, when he was 2. Horrible reaction, nearly died. I'm older, don't have it. A brother younger than both of us also has no allergy to peanuts. We were all raised in the same house, same foods, no bubble environment (the 70s were pretty unbubbled for most kids).
He also had a grape allergy, and reaction was quite severe, but he seemed to outgrow that by his 40s.
Right, allergies are likely a real thing, but I think there's many things nowadays where as soon as we hear of chances of something we go on this hyper vigilant avoidant mode, and that often makes the chances even greater, counterintuitively.
At some points, some things are bad luck, at least until we truly understand the mechanisms and causations.
Fortunately for food allergies, oral immunotherapy seems to be very effective if you can catch the allergy early (before 2 years old). We did for our oldest and the results are miraculous. It's a ton of work though, and I had more than a few near crash-outs from trying to get an 18 month old who doesn't really like the taste of peanut to eat a teaspoon of peanut every single day. That said, I don't regret it.
Even though we keep an epipen around and we make sure they're not eating peanuts, we don't practice strict avoidance anymore, we don't have to worry about the "processed on shared equipment" warnings, and there's no problem if he touches/inhales/eats peanut, meaning we can eat peanuts around him.
I've been in projects where they're 'on the cloud' to be 'scalable', but I had to estimate my CPU needs up front for a year to get that in the budget, and there wasn't any defined process for "hey, we're growing more than we assumed - we need a second server - or more space - or faster CPUs - etc". Everything that 'cloud' is supposed to allow for - but ... that's not budgeted for - we'll need to have days of meetings to determine where the money for this 'upgrade' is coming from. But our meetings are interrupted by notices from teams that "things are really slow/broken"...
About sums up my last job. Desperation leads to micromanaging the wrong indicators. The results are rage-inducing. I am glad I got let go by the micromanagers because if not I would have quit come New Year.
I'm one... I was introduced to JB by someone else who paid out of their own pocket 18 years ago. I thought he was crazy... then a couple years later I tried it in earnest and it was ... life (well career) changing.
similar. i guess i got a bargain cause I got 2.5 hours in ER with a couple tests for only $4k! Adjusted down to .. $2300 after 'insurance' (which I was paying $500/month for, with a $7k deductible).
API changes breaking BC feel like they should be using versioning. I don't see enough people putting versioning support in to their API stuff at the outset. I've been chastised for doing that with "YAGNI". And then... one day, we do need it, and trying to introduce versioning support becomes... that much harder.
petrol is one of the few things we buy that has tax built in. you pump $23.72, that's exactly what you pay. You prepay with cash - you're having to estimate what, say, $15 will get you. Delta of $2.80/gal vs $3.30/gal - yeah, it's a bit different, but nothing is hidden.
Sales tax on literally everything is fairly different state to state (and within sometimes) but petrol is a major daily thing that is tax inclusive.
I had this issue during a job interview exercise. Their "follow these steps exactly" were simply broken. The root cause was that they were having people re-use the same shared remote amazon desktop system. Each candidate got their own home directory, but they wouldn't just reset the image between candidates. The person before me had used up 98% of the drive space. When I followed the 'step by step' guide, nothing worked, because it was out of drive space, but... I wasn't seeing 'out of drive space' messages directly - I was seeing their 'setup shell scripts' looking like they worked, but then nothing did.
I honestly thought this was some sort of trick exercise to see how I deal with broken processes, and I was writing fixes to their docs and shell scripts to deal with error states, and reported back to the person. I initially got a 'no, this isn't that sort of test. the docs work, just follow them'. After more back and forth, I got 'oh, I see that might be broken, yeah, just carry on'. I fixed what I could, made a couple commits back up, but was then told my commits needed more context, which I then added, and promptly never heard back from them again. Until... weeks later, HR reached out to say "we've gone with someone else". I recounted this story and got at least some semblance of feigned shock of 'that's not how any of this is supposed to go'. I'd kept some screenshots and emails, but they didn't care to go down that road.
tldr - Employers giving tests, please run through your own exercise processes now and then (or maybe even automate them with some smoke tests).
I don't have an employer, but I still only have one company selling health insurance in my county, so... that's all I can buy.