Also PRISM. Maybe the third—wait, wrong side of the array—worst.

I like draw.io for process diagrams.

Dude, Harry and Tuvok were not just friends. They just don’t show what happens off shift in some obscure corner of the lower decks.

You mention ThePicardManeuver but leave out Stamets@lemmy.world???

When I’m prototyping some model deployment/application/backend, I choose Ubuntu. I’ve also chosen Debian Stable before.

When te decision has been made to actually write the fucking thing for real enterprise deployment, it’s always Alpine Linux so that we have fine control over literally every aspect of the image.

I’d never recommend Alpine for any other use case, tbh.

It was /c/amotio? Pitchforks out; GET ‘EM!

Unused kitty litter works great.

Used kitty litter probably also works. Hey, I don’t judge others’ fetishes.

Xean Connery hates this simple trick.

Because starting with ‘X’ does not guarantee the ‘sh’ sound. See ‘xylophone’, ‘Xavier’, ‘Xenon’.

Xitter looks like ‘exiter’ to me.

LoRA models still have the underlying fully trained base model underneath; it is not a complete replacement or complete modification of the model weights.

Musk has brought a lot of visibility to Tesla over the years, which it has benefited from, but make no mistake—he didn’t build Tesla. The engineers, scientists, developers and technicians at Tesla built Tesla.

Tesla has outgrown Musk. The board of directors, and the shareholders, need to see this and cut him loose. Let him grow SpaceX and xAI the way Tesla has. Let be an incubator and a hype machine—that’s what he’s good at—rather than an accelerator.

A true Debian user would never tell us that they use Debian. They would say they use Debian Testing’. BTW.

X

I’m in this picture and I resent it.

“Spilt milk under the bridge.”

A wizard wears his shirt neither over or under his robes. He wears it precisely where he wants to. Which, in my case, is instead of underwear. Would you like to see?

No, this is incompetent management.

Senior engineers write enabling code/scaffolding, and review code, and mentor juniors. They also write feature code.

Lead engineers code and lead dev teams.

Principal engineers code, and talk about tech in meetings.

Senior Principal engineers, and distinguished technologists/fellows talk about tech, and maybe sometimes code.

Good managers go to meetings and shield the engineers from the stream of exec corporate bs. Infrequently they may rope any of the engineers in this chain in to explain the decisions that the engineers make along the way.

Bad managers bring engineers in to these meetings frequently.

Terrible managers make the engineering decisions and push those to the engineers.

We haven’t learned our lesson about Unix time overflow yet, have we? Better up it to 64 bit signed, just to be sure.

I’m not your bro, bruh.