[{"data":1,"prerenderedAt":101},["ShallowReactive",2],{"blog-return-value":3},{"id":4,"title":5,"article":6,"body":7,"date":88,"description":89,"extension":90,"meta":91,"navigation":92,"path":93,"promptVersion":94,"readingTime":95,"seo":96,"stem":97,"tags":98,"__hash__":100},"content\u002Fblog\u002Freturn-value.md","Return value",0,{"type":8,"value":9,"toc":80},"minimark",[10,14,19,33,36,40,43,46,49,53,56,59,62,66,74,77],[11,12,13],"p",{},"Most blog posts get published because someone wrote them. That is not the same as earning a place in someone's attention, and most never do — they are read once, if that, and forgotten. Every post on this blog is held to the second standard, not the first: would the reader keep it?",[15,16,18],"h2",{"id":17},"a-short-bio","A short bio",[11,20,21,22,27,28,32],{},"Seventeen years of building software, currently full-stack and AI-powered tools at ",[23,24,26],"a",{"href":25},"\u002Fcv#progmbh","PROGMBH d.o.o."," — the rest of the bio is on ",[23,29,31],{"href":30},"\u002Fcv","my CV"," for anyone who needs it.",[11,34,35],{},"I bring it up only to flag a parallel. Most software ships because the work happened, not because the result earned its place in the system it joins. Most blog posts ship for the same reason. The standard worth keeping is the same in both domains: a thing that exists is not the same as a thing worth keeping. This blog applies the second test to writing.",[15,37,39],{"id":38},"what-most-posts-miss","What most posts miss",[11,41,42],{},"Most blog posts fail return-value because the test that gates their publication is writer-side, not reader-side. Did I write something today? Did I hit the cadence? Did I cover the keyword? Each of those is a question only the author can answer, and a yes from the author lets the post ship. None of them ask anything of the reader.",[11,44,45],{},"The genres prove it. SEO listicles exist to rank, not to inform — the reader is incidental, a vehicle for impressions. Weekly-cadence posts get written to the calendar; the topic is whatever was due. Consensus restatements take an idea everyone already nodded at and put cleaner sentences around it. The reader closes the tab, learns nothing, and the blog still counts the page view.",[11,47,48],{},"The default state of a published post is that no one needed it. That is the bar most posts clear, because most posts only have to clear the bar the writer set.",[15,50,52],{"id":51},"the-return-value-test","The return-value test",[11,54,55],{},"A post passes the return-value test because the reader takes away more than they spent. The currency on the reader's side is attention; the currency on the writer's side is words. The trade is asymmetric — the writer pays once, the reader pays each time — so the burden of proof sits on the post, not on the reader's patience.",[11,57,58],{},"What does return value look like, concretely? A reframe instead of an exhortation. A named pattern the reader can carry into a meeting next week. A mechanism that explains something the reader had felt but not articulated. One applicable claim per post, promoted to its sharpest sentence and given a handle. Bookmarks, returns, and shares are evidence that the trade landed — they are not the goal of writing, they are the receipt.",[11,60,61],{},"If a post does not name something the reader did not already have words for, it did not pay back. That is the bar the rest of this blog wants to be measured against.",[15,63,65],{"id":64},"the-experiment","The experiment",[11,67,68,69,73],{},"I can publish LLM-assisted writing under this bar because the unit of work is not the prompt. It is the pipeline. Constraints survive across phases — grounding, plan, draft, audit — that a single mega-prompt would dilute long before the closing paragraph. The fuller argument is at ",[23,70,72],{"href":71},"\u002Fblog\u002Fprompts-as-pipelines","Prompts as pipelines","; this section only names the pipeline as the reason the return-value bar is enforceable rather than aspirational.",[11,75,76],{},"Right now, every post on this blog is manually checked and corrected before it ships. The pipeline does most of the work; my hand is on the brakes for the rest. That is the honest state of the experiment as I write this. The day a post clears the bar without my correction is the day the experiment worked.",[11,78,79],{},"Until then, every post here is held to the same question, by hand if it has to be: would you keep this? If the answer is no, the post does not ship. That is the only test I want this blog to be measured by.",{"title":81,"searchDepth":82,"depth":82,"links":83},"",2,[84,85,86,87],{"id":17,"depth":82,"text":18},{"id":38,"depth":82,"text":39},{"id":51,"depth":82,"text":52},{"id":64,"depth":82,"text":65},"2026-01-05","Most blog posts get published because the writer wrote them. This blog is built around a different test — would the reader keep it?","md",{},true,"\u002Fblog\u002Freturn-value",6,"4 min read",{"title":5,"description":89},"blog\u002Freturn-value",[99],"philosophy","dUxIEAULucAm7E8qBH3vZa1GSZcZ0N9MQUkLxnPIlbM",1777707609887]