I like to splurge on a Shackshackshack from time to time.

deleted by creator

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.

They need to tell that to Theodore Ts’o.

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.

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?

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

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.

I’ve worked for startups too; everyone does everything all at the same time! Let the chaos reign! But it is fun in its own way.

I work for a large company now after the startup I worked for was acquired. Hierarchy, bureaucracy, layers, we’ve got it all. For worse and for better though, it allows me to focus and specialize on what I’m awesome at and furgeddaboddit (ahem! delegate) the stuff that I suck at to those who excel at those tasks.

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.

Not on my map! NZ is an Australian conspiracy!

Telling people to suck on Chef’s Chocolate Salty Balls was one of my favorites parts of my fucked up childhood.

Hmm. Attorney charges by the hour and at least 3 discovery hours will be attributed to the time spent learning to exit vim let alone exit with preserving changes.