惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

U
Unit 42
The Cloudflare Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Y
Y Combinator Blog
G
Google Developers Blog
Vercel News
Vercel News
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
Jina AI
Jina AI
Blog — PlanetScale
Blog — PlanetScale
H
Help Net Security
博客园 - 三生石上(FineUI控件)
MongoDB | Blog
MongoDB | Blog
S
SegmentFault 最新的问题
阮一峰的网络日志
阮一峰的网络日志
H
Hackread – Cybersecurity News, Data Breaches, AI and More
aimingoo的专栏
aimingoo的专栏
T
Tailwind CSS Blog
博客园 - 叶小钗
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
月光博客
月光博客
Microsoft Security Blog
Microsoft Security Blog
P
Proofpoint News Feed
The GitHub Blog
The GitHub Blog
云风的 BLOG
云风的 BLOG

Pierce Freeman

A browser for agents | Pierce Freeman The grey market of podcast appearances The way I travel | Pierce Freeman Fixing slow AWS uploads | Pierce Freeman Local tools should still use vaults Starting a podcast in 2025 Being late but still being early Automating our home video imports Adding my parents to tailscale A deep dive on agent sandboxes Language servers for AI | Pierce Freeman My simple home podcast studio We need centralized infrastructure | Pierce Freeman Coercing agents to follow conventions using AST validation My unified theory of social selling My personal backup strategy | Pierce Freeman July updates to the homelab How the KV Cache works httpx is the right way to do web requests in Python Reputation is becoming everything | Pierce Freeman Building a (kind of) invisible mac app Updated knowledge in language models Making an ascii animation | Pierce Freeman How speculative decoding works | Pierce Freeman Under the hood of Claude Code Doing things because they're easy, not hard Speeding up sideeffects with JIT in mountaineer Firehot for hot reloading in Python Misadventures in Python hot reloading How text diffusion works | Pierce Freeman
We solved scratch content first
2026-02-02 · via Pierce Freeman

One of my greatest surprises with scaling laws is we solved from-scratch image generation sooner than we solved editing.

We could have started with trying to encourage models to learn Photoshop; perhaps not by UI interaction but certainly by programmatic manipulation. Take a base layer, stack on transformations that are modeled as tool calls, and measure the output against the results that we want. In some ways this feels easier than pixel based generation. You're guaranteed that shapes are logically coherent if they were created with object primitives that themselves are logical (square, circle, etc).

Instead we decided to solve the whole enchilada.

Models still aren't particularly good at interacting with editing tools; I've tried to build systems that will iteratively modify images with tools.1 At best it ends up with a few simple svg shapes but no sophistication. The results are so painfully worse - longer and worse quality - than just using Nano Banana Pro to generate the whole thing.

It ended up being way easier to treat the problem as truly end to end. But fully generating pixels comes at the expense of being able to tweak the end product manually. I suspect that's part of why we see such a flood of corporate slop2. Their creators might see the flaws - might even not be happy with them - but they've satisfied the bar of good enough. After all if you really want to get 100% good you're going to have to restart from scratch and build it yourself. It's much easier to accept the 95% quality that's one shotted.

At the moment we're left with a strange inversion: infinite creative power, zero creative control. You can make anything, as long as you're willing to accept whatever comes out. I imagine eventually the tooling will catch up: but I think it's distinctly possible we end up with better pixel-editing tools (ie. infinite guideable revisions) before we end up with tool use control.

  1. Simon Willison is well known for his pelican test of each LLM, where he tries to get the LLM to generate him a pelican from scratch via svg code. They're pretty bad at doing this; but a 7B image model can easily generate something photorealistic. ↩

  2. There's always the concern that we only can identify poor AI, not good examples. There might very well be a ton more AI generated content online than we recognize because it's good enough to pass unnoticed. ↩