I really like fly.io posts, they're usually written in such a way that feels so human. I used to read all of them, because the writing was interesting, and secondarily sometimes the topic was.
Except seeing sentences like this:
> The difference is that a Sprite now stops and says so instead of carrying on with a disk it can’t vouch for
Makes it feel distinctly LLM written. Maybe I'm being RL'd to identify LLM authorship, maybe the author was RL'd to write like that by reading so many Claude-written works, but I'd like to see the humanity of fly.io blog posts come back.
I wish we'd stop getting replies like this to articles. It's just as tiring as LLM written articles.
People seem to forget that LLMs copied human writing. They also tended to copy people with more proper or formally trained writing styles. There are so many journalists and writers that talk about how they've had to 'stupify' how they write so they don't get accused of being an LLM.
It's like we're running idiocracy on fast forward.
Because as being critical in those instances is more like going to mcdonalds and complaining about burger not being cooked to your specs. No one says you can't, but it does get tiring.
people are just going to have to turn the accursed spell-check off and start writing like psychos again. said modality was second nature online for like the first 15 years of the web. phones ruined us
It is always worth remembering that LLMs use certain phrases and patterns because many source materials in the training set did. One or two smells does not a cesspool make.
As anti-AI as I am, people pointing out that they've spotted an AI are getting quite tiresome too. If you think people won't spot it without you telling them, then it is good enough for them no matter who or what generated it.
A story which may or may not be based on lived experience: one day a Sprite stops booting. JuiceFS is asking object storage for a chunk and getting a 404. We wanted to go fast, so we ran JuiceFS in writeback mode. It records a chunk in its metadata first and uploads the bytes after. If the machine is killed at any time between those two steps, the metadata points at a chunk that doesn’t exist.
So we built a harness that drives fleets of Sprites through write, checkpoint, sleep, wake and restore, over and over, verifying every byte that comes back. We pointed it at 400 JuiceFS Sprites for about 5,000 cycles. A nonzero number of them permanently lost the ability to checkpoint. Well … fuck.
Enter: the Sprites Block Device (SBD). It takes a bucket and presents it to the Linux kernel as a block device, over NBD. The Sprite formats that device as ext4 and mounts it, the same way you’d mount a disk on any Linux box. Duh.
This blog has has a strange vibe like "the last BRAWNDO we made in a bathtub may or may not have killed some customers lmao, try NEW BRAWNDO 2.0 TODAY!" that I didn't realize could work for corporate messaging around an in-house CoW cloud filesystem.
I really like fly.io posts, they're usually written in such a way that feels so human. I used to read all of them, because the writing was interesting, and secondarily sometimes the topic was.
Except seeing sentences like this:
> The difference is that a Sprite now stops and says so instead of carrying on with a disk it can’t vouch for
Makes it feel distinctly LLM written. Maybe I'm being RL'd to identify LLM authorship, maybe the author was RL'd to write like that by reading so many Claude-written works, but I'd like to see the humanity of fly.io blog posts come back.
I wish we'd stop getting replies like this to articles. It's just as tiring as LLM written articles.
People seem to forget that LLMs copied human writing. They also tended to copy people with more proper or formally trained writing styles. There are so many journalists and writers that talk about how they've had to 'stupify' how they write so they don't get accused of being an LLM.
It's like we're running idiocracy on fast forward.
Why? Why should we give up being critical of things we read?
Because as being critical in those instances is more like going to mcdonalds and complaining about burger not being cooked to your specs. No one says you can't, but it does get tiring.
people are just going to have to turn the accursed spell-check off and start writing like psychos again. said modality was second nature online for like the first 15 years of the web. phones ruined us
It is always worth remembering that LLMs use certain phrases and patterns because many source materials in the training set did. One or two smells does not a cesspool make.
As anti-AI as I am, people pointing out that they've spotted an AI are getting quite tiresome too. If you think people won't spot it without you telling them, then it is good enough for them no matter who or what generated it.
A story which may or may not be based on lived experience: one day a Sprite stops booting. JuiceFS is asking object storage for a chunk and getting a 404. We wanted to go fast, so we ran JuiceFS in writeback mode. It records a chunk in its metadata first and uploads the bytes after. If the machine is killed at any time between those two steps, the metadata points at a chunk that doesn’t exist.
So we built a harness that drives fleets of Sprites through write, checkpoint, sleep, wake and restore, over and over, verifying every byte that comes back. We pointed it at 400 JuiceFS Sprites for about 5,000 cycles. A nonzero number of them permanently lost the ability to checkpoint. Well … fuck.
Enter: the Sprites Block Device (SBD). It takes a bucket and presents it to the Linux kernel as a block device, over NBD. The Sprite formats that device as ext4 and mounts it, the same way you’d mount a disk on any Linux box. Duh.
This blog has has a strange vibe like "the last BRAWNDO we made in a bathtub may or may not have killed some customers lmao, try NEW BRAWNDO 2.0 TODAY!" that I didn't realize could work for corporate messaging around an in-house CoW cloud filesystem.