They are correct!

Are the wheels rotating in the wrong direction? I stared at it they seemed to reverse. Perhaps a bit of a optical illusion.

Looking at the SVG, the direction is missing but the default is clockwise. So I'd say it's good!

Exactly. I've referred to Ikea as the MacDonald's of furniture. Which is a little harsh and I do own a few pieces.

I've heard of people 'walking' old hard drive cabinets by fine manipulation of the read/write heads.

(submitter here) I wonder whether this is related to Amok (also Malay origin). Also related (probably) is The Jumping Frenchmen and Tourette's.

https://en.wikipedia.org/wiki/Amok_syndrome

https://en.wikipedia.org/wiki/Jumping_Frenchmen_of_Maine

There were plenty of conspiracy sites pre-2000. I think a lot of them shared mindspace with USA late night talk radio. Also, usenet.

You could run rsync with -b --backup-dir=something-$(date +%Y%m%d.%H%M%S) every few seconds. Or fired off with inotify.

It does (let you change history), but in a tamper evident way.

It's two different ways to see the same thing.

Basically, almost everything is immutable in git, apart from tags and branches: these are mutable pointers to immutable commits.

"Don't come to me with problems, come to me with fixes." has always been a thing. You shouldn't take it too literally or personally. For "fixes" read alternatives or suggestions. e.g. hook in a senior engineer that you know is intimate with the system.

I would argue the difference is that upstream is well known for being defensive about their ideas and pushing back.

On LKML you might get cursed out, but if your fix is solid fix, it has high chances of getting through. Regardless of how true it would be in reality, the atmosphere created by upstream is that I do not expect the same with journald unless you convince redhat management

Indeed. It also means "don't come to me with problems alone." Yes, one can come with a problem, but the exhortation is to come with possible solutions as well and seek guidance on which one is best.

Yes, a lot of awful practices have always been a thing.

> e.g. hook in a senior engineer that you know is intimate with the system.

unless, of course, you don't know said engineer because you don't even work in the same company, you're a just a user seeing a problem in an app you use

> unless, of course, you don't know said engineer because you don't even work in the same company...

Or they work in a different part of the fairly-large company that you both work for.

I guess emmelaich either missed the part of my commentary where I talked about handling inter-organization communication, and/or has never worked at a company where it's simply impossible to know everyone who could reasonably be relevant to the stuff that the company works on.

So put out feelers. Ask everyone if they know anyone....

At least triage it with your best effort.

And it's always been cope. Only the worst kind of person would rather not know about a problem if it's not already solved for them.

lutusp here on HN