queerlilhayseed

I don't share your concerns about the profession. Even supposing for a moment that LLMs did deliver on the promise of making 1 human as productive as 5 humans were previously, that isn't how for-profit industry has traditionally incorporated productivity gains. Instead, you'll just have 5 humans producing 25x output. If code generation becomes less of a bottleneck (which it has been doing for decades as frameworks and tooling have matured) there will simply be more code in the world that the code wranglers will have to wrangle. Maybe if LLMs get good enough at generating usable code (still a big if for most non-trivial jobs), some people who previously focused on low-level coding concerns will be able to specialize in higher-level concerns like directing an LLM, while some people will still be writing the low-level inputs for the LLMs, sort of like how you can write applications today without needing to know the specific ins and outs of the instruction set for your CPU. I'm doubtful that that's around the corner, but who knows. But whatever the tools we have are capable of, the output will be bounded by the abilities of the people who operate the tools, and if you have good tools that are easily replicated, as software tools are, there's no reason not to try and maximize your output by having as many people as you can afford and cranking out as much product as you can.

What amuses me about this take is that the jokes about the song being played all the time fall prey to the exact same overexposure mechanism that made people dislike the song in the first place. As the song gets more commonly perceived as being overexposed, the idea of its overexposure itself becomes more and more popular until it is itself perceived as overexposed. Like a memetic echo.

I'm just making stuff up, but your comment made me look it up and of course it's also the name of a controversial youtuber who blew up, coincidentally, around the same time the trebuchet did. Learning all kinds of internet history today.

The CPU malloceth, and the CPU freeeth, according to the divine Program. And lo, the virtuous array shall enter into the ofstream and be saved, while the wicked shall be dereferenced for ever.

I'd expand on your last thought to say that all art is a compression tool for meaning. Got an idea in your head you want to communicate? You've got your body and your environment to work with, good luck. Words, images, dance, sculpture, they're all noisy channels we use to try and get information from one brain to another.

I think if we're ever going to find an answer to "Why does the universe exist?" I think one of the steps along the way will be providing a concrete answer to the simulation hypothesis. Obviously if the answer is "yes, it's a simulation and we can demonstrate as much" then the next question becomes "OK so who or what is running the simulation and why does that exist?" which, great, now we know a little bit more about the multiverse and can keep on learning new stuff about it.

Alternatively, if the answer is "no, this universe and the rules that govern it are the foundational elements of reality" then... well, why this? why did the big bang happen? why does it keep expanding like that? Maybe we will find explanations for all of that that preclude a higher-level simulation, and if we do, great, now we know a little bit more about the universe and can keep on learning new stuff about it.

Yes, kind of, but I don't think that's necessarily a point against it. "Why are we here? / Why is the universe here?" is one of the big interesting questions that still doesn't have a good answer, and I think thinking about possible answers to the big questions is one of the ways we push the envelope of what we do know. This particular paper seems like a not-that-interesting result using our current known-to-be-incomplete understanding of quantum gravity, and the claim that it somehow "disproves" the simulation hypothesis is some rank unscientific nonsense that IMO really shouldn't have been accepted by a scientific journal, but I think the question it poorly attempts to answer is an interesting one.

Thanks! it's probably not the best tool, but it's one I'm familiar with. I love diving into commit histories and reading what developers say in their commits (especially giant corporate private projects where they're so sure no one will ever read them... I read them 👻) and I really wish I could look at, to pick one at random, Tolkien's commit history and see how the work evolved over time. Of course we have his diaries but there's something very specific and personal about seeing a specific change to a line, or a word, that I've seen in code and wish I could see in other written media. That's what I want to capture with my writing. If I ever do publish a book of poetry or short fiction (or a novel, assuming I ever finish one 😓) I imagine I'll cut a release branch for posterity and keep editing them if I so desire, but that decision feels like a long way off.

Long-term, I want to write a tool for collaborative storytelling that incorporates a VCS like git but in a way that's a lot more accessible to writers who aren't also developers. git is a cool tool but it's intimidating for non-devs and with good reason. Part of what I'm doing is figuring out a workflow that works for me, and then maybe I'll build an editor that makes that workflow easier.

I want to give Obsidian a real try. I have seen it around but never used it, because it seems really complicated to operate and I haven't felt like I have the brainpower to really get my head around it, but it looks interesting. Do you use the concept graph and all the other stuff or do you use it more as a plain old editor?

the realpolitik is in Corrections

IME:

I like using commit messages as a a little built-in editor's log; I'm hopeful that in time I'll be able to review the history on a particular poem and see something interesting about the types of edits or editorial choices I make over time. I have a really hard time writing good commit messages for poetry as opposed to code, a lot of the times it's "changed word choice in XXX" or something like that but I want to improve on that. Not really sure what a "good" poetry commit message is but I figure I'll know it when I see it. Or maybe I'll just see a natural trend as my writing matures. But now that the poems are in git, git is part of the medium and the commits are part of the art, and I want to be thoughtful about them. I've always wanted to see the commit history for novels I've read and, if I ever publish my own work (and if I'm brave enough) I want to publish my git repo alongside the finished work.