Yes, but HN isn’t made up of children. The vast majority of people here are adults, a population in which Covid-19 is a risk for a large proportion. People aren’t talking about children and saying “you’re afraid of the sniffles* (* is only sniffles for children)” is disingenuous.
The “selfish and myopic” people I know in states that don’t have mask mandates have happy kids who go to school and can look at each other’s faces and grow as humans.
Here in NYC we have woman yelling at kids to keep their masks on and they are in and out of school on a whim.
The particles are floating around in the air. They don’t hit the glass and turn around and go home, they continue to float and a draft or whatever will disperse the particles throughout the room.
Who gets to decide what size interior is ok? Or what crowded is?
It’s all arbitrary and you all fell for it.
Just let omicron spread, accept it’s another seasonal flu, and move the fuck on.
To be fair, I wasn't referring to my own personal risk tolerance but I guess trying to explain a seemingly arbitrary rule... I haven't eaten at a sit down for the last two years because I have small children and expecting them to follow any sort of strict masking protocol is unrealistic.
I also have multiple close family members who work in ICU and healthcare and I really don't think you want Omicron to spread faster than it needs to... That's an extremely shallow selfish mindset.
Edit: Just wanted to share an article from yesterday on the state of hospitals. I have friends/family that are super badass just like you, until they get in a car accident and need a bed at the ER. All the sudden shit gets a little more real and personal...
https://www.npr.org/sections/health-shots/2022/01/11/1071568...
I work on a massive CMS and he’s correct. There is an insane groupthink going on in webdev.
Another team in my org has spent a year reinventing our client side js so that our templates are now mixed with the svelte runtime. All to render/update cards on the page that can update when an api pings the page.
So 6 months later they’re still building the svelte integration and have only shipped 2 pages to users.
This is a cms where you should be able to create any page via a combination of SSR components but no, now it’s a mix of SSR, SSR svelte within handlebars, and client side svelte. So the edit ui is now a fragmented mess of parts of the page that can and can’t render, ruining the default model of the cms all because they couldn’t bear to write vanilla js. They also added react the year before and now it just sits there decaying.
I'm not sure if this one org making a mess is good evidence that there is groupthink occurring in the entire industry. There are places that are using these frameworks well, and it really does improve productivity.
Reducing your website to something that can essentially be served straight out of s3 buckets + lambda functions for the few interactive elements your site has (e.g. newsletter subscription, contact form) will reduce your hosting bill and attack surface, but increase operational complexity.
The key thing behind the "headless CMS" fashion is that most people severely overestimate the amount of cost reduction and underestimate the impact of something breaking down in the backend side as well as the engineering cost.
As if "devops" were a job... at most companies the sad reality is that the ops team gets fired and the developers who often enough don't even have more understanding of a Linux shell than ls/cd/cat/rm get told "you're also doing ops now, have fun!".
Inevitably, issues will plop up - hacks, data loss, site going down over the weekend because there's no 24/7 on-call any more - and then management comes down to the devs and whines "what's the cause of problem X"... and fires the rest when they say "we're developers, not SREs and server administrators".
I’ve seen the transition occur in my company where DX is trumping backwards compatibility, “simplicity”, and inter team cohesion.
If you can’t bother to write the if statement that guarantees backward compatibility and follows a defined standard in use for almost 20 years, you are a horrid engineer IMO.
This is why there’s a general trend toward all things becoming complicated, brittle, and shitty.
Hopefully nobody is writing if statements in code to handle backwards compatibility. That would be terribly unmaintainable. This should be handled at the compiler level. In javascript world, it is fairly simple to use Webpack or the like to target whatever browser versions you wish to support.
If you're not using a compiler, you should definitely not use the latest and greatest features, unless you are well aware that you will not be supporting older browsers.
That’s literally how all polyfills work. They first check if the thing is there, and if not then implement it.
And in this case you can simply do an if statement with (first && first.second && first.second.third)
My point being, writing one long line is how the language inherently works. Use that instead of the new feature that only ships in new browsers. I’d still be upset if one of my teammates added an entire bundling system so they can simply write fewer lines for such simple menial aspects of the code. Forest for the trees.
People end up waiting until standup to ask questions, creating a culture that doesn’t simply message one another for simple things. If something is brought up in standup, now product and project mgmt will want to understand and weigh the value of something that could literally be as simple as, “I need access, how do I generate a key?”
Also I hate being interrogated every morning about what I did the day before.
Daily standup removes the need to remember anything, or even picture the system/ product in your head because you can just ask someone else every day and get what you want. No need to think! Process over people!
Stand-ups in general are cancerous enough to warrant an outright ban. That way, if you do have them they have to be conducted clandestinely and very quickly.
I recently watched some state level testimony from nurses and they said something along the lines of, “our staff, nurses and doctors, are unaware of or trained to use VAERS”
