Ekky

I had quite some beef with the tethered caps in the beginning when they didn’t latch properly, but have since gotten used to them. That said:

• Cap on top -> Funny hat for nose!
• Cap on bottom -> Beard gets to take a moist nap.
• Cap on sides -> Mustache also gets to take a sip!

Obviously not much of a problem. I’d need to clean my facial hair either way if eating ice cream or other messy foods, but cap rotation might not be effective if your “face” sticks out 1-2cm from your mouth.

One could also attempt to rotate the cap in a way to achieve quantum tunneling, but I don’t feel that I’ve achieved that level of “tethered cap proficiency” yet.

I’m pretty sure it’s more like

Junior dev: Got all the nice addons, RGB lighting, only uses dark theme, got all the stickers, works from either a café or moms basement.

VS Senior dev: Works on company standard issue hardware, barely customizes visuals (but got a script which makes a cup of coffee on the shared machine in exactly 2 minutes and 30 seconds), works in shared office, has old rolling cabinet with unknown artifacts last touched 10+ years ago.

Obviously this is an overgeneralization and not a catch-all, you might even say that it’s “programmer humor”.

Stacked on top, and vertical orientation since we’re not doing Java here!

Lol, it is indeed one of the cleaner versions that I remember having seen, nice work! ^, ^

But Admiral Patrick, how dare your ancient memes from times long forgotten not meet our modern expectations? Do you at least have a proper shitposting license?

I’ll post mine as reference, may you gaze upon it and ponder the shortcomings of your horrible artifact-ridden memes!

AI: “Can I copy your work?”

Phil: “Just don’t make it obvious.”

AI:

“Fixed issue with ssl python libs,” or “Minor bugfixes.”

In other news, never work more than one person on a branch (that’s why we have them). Make a new related issue with its own branch and rebase whenever necessary, and don’t even think about touching main or dev with anything but a properly reviewed and approved PR (in case they aren’t already protected), or I’ll find and report you to the same authority that handles all the failed sudo requests!

Also, companies that disable rebasing are my bane. While you can absolutely do without, i much prefer to have less conflicts, cleaner branches and commits, easier method to pull in new changes from dev, overall better times for the reviewer, and the list goes on. Though, the intern rewriting multiple branches’ history which they have no business pushing to is also rather annoying.

You are correct! It sets HEAD to the first commit and then force pushes, deleting everything after HEAD.

Though, it only affects the currently selected branch.

like this?

# Let Git take a rest with some yummy awk chocolate logs with delicious nuts and seeds, and don't be pushy!
git reset --hard $(git log --reverse | sed -n 1p | awk -F "[ ]" '{print $2}') && git push -f

EDIT: Don’t actually run it.

Or make a shortcut/link in the readme to the newest release of the most popular OS’s.

A decent release page tends to contain all kinds of files for different OS, so ‘regular’ people who just want the .deb or .exe would likely become confused regardless.

Right, my bad. I thought you were explaining turbines in relation to the post, which would indeed have one attempt to run sand through it if not used with either liquid or steam.

I also wrote turbine and generator separately, as, as you stated, turbines and generators are not the same. I, in turn, hope I didn’t give the impression that they were.

I fully agree about the system as a whole better being described as a battery, which usually includes generators of some sort to convert the stored energy back into electricity.

And yes, this is a rather precarious article, which also is why I wrote the half-question half-joke about unnecessary conversion steps using turbines.

And that’s my confusion, why use a turbine (connected to a lift) to turn the heavy weight into a flow of steam or liquid, presumably to convert this flow to electricity using another turbine with a generator connected to it, instead of simply converting the heavy weight to electricity using a lift (or corkscrew) to turn the generator?

This is, of course, assuming that a turbine only is a turbine when it is driven by steam or liquid.

I guess the publishers of the article either got the definition wrong, or there’s a less used definition of turbine which I am not aware of.

But isn’t the definition of a turbine “a type of machine through which liquid or gas flows and turns a special wheel with blades in order to produce power” with the “power” (aka. rotational energy) going to a generator?

Where does the liquid or gas come from? Isn’t this battery supposed to lift heavy, solid objects?

It doesn’t outright state that it uses solid weights, but their illustration looks more like they’d use a lift with sand or weights, and not a turbine with liquid or steam:

Very interesting, and good to hear.

Though, I’m not sure why they would drive a turbine to drive a generator, instead of just driving the generator directly. Their illustration doesn’t show any turbines either.

Those actually match somehow, I mean:

“Quick, we need to hold back the invaders in sector r5!”

“Invaders in sector r5? A quick release of the airlock oughta fix that! Also, Jimmy, could you go fetch me the BIG welder?”

They didn’t even use pictures of the cases, they just write about gardening with a picture of proper gardening tools.

For those wondering how to exceed the 70 (80) recommended character limit and still follow best practices:

1. Write the title on the first line, keep below 70 characters.
2. Make two (2) newlines
3. Write one or more descriptive paragraphs.

The first line will be shown as commit message, and the full text can usually be viewed by checking out the commit. Sentences can span multiple lines, but try to keep the line length below 70 characters for best readability.

This off the top of my head, so feel free to correct me if I’ve misremembered the best practices.