Also: https://geohot.github.io//blog/jekyll/update/2025/02/19/nobo...

Apparently if we, the poorer ones, win the war of attrition, the problematic ones that own everything will resign to golf. Or something. Getting financial planning from a lottery winner.

> I dream of a day when company valuations halve when I create a GitHub repo. Someday.

Isn't that exactly what Anthropic did to the SaaS sector? Taking the "I can replace you with a very small shell script" line from BOFH lore (except that it was a bunch of SKILLS.md files, not shell scripts) and making it real.

Hard to say. SaaS is dead, long live SaaS.

Interesting consideration, 'mandates' and all. Definitely in camp 'toss the output', here. I think I'll see 'morality' leaving when $EMPLOYER fires 'professional discretion'... forcing usage and, ultimately, debasing the position.

edit: Peer said it well, IMO. The consequences aren't really yours. Also: something, something, Goodhart's Law.

When you hear "left behind", remember: is 'it' going to places you want?

And if it's going to get easier and easier for my work to be performed by AI, then what does it mean for me to "keep up"? Do I just need to create more slop than anyone else?

Excellent consideration, probably. Sounds like a lot to do for very little in return. I'll leave with this, a sort of sick joke given context:

    Quit when the work is done

Fortunately my job is not based on generating plausible-sounding bs, so I should be safe.

Hear, hear. Wish you the best! There's a whole list of other silly games to avoid, unfortunately. Namely, "up or out".

For instance, I want to engineer [more]. Closer to management or sales due to scope creep. At this rate, by career-end, I'll be operating a small country by myself.

The purpose of a system is what it does.

'Same thing', hah. This was edited out, but I'm quoting it anyway:

> I should trot out all of the justifications here.

I'll start: personal use instead of profit. Certainly a difference, not convinced justification is required or even advisable.

In the US it's common to either negotiate 'differential' pay for the responsibility, or as one might see in this thread, get suckered into it for free.

Community planning another derivative

Trusted boot is here to ensure you will only boot Microsoft-blessed Linux distro and will have no way to modify its binaries.

In this room? Over my dead machine(s), firmware toggles, and 'mokutil'; secure boot isn't that bad, yet. They're pushing, our move. Can't say I know a good one, long term.

No complaints here, I use a Framework Desktop with this chip. 32G given to RAM and the rest plays VRAM. Can use large models like 'gpt-oss:120b' fine. Splurged and got a second SSD for mirroring, hoping to speed up reads/model loads. Haven't tested this for efficacy, but it also gives redundancy. Shrugs!

Haven't paid a subscription in years or even signed up for $EMPLOYER offerings; handles the rare outsourcing well enough.

The first taste is free, eh

I have to say something my Dad used to say, hope this doesn't land poorly: "they can want with one hand and shit in the other, see which fills first."

Generally agree with the peer comment, carrot vs stick applies (ie: 'safety'). There are more, arguably better, moves. Demanding juice from a husk, hmm. Selecting for fresh graduates/those without leverage, still, I see.