Don’t forget your poop plug so the devil can’t turn you gay

Crows and / or ravens (forgive my ignorance)

“Corvids” is a good catch-all

Half-Life

And the , commas with , spaces on , both sides

Depends on the definition of “you”

[email protected]

Point was: most of the time I see someone spending time counting the requisite number of ..s, all they really wanna do is “go back to where I was before”.

cd foo/bar/baz/qux and cd - is better than cd foo/bar/baz/qux and cd ../../../..

cd - helps

Do not nixos-install me without reason

Do not uwsm start select me without valor

Classic

You’re a legend.

A small black stroke on the text helps with legibility.

Thank you for your service.

As in Trump saying “Good — will you be paying me again?”

Transportation expert uses expert-level transportation? Wild.

ideological*

I mean, they definitely had logos. But what about pathos?

Tim “Cook of” Apple

So if library users stop communicating with each other and with the library authors, how are library authors gonna know what to do next? Unless you want them to talk to AIs instead of people, too.

At some point, when we’ve disconnected every human from each other, will we wonder why? Or will we be content with the answer “efficiency”?

The process is supposed to be sustainable. That doesn’t mean you can take one activity and do it to the exclusion of all others and have that be sustainable.

Edit:

Also, regretably, I’m using the now-common framing where “agile” === Scrum.

If we wanna get pure about it, the manifesto doesn’t say anything about sprints. (And also, you don’t do agile… you do a process which is agile. It’s a set of criteria to measure a process against, not a process itself.)

And reasonable people can definitely assert that Scrum does not meet all the criteria in the agile manifesto — at least, as Scrum is usually practiced.

It’s funny (or depressing), because the original concept of agile is very well aligned with an open source/inner source philosophy.

The whole premise of a sprint is supposed to be that you move quickly and with purpose for a short period of time, and then you stop and refactor and work on your tools or whatever other “non value-add” stuff tends to be neglected by conventional deliverable-focused processes.

The term “sprint” is supposed to make it clear that it’s not a sustainable 100%-of-the-time every-single-day pace. It’s one mode of many.

Buuuut that’s not how it turned out, is it?