The most annoying thing about a lot of these is that tutorials are “minimal viable setup” sorta things. Like “now you have it setup, make sure you tune it for production”

Dude I’m already in pain from trying to serve these models and you just have to go rub salt into my eyes. “Simplify your stack with <Tech>” they said. “Share your resources effectively and easily with <Tech>” they said. “Here’s your fuckin’ ‘Hello, World’ now GRTFM and buzz off” they said.

Working close to the metal do be like that.

oFCoURsE! And the dot at the end with no file type extension? Also intentional.

stOcHaStIC-l33t-CasE FTW yizzo.

Sorry for your loss. I hit myself with the ‘rm -rf /*‘ several years back when I was actually trying to do ‘rm -rf ./*‘.

Now I do ‘ls’ instead of ‘rm’ just to make sure that what I’m deleting is what I’m intending to.

Figured I was very lucky that it was just on my own workstation and not on any of the servers I was tasked with maintaining. I lost a day or so of work. Had it been our dev server? Would’ve destroyed my team for a while.

I work for a large enterprise and build ML model monitoring pipelines fairly frequently—this will be a more in depth but similar use case to what you’re asking.

We use Grafana (visualization) and Prometheus (timeseries db)—they’re built for this use case exactly. Tons of info out there on how to build, configure, connect to your sensors, and deploy it.

sudo chmod 000 /

I call it N Jinx. Always have and I’ll never be convinced otherwise that it’s not.

Eh I just misspelled it, the spirit, pronunciation are still there. I consider the chain in tact.

No, you’re thinking of a dead lach. A deadlock is an anti folk music pioneer—not really dead yet though he claims to be dead inside.

Who can get there first?

Sometimes old software just has too much legacy spaghetti written in to really build from though. Starting from scratch gives new ideas room to breathe and grow that might otherwise be impossible to implement in the previous framework—which while probably useful can also be stifling. See the reason why Wayland is being written to replace Xorg.

I feel so compressed.

I don’t think an SSD is the right choice here. SSDs have a limited lifespan that’s majority driven by the number of writes that happen to a certain block. Reads are cheap and near infinite though.

When you’re talking about a Lemmy instance, mail server, etc. my mind thinks this is likely to be many writes with several read-once ops. This is a better use case for a HDD.

A media server that oriented towards most consumption (reading) would be better for SSD.

deleted by creator

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

I like draw.io for process diagrams.

I figure I can probably convert about 10 kg into manure before it autoconverts into compost. Which is maybe even a worse problem.

Would you rather have 100,000 kg of tasty supreme pizza, or 200 kg of steaming manure?

Choose wisely.

Some people use git to flog, though. See

git blame

Every time.