This idea never left my mind. Shadows that track a single light source. Took it into @figma and made it a system
https://t.co/3a73341xdc
Many thanks @alexwidua π
furthermore, you take the polished, generic-but-well-dressed version and echo it into the web. you just created more training data that reinforces the mean distribution of token vectors into the next generation of models. dead internet becomes dead models
you feel something. you go to your favorite model. it does what models do best, abstracts, names the pattern, references related concepts. you feel you're onto something, but now your direct experience got laundered by the latent space
i built a heatmap of where ai is broken this week
scraped complaints from @Reddit and @hackernews, classified them, rendered a heatmap. this week's hottest pain points:
api pricing/limits (heat: 100)
ai security & prompt injection (95)
coding tool DX (93)
https://t.co/ebtoi46l8n
@GeoffreyHuntley what if you used the Ralph Wiggum loop not just to build software, but to train the models? The number of iterations to complete a working system seems like a pretty good reward signal. Fewer loops = better
@Absolcasso a malicious server is a problem regardless of protocol. CLI output that reaches the agent's context can carry injection too. With MCP it's by design
"MCP is more secure than CLI"
The security lives in the OAuth token scope, not the protocol. A CLI with a narrow token is more secure than an MCP server with a broad one
HATEOAS, The idea that clients should dynamically discover and navigate interfaces at runtime, failed because no client could actually do it. LLMs are the first clients that can.
An agent exploring a CLI with --help is doing what @fielding envisioned 20 years ago