Right, but saving an edit history of every change to every comment is a geometric increase over just saving the edit to the original comment.

save them… to the database?

Do you want an exponentially growing database? Because this is how you get an exponentially growing database.

xkcd #1105: License Plate

They also don’t have the experience of only seeing half the episode because you were channel surfing, and not getting to see the rest of it until you catch another rerun two years later.

Yes, when there’s a new new guy.

Common practice in most workplaces is to continue the cycle of dumping the shit work on the new guy. But, if you want to build influence, you don’t do that. When the next new guy comes along, you adopt them, you show them how to get things done, and when other people dump shit on them you help clean it up. You don’t do their work for them, but you also don’t leave them to do the work alone.

And you teach them to do the same thing with the next new guy. When they’re up to speed you start load balancing with each other intentionally. They need to leave early for personal reasons one day so you handle some of the extra workload for them. They do the same for you.

(side note - this works when you offer first - you don’t open this by trying to get them to do you a favor first; you will run into people who will take advantage of this and not grasp the concept of returning the favor - when this happens you don’t whine about it, you don’t confront them about it, you don’t even mention it, you just note that this is an indication of that person’s character and you don’t ever offer to help them out like that again - there will be others who understand cooperation and join in automatically, those are the people you make part of your group; so you worked extra one day and didn’t get reciprocation, that’s OK, it’s a cheap low-risk way to learn about who that person is - scratch it off and don’t catch feelings over it, be professional, you still have to work with this person you just don’t have to trust them)

(second note - this does not work for anything that you might be legally liable for - if the other person has to sign their name for the work or is in some other way accountable on record you cannot cover for them and even helping may be problematic, especially in the medical field)

Maybe you’re still shoveling shit, but you’re not doing it alone. If you don’t have a tribe, build one.

And then break the cycle.

And all things end
All that we intend
is scrawled in sand
It slips right through our hand
And just knowing
That everything will end
Should not change our plan
Whеn we begin again

Hmm, but you have to install and run the Python environment for that. AWK is typically present on *NIX systems already. Python seem alike overkill for basic text processing tasks.

It’s comic sans. It’s a crime against humanity.

Just, ah, be careful with DIY laser cosmetic devices, and don’t trust safety goggles that come in the box with them.

This is relatively minor. The bigger risk when running a downstream OS is that the team does not have the finances, the staff, or the broad-ecosystem visibility to support their own security research and development in any functional capacity, and there is an unavoidable delay in integrating security updates from the upstream OS.

This is a big problem. It makes running any small-team derivative OS a high-risk choice.

Um, what’s with the personal attack dude?

It is really nothing compared to what will happen if the current international infrastructure supporting hospitals and food delivery breaks down.

Most people don’t grow their own food, they buy it from a store. There’s about a week, maybe two of fresh food in the system, depending on local population density and available suppliers. Maybe a month or two of dry goods.

Hospitals are highly dependent on consumables to provide care. In a month they’re out of exam gloves, masks, sample tubes, hand sanitizer, antibiotics - then sanitation starts to break down and hospital-acquired infections start to ramp up. Less time for high-value items like anesthetics, immune suppressants and other specialty drugs. The volume of chlorine and isopropyl needed daily just to keep things clean will be a problem. Anything less than immediate life-threatening conditions starts getting turned away because the hospital is a source of danger for otherwise healthy people, and they might not have the resources to provide care anyway. The emergency room runs out of blood bags.

In the present, the things that keep people alive are dependent on just-in-time logistics systems. There’s very little inventory stored anywhere, because it’s cheaper to not store stuff. If the trade relationships break down and the supplies become unreliable, it falls apart. And it doesn’t have to all come to a complete halt for people to die, it just has to become unstable so that sometimes the right things don’t show up at the right places at the right times.

Systemic collapse would lead to orders of magnitude more deaths.

…except for, you know, all the people that die.

…and the penalties are enforced.

noai.duckduckgo.com

“male climate change”?

Is that what you call it when you shrink up because it’s cold?

Analog computers were also bulkier, had more mechanical complexity, and required higher power to operate and generated more heat as a consequence. The Heathkit EC-1 logic circuits operated at 0-100V. There are some real physics problems with scaling analog circuits up to higher complexity.

There’s a food source somewhere. Assuming they’re not getting food from your kitchen (you’re not finding them in the pantry), there must be something else nearby. What’s around? Anything you can get rid of? Old cardboard boxes? Dead plants/yard waste? Pet food?

How old is the house? Does it have wallpaper? If you are unlucky they might be eating wallpaper glue or something like that. Also have you made sure there isn’t a sewage leak under the house?

what could possibly go wrong