spitchell

@spitchell@indieweb.social
48 Followers
138 Following
704 Posts
I changed the way I work a couple of months ago to follow this advice, it made a big difference and my productivity went up by miles.
You shouldn’t use an em dash because people think it might have been shit out by an LLM — over my dead body!

I see people talking about "reach" and "engagement" and "algorithms" and whatnot on X vs Bluesky vs Mastodon and I feel so lucky that I have no commercial needs whatsoever.

It's 100% a feature for me that unless I actively include a bunch of hashtags no one will ever see my vapid, drunken, digital utterances.

#VapidDrunkenDigitalUtterances

I "uninstall" copilot from my teams sidebar every day, and the next day it's back.

If I'm also actually using it on purpose, however tentatively, surely it's just a matter of time before my resistance begins to crumble and I just give in to the need to rely on this bullshit for one reason or another, like I did with self service checkouts.

I feel like a frog being boiled.

Recently I've used a "AI" to generate mock data in a specific json schema, and it worked great.

I've also used it to produce an exhaustive list of handwavy arguments for a particular software architecture I want to critique.

In both cases I'm leaning into LLMs' specific ability to come up with convincing bullshit, but even still I'm troubled.

I am proud to consider myself a bloody-minded, socialist refusenik. So I'm obviously staunchly opposed to this ubiquitous commercial shoehorning of LLMs into every aspect of my experience as a web user and a frontend developer.

But I was bloody-mindedly opposed to self service checkouts for several years, until they became tolerably usable and the shops became intolerably understaffed, and now. I use them every single day.

Look, I know AI is controversial, but just for a moment, let's set aside our preconceived notions, our biases, the environmental impact, the massive cost to train and run models, the labor exploitation, the intellectual property theft, the inaccuracies, the mania it causes in users, the destruction of search, the deskilling of professionals, the devaluation of creative work, job losses, and lack of economic value from enterprise implementations.

Wait, what were we talking about?
Wait I think I withdraw my above statement because "demand chain" / "software demand chain" is just too good
At work we have started a new project called "Hot Chocolate Leather Queen" with sub projects like "transfemme" and "black justice". It has nothing to with any of that. We named it that to keep the prudish AI bots from stealing our work.

It takes a lot of energy to believe things that you know really aren’t true.

#ActuallyAutistic #EnergyManagement #AuDHD #BurnoutRecovery #AutisticBurnout

×
Wait I think I withdraw my above statement because "demand chain" / "software demand chain" is just too good
@mcc and the people making demands of that chain? We call them “chain yankers”.

@mcc "software demand chain attack" also works well

(it's a little "dragonball Z" but that may be an advantage)

@mcc Goldish Lookin Chain.
@mcc software alms race
@mcc it also works really well at exposing the attack surface and whose fault it is. "It's a demand chain vulnerability because you went out of your way to obtain code from some random unpaid unknown actor and run it within your machine. You moron"

@elrohir It's not like there are greater assurances provided if the code is written by some known actor who/that gets paid.

@mcc

@mkj @elrohir when i pay someone money i expect i get assurances in return
@mcc @mkj @elrohir Clearly that is not the industry norm these days...
@dalias @mcc @mkj @elrohir At least you have *some* influence on how much time the person spends to work on the project.
Not that this wouldn't still lead to the situation that companies ask for way more than they pay for.
@mcc but notice that it also inverts some meanings: a healthy dema d chain is _not_ a good thing :)