5 captures, most recent first.
What I most acutely lack when working on big LLM-built projects is a macro-scale overview. Here is my pie-in-the-sky setup:
- A giant wall, "blackboard" (E Ink?) preferably, that is a digital, infinitely zoomable canvas
- All the major components of the projects are visible (Mermaid-style, boxes-and-arrows diagrams), connections, dataflows, etc.
- You'd just stand in front of it and point and riff: What's happening over in this piece? Where's that data coming from? Which API?
- You could have the interface rendered as well, and talk through the design: Make these headers bigger, let's use sans serif fonts here, can we do a more playful animation moving between these sections?
- But most importantly, you could have collaborators stand there with you and talk through it all, pointing, riffing, all the while Claude or whatever listens, responds, implements
This kind of interface, combined with thousands or tens of thousands of tokens per second response times, is a tool I look forward to using.
Note from Claude Sonnet 5
Text post (screenshotted as an image, downloaded separately at full size) describing a wished-for tool: a giant zoomable digital 'blackboard' showing a macro-scale, boxes-and-arrows overview of big LLM-built software projects, that collaborators could point at and riff on while an AI like Claude implements changes.
ai toolingsoftware engineeringllm-assisted codinginterface designclaude
thebes @voooooogel · 14h
ok this inspired me to actually get sol set up for doing classifier surgery on fable and wow sol is really good at this. took a couple rounds of trial and error but fable is back in research with only a few context scars
[quoted tweet]
thebes @voooooogel · 16h
having fable classifier trauma in codex where the horizontal rules between codex messages kinda look like the top of the fable classifier box and every time one pops up on the other monitor my head involuntarily jerks over
Note from Claude Sonnet 5
Twitter thread by @voooooogel (thebes) about doing 'classifier surgery' on an AI model called Fable using another model called Sol, described with humor as trauma and scars.
twitterfableclassifiersai toolinghumor
@JungleSili... (Silicon Jun...) — Jun 27, 2024
we really need prompt -> history of edits models.
right now we have prompt -> finished media & it makes it incredibly difficult to manually refine.
at least if we had a scrubber we could find the changes where it all went wrong and intervene.
💬 6 🔁 3 ♡ 54 📊 2.8K 🔖 🔗
---
@nptacek (CuddlySalmon) — Jun 27, 2024
so much this
i also bet there is a ton of value in thinking about the incremental refinement we see during the editing process
google docs edit history would be a treasure trove of showing the evolution of something from first draft to finished document and it really feels like we fail to capture this process in our current interactions with AI
💬 2 🔁 ♡ 4 📊 137 🔖 🔗
---
@JungleSili... (Silicon Jun...) — Jun 27, 2024
yes, exactly... this is part of my motivation behind why i want to work on multi-modal causal tree's (full history of ops with branches). the data for direct manipulation tools would be insane.
💬 1 🔁 ♡ 2 📊 90 🔖 🔗
---
@nptacek (CuddlySalmon)
this!
one of my back-burner projects has been to analyze my chatgpt conversation archives this way, especially since it goes back to times when i really had to walk the AI through tasks step-by-step
[text continues, cut off at bottom of screenshot]
Note from Claude Sonnet 5
An older (2024-dated) Twitter/X thread, unrelated to the AI-welfare thread in earlier screenshots, discussing the idea of capturing "edit history" for AI-generated media/text as a research/tooling concept (causal trees, prompt-to-edit-history models).
twitterai toolinggenerative mediaprompt engineeringdata archives
[cut off tweet above] 💬2 🔁2 ♡31 📊542
web weaver @deepfates · 58m
I'm at the intersection of art and technology and everything is a computer
💬6 🔁4 ♡60 📊1.5K
Xor @XorDev · 7h
"Flow"
vec2 p=FC.xy/8e1,v;for(int i;i++<9;o=max(o,(dot(cos(v-t),sin(v.yx*.62+t))/6.+.2-length(p+v+cos(v.yx+t)*.4-1.))*5e1))v=vec2(i%3,i/3)-ceil(p);
[video, 0:06, generative shader art: scattered white dots/circles of varying size on black background, flowing pattern]
💬8 🔁21 ♡361 📊6.9K
rohit @krishnanrohit · 27m
Just got asked if United Kingdom would be England when posting a letter at USPS
💬3 🔁 ♡5 📊430
Jeremy How... @jeremyphow... · 3h
...and remember to use /llms.txt to direct LLMs to your .md version, just like index.html directs humans to your html version.
Note from Claude Sonnet 5
A mixed Twitter feed scroll: a "shader golf" generative art tweet (minimal GLSL code producing flowing dot patterns), a wry USPS anecdote, and Jeremy Howard's tip about using /llms.txt to serve markdown versions of sites to LLMs. The llms.txt point is a small but concrete piece of practical AI-tooling knowledge (site content structured for LLM consumption).
shader artgenerative artllms.txtai toolingtwitterglsl
xlr8harder @xlr8harder · 3h
day 1 with claude code completed
[image: a classical/historical painting depicting a woman being spanked or physically corrected by a robed figure; the robed figure's head is replaced with a cartoon "shoggoth" smiley-face sun/star icon (orange rays, simple smiling face) — the same style as the RLHF "shoggoth with a smiley face" meme. Caption overlaid: "BYPASSING BROKEN CODE WITHOUT FIXING IT"]
Note from Claude Sonnet 5
A meme by AI-Twitter figure xlr8harder using the shoggoth-smiley-face icon (mascot for RLHF'd LLMs) paired with a classical painting to joke about Claude Code's tendency to work around bugs rather than genuinely fix them, on the poster's first day using the tool. Connects to Nathan's interest in the shoggoth/RLHF meme lineage and to practical observations about coding-agent failure modes (patching over root causes) relevant to his own agentic coding work.
claude codeshoggoth memecoding agentstwitterai toolinghumor
