pnutjam

As if you can live anywhere without paying in perpetuity.

If there wasn't an endless drive to increase the value of homes, this would all be moot.

Equity is a red-herring. People just want a place to live. Developers want equity.

Myself as well, but that information is out there and easily found through payroll subscription services.

"To clarify - I think 'able to read and understand most things' qualifies? So - if they needed to read instructions to get to another level in a video game, or read a menu in a cafe, etc? Obviously we are all learning new words all the time. And not every kid wants to read a novel."

Every kid should be able to read a novel, this is a sad commentary on why parents are often poor teachers.

She died at 60, so no eligibility for Medicare or Social Security. That's a nightmare scenario in the good old US of A. RIP

I once plugged a toner into a network patch panel to locate a drop and crashed the AIX system at a medical office. :(

In a past job I took over for an enterprise linux setup where all the log volumes where way too small. It was dozens of alerts every week to just grow the log volume or delete some stuff. It took me a couple years to get everything resized properly and logs rotating correctly. This was around 700 servers with all the change requirements of a heavily audited environment.

on-prem block storage like a Scality Ring is where it's at.

Have you considered doing volunteer work with children. Something like Big Brothers?

Read the act 1 section, or listen to the podcast. This has been tried and it's basically impossible in a capitalist system with local democracy. https://www.thisamericanlife.org/762/transcript

woah... This works in KDE too on linux.

This is an artifact of capitalism driven healthcare. It's only an issue in the U.S. It's the end results of incentive's designed to extract money vs incentives designed to provide healthcare. (i.e. capitalism)

Get a load of Mr. "everything I hate is communism" over here.

It's an end run around re-imbursement rates for insurance and how the pharmacy benefit managers get paid. Basically an artifact of why capitalism sucks.

Sure, all you ever said was you could not believe and you could do remote stuff in person. Way to support your statements.

So you're just ranting, no data and looks like no experience. OK

In person is worse. I've done both. It's noisier, you're crammed into a cube taking notes, etc. If you're going to use remote tools, what's the benefit of in person?

Please elaborate how it's better in person? Remote: I can see and hear the person. I can see their screen. I can copy past back and forth (as can they) through the screen sharing app. I can invite others into the training pretty much instantly. I can send links and commands typed properly in the chat. User can record session for later.

In person: Usually have to face the person or the screen, can't see both. I have to write down commands and pass them, or type them myself. There is a delay finding others if we need to talk to them. More chance to transpose commands incorrectly by the user. Harder to record the session without losing parts.

100% this. Keep an open channel for IM and setup regular shadowing. I've been on both ends, learning and teaching. It's way preferable to have your own computer, shared screen vs trying to look at another screen and taking notes. Remote is better for collaboration and training. Proper documentation is a big part of it, and open channels for IM, like slack.

A culture of good, clear documentation is critical.

And all those cloud compute instances are probably strangled for io if there is any real load. Colocating your own equipment is going to give way better base performance. Compute is not just processor and memory, it's also dependent on network and disk i/o. Disk is often overlooked because modern disks are so fast, people don't even realize it's crippled in the cloud.

Yeah, KRR is bad, but they are just a cog in the machinery of crapitalism.

Just anecdotally, I got 2 of my last 4 jobs by direct applying with no networking, and 2 from recruiters. One internal and one external. The internal recruiter oversold the job and it was not great. The other jobs were all good and about what I expected.

IMO, SUSE does this right. SLES 15 (and OpenSUSE leap) is supported until 2031 and it was first released in 2018.

You do need to apply updates, but that's the point of support. You can take any version of linux as is and run it for 20 years with no updates, no changes, and no support. In my experience, SUSE also rolls from major release to major release with very little problem, so upgrading to SLES 16 is probably an in-place upgrade.

EDIT: also, RHEL never did this right in my opinion. They lock the kernel for a decade, SLES updates the kernel.

citation needed

It's always fun having gun nuts pretend to debate in good faith. Thanks

Same, RHEL says you should be compatible against all minor versions and it doesn't matter if it's 8.5 or 8.6. Upgrades can happen without you noticing, but our software would only run on specific minor versions without investing time and development energy. Several installs I've worked on required an OS rebuild because the version crept into an unsupported minor version.

Vendor support is pretty crappy. By the time you're done gathering all the logs and running out the response time clock you've usually figured it out. Then at least half the time they do help, it's wrong because you're environment has some special requirement.

Oh yeah, that's 100% true, but take a look at the way they train each other.