Yeah, thise were two things directly aimed at the misbehaviour of the outgoing government.

Ah, those heady days, before shouting "nonsense!" at Jack Straw would gwt you arrested under the (woefully badly-written) Prevention of Terrorism Act. It's almost as though power corrupts (and the office of the Home Sec in particular is enough to break the morals of anyone).

The specific things I recall were the FOIA (which Blair later came to regret; the tine to strike with such things is while the fires of idealism still burn hot) and removing the control of interest rates from the Treasury - the Tories had been royally fucking the economy with that in the years running up to the election. Imagine if Truss had her hands on that lever.

Here's another. You being you isn't a line of defence if someone decides to murder you on a date.

Serious answer then: you won't be fired for being yourself.

When I had this conversation with a trans mate (who had a fucking awful Daily Heil-reading co-worker with no notion of what was appropriate conversation for the workplace) I said, "hang on a moment, isn't [being fired over being out] illegal?" He said, "yes, but it doesn't stop it happening."

I believed him - he was living it, he had the experience. Conversations with him involved me getting smacked in the face with my own privilege on a regular basis. You have it easy.

Once the water companies were privatised, they took out massive loans and performed no maintenance. The loans were purely to pay shareholder dividends. Now they're loaded down with debt.

Atop this, that crumbling infrastructure can't handle the increased water flow that's due to rainfall increases. So there's been a general trend of dumping raw sewage into rivers (the fines are cheaper op ex than the capex needed to fix the situation).

It's parasitic capitalism at its finest.

Incidentally, this kind of passive-aggressive pressure is the kind of thing that might be considered a legitimate security threat, post xz. If you need to vent, vent in private. If "it works for you" but the maintainer is asking legitimate questions about the implementation, consider engaging with that in good faith and evaluating their questions with an open mind.

Which mantra is that? The ellipsis doesn't offer a clue.

Casey's video is interesting, but his example is framed as moving from 35 cycles/object to 24 cycles/object being a 1.5x speedup.

Another way to look at this is, it's a 12-cycle speedup per object.

If you're writing a shader or a physics sim this is a massive difference.

If you're building typical business software, it isn't; that 10,000-line monster method does crop up, and it's a maintenance disaster.

I think extracting "clean code principles lead to a 50% cost increase" is a message that needs taking with a degree of context.

Not "terrible" in the sense the OP meant, but when I went to see "Hard to be a God," 40 people sat down and eight made it to the end.

What are the permissions on the directory? What is command are you running to edit the file? What command are you running to delete it? (Have you got selinux turned on? What filesystem is this directory on?)

Came here to say the same thing. The git book is an afternoon's reading. It's well worth the time - even if you think you know git.

People complain about the UX of the cli tool (perhaps rightly) but it's honestly little different from the rest of the unix cli experience: ad hoc, arbitrary, inconsistent.

What's important is a solid mental model and the vocabulary of primitive and compound operations built with it. How you spell it in the cli is just a thing you learn as you go.

Came here to mention laser cooling; glad someone else got there first.