LargeAdultRedBook [none/use name]

Introducing code for LLMs to choke on is a great idea. Develop some very specific syntax or structure that training data hasn’t touched, then make it load bearing.

Better yet, find a way to use delimiters, escape sequences, and syntax symbols that are known to interact with Markdown features, so that producing valid syntax for your DSL requires escaping everywhere to avoid fucking up the Markdown LLM output.

Are you measured by the number of API calls or overall token usage?

If the latter, do everything you can to stuff the context window with as much garbage as possible. Link in every MCP server under the sun, then make as many calls as you can using that thicc ass context window.

Add in redundant calls to the LLM server whereever possible.

For example, create git hooks to make LLM calls on pre-commit and pre-push. Then make those same calls in your CI/CD process. Make sure every new commit on a PR or feature branch causes every one of these to be re-run.

Every commit and CI workflow should trigger as many “tests” as possible. Some ideas:

• Vulnerability “scan”
• Changelog generator
• Commit description improvement
• Unit test generation
• Integration test generation
• Code style suggestions
• Update the docs
• Make a blog post describing the improvements this major/minor release.

For compounding effect, if you can manage it, stuff the output of every previous call into the context window of the next one to run.

To make sure you are credited with the usage, setup your editor to run an LSP that makes LLM calls whenever possible.

Run some on save, run some as a part of linting and static analysis checks, run some on every keystroke.

Make sure to stuff this crap in your editor’s global config but only scoped to the paths associated with company projects. That way you get the increased token usage explicitly attributed to you without committing it to git and thus “sharing the credit” with all of your teammates. Still runs on the company projects without ruining your ability to quickly open random text files. Also, I would make sure to set a timeout on the LSP to prevent the AI nonsense from blocking real linters and tools, keeping your editor nice and responsive.

MSS wumao reporting for duty o7

“I only work on the infrastructure that facilitates all the murder. I don’t do any murder myself.”

A single cooking show where contestants are confined by the same constraints that the average prole contends with would be very worth watching. Start that shit from the grocery store too. Bonus points for fewest dishes dirtied.

I’m rabidly pro-China and tacitly pro-Russia. I will praise both their people and their governments when I feel they are doing right, and criticize them when they are doing wrong.

Not interested in spreading falsehoods, but if anyone would like to organize efforts to express these opinions and supporting evidence, I would enthusiastically participate.

Westerners are so conditioned to regurgitate hatred against the officially sanctioned state enemies that not blindly parroting their caricatures is seen as suspicious, let alone have positive things to say.

I have more and stronger critiques of both countries and their governments than their haters do, largely because I have made serious attempts to understand the culture, history, & material conditions of these countries, instead of brushing them off with a thought-terminating cliché.

China making the BBC slightly more inconvenient to access is far worse than exterminating an entire continent of people in a centuries long colonial project.

Nevermind the rate at which that proportion is shrinking.

FD, no items, fox only

GTK themes are themes for apps using the GTK GUI toolkit. They are basically CSS rules that apply to app widgets. You can probably find one by searching “amoled GTK theme” then installing it on your distro and using GNOME Tweaks to select the theme.

I’m sure there are #000000 AMOLED GTK themes.

Get a load of this green bubble loser