<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Thoughts &#8211; Cristian Nebunu</title>
	<atom:link href="https://cristiannebunu.com/category/thoughts/feed/" rel="self" type="application/rss+xml" />
	<link>https://cristiannebunu.com</link>
	<description>Full Stack Developer - Laravel / Vue.js / WordPress</description>
	<lastBuildDate>Sun, 30 Aug 2026 15:30:51 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>
	<item>
		<title>On Privacy, Design &#038; Career: 4 Essays</title>
		<link>https://cristiannebunu.com/online-privacy-web-design-villains-career-reflection-4/</link>
		
		<dc:creator><![CDATA[Cristian N]]></dc:creator>
		<pubDate>Thu, 22 Oct 2026 20:30:00 +0000</pubDate>
				<category><![CDATA[Thoughts]]></category>
		<guid isPermaLink="false">https://cristiannebunu.com/?p=978</guid>

					<description><![CDATA[<p>Should You Leave Red Herrings About Yourself Online?: For most people, scattering fake biographical details online is a weak way to confuse data brokers. Brokers merge public records that cannot be fictionalized, ten planted lies cannot compete with years of automated collection,…</p>
<p>The post <a rel="nofollow" href="https://cristiannebunu.com/online-privacy-web-design-villains-career-reflection-4/">On Privacy, Design &#038; Career: 4 Essays</a> appeared first on <a rel="nofollow" href="https://cristiannebunu.com">Cristian Nebunu</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<ul class="wp-block-list">
<li>
<p><strong><a href="https://blog.alcazarsec.com/posts/should-you-leave-red-herrings-about-yourself-online" target="_blank" rel="noopener">Should You Leave Red Herrings About Yourself Online?</a>:</strong> For most people, scattering fake biographical details online is a weak way to confuse data brokers. Brokers merge public records that cannot be fictionalized, ten planted lies cannot compete with years of automated collection, and fake facts become liabilities when an account-recovery flow asks for a previous address. Pseudonyms, compartmentalized accounts, and regular opt-outs provide more practical privacy than maintaining an improvised identity under your real name.</p>
</li>
<li>
<p><strong><a href="https://daverupert.com/2026/06/curated-public-domain-images/" target="_blank" rel="noopener">Finding Curated Public Domain Images</a>:</strong> Dave Rupert lists three sources for the woodblock and lithographic illustrations he uses in blog posts: The Public Domain Review, Artvee, and Heritage Type. They fund their curation by selling prints or design assets made from the same public-domain works. I have saved all three for the next time I need a header image that is not a stock photo.</p>
</li>
<li>
<p><strong><a href="https://tylersticka.com/journal/wicked-websites-a-rogues-gallery/" target="_blank" rel="noopener">Wicked Websites: A Rogues&#8217; Gallery</a>:</strong> This illustrated, tongue-in-cheek catalog collects familiar web villains: dialog walls, JS-bloated homepages with autoplay video, &#8220;treasure hunt&#8221; navigation, and pre-checked marketing consent written with confusing double negatives. It is a quick chance to laugh at patterns most web developers have probably shipped at least once.</p>
</li>
<li>
<p><strong><a href="https://kittygiraudel.com/resume/" target="_blank" rel="noopener">Kitty Giraudel&#8217;s Résumé</a>:</strong> This is a useful reference rather than an article. It condenses fifteen years of engineering leadership into a readable résumé, from frontend work at Edenspiekermann to VP of Engineering roles that scaled teams beyond 35 people, alongside long-running open-source projects such as <code>a11y-dialog</code> and Sass Guidelines. Its structure is a good model for presenting a long, varied career to a hiring manager.</p>
</li>
</ul>
<p>The post <a rel="nofollow" href="https://cristiannebunu.com/online-privacy-web-design-villains-career-reflection-4/">On Privacy, Design &#038; Career: 4 Essays</a> appeared first on <a rel="nofollow" href="https://cristiannebunu.com">Cristian Nebunu</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>On Writing, Craft &#038; Thinking Clearly: 5 Essays</title>
		<link>https://cristiannebunu.com/writing-ai-thinking-clearly-2026-5-essays-work-craft/</link>
		
		<dc:creator><![CDATA[Cristian N]]></dc:creator>
		<pubDate>Thu, 15 Oct 2026 20:30:00 +0000</pubDate>
				<category><![CDATA[Thoughts]]></category>
		<guid isPermaLink="false">https://cristiannebunu.com/?p=976</guid>

					<description><![CDATA[<p>Five essays that all circle a similar question from different angles: what happens to your own thinking when you outsource the hard, effortful part of it. Starting in the Analog Domain: Stoyan Stefanov sees the same pattern in music composition and &#8220;vibe…</p>
<p>The post <a rel="nofollow" href="https://cristiannebunu.com/writing-ai-thinking-clearly-2026-5-essays-work-craft/">On Writing, Craft &#038; Thinking Clearly: 5 Essays</a> appeared first on <a rel="nofollow" href="https://cristiannebunu.com">Cristian Nebunu</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">Five essays that all circle a similar question from different angles: what happens to your own thinking when you outsource the hard, effortful part of it.</p>



<ul class="wp-block-list">
<li>
<p><strong><a href="https://www.phpied.com/starting-in-the-analog-domain/" target="_blank" rel="noopener">Starting in the Analog Domain</a>:</strong> Stoyan Stefanov sees the same pattern in music composition and &#8220;vibe coding&#8221;: committing ideas to a computer too early makes the work take longer. He develops music through an idea, an instrument, and paper before opening notation software. A computer&#8217;s precision makes it a poor place for loose experiments and quick failures. His short essay makes a persuasive case for sketching before building.</p>
</li>
<li>
<p><strong><a href="https://www.science.org/content/article/i-hated-writing-until-i-learned-there-s-science-it" target="_blank" rel="noopener">I Hated Writing Until I Learned There&#8217;s a Science to It</a>:</strong> An engineering student who dreaded writing receives a paper covered in red ink from a graduate-student mentor. The marks turn out to be the ordinary shape of revision rather than a verdict on her competence. Treating writing as a skill with techniques, instead of an innate talent you either have or lack, offers a better model for anyone who thinks they are &#8220;just not a writer.&#8221;</p>
</li>
<li>
<p><strong><a href="https://sebastiandedeyne.com/dont-let-ai-write-for-you/" target="_blank" rel="noopener">Don&#8217;t Let AI Write for You</a>:</strong> Sebastian De Deyne shares a short passage from Alex Woods about the purpose of writing. The work increases the writer&#8217;s understanding before it helps the reader. In Woods&#8217;s analogy, letting an LLM do that work resembles paying somebody else to exercise: you receive an output but miss the strength that should come from the effort.</p>
</li>
<li>
<p><strong><a href="https://om.co/2026/04/30/whats-wrong-in-my-thinking-about-errors/" target="_blank" rel="noopener">What&#8217;s Wrong in My Thinking About Errors?</a>:</strong> Om Malik follows up after two resilience-engineering researchers challenged his earlier distinction between forgivable human error and machine error. Their correction is precise: &#8220;human error&#8221; often closes an investigation before it finds the systemic cause. Anyone who has filed an incident under &#8220;operator error&#8221; and moved on will recognize the problem.</p>
</li>
<li>
<p><strong><a href="https://nonogra.ph/write-some-software-give-it-away-for-free-05-05-2026" target="_blank" rel="noopener">Write Some Software, Give It Away for Free</a>:</strong> This essay makes a quiet case for building software as self-exploration rather than as a route to a paycheck. Work made that way may avoid the user-hostile, value-extracting patterns that appear when every decision serves a financial result. The Hacker News discussion is divided between maintainers whose generosity attracted entitlement and those who experienced the opposite.</p>
</li>
</ul>
<p>The post <a rel="nofollow" href="https://cristiannebunu.com/writing-ai-thinking-clearly-2026-5-essays-work-craft/">On Writing, Craft &#038; Thinking Clearly: 5 Essays</a> appeared first on <a rel="nofollow" href="https://cristiannebunu.com">Cristian Nebunu</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>On Power, Attention &#038; Building What&#8217;s Actually Yours</title>
		<link>https://cristiannebunu.com/bootstrapping-redesigning-reclaiming-technical-skill-3/</link>
		
		<dc:creator><![CDATA[Cristian N]]></dc:creator>
		<pubDate>Thu, 08 Oct 2026 20:30:00 +0000</pubDate>
				<category><![CDATA[Thoughts]]></category>
		<guid isPermaLink="false">https://cristiannebunu.com/?p=959</guid>

					<description><![CDATA[<p>The essays in this pair are smaller in scope than the last group, but they hit close to home if you build things for a living. The Slow Death of the Power User: This essay argues that two decades of platform design…</p>
<p>The post <a rel="nofollow" href="https://cristiannebunu.com/bootstrapping-redesigning-reclaiming-technical-skill-3/">On Power, Attention &#038; Building What&#8217;s Actually Yours</a> appeared first on <a rel="nofollow" href="https://cristiannebunu.com">Cristian Nebunu</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">The essays in this pair are smaller in scope than the last group, but they hit close to home if you build things for a living.</p>



<ul class="wp-block-list">
<li>
<p><strong><a href="https://fireborn.mataroa.blog/blog/the-slow-death-of-the-power-user/" target="_blank" rel="noopener">The Slow Death of the Power User</a>:</strong> This essay argues that two decades of platform design choices have taught a generation not to understand its own tools. Its examples include the absence of a user-accessible filesystem on iOS for more than a decade and Android&#8217;s gradual restrictions on sideloading and bootloader access. The author believes the effect has reached developers who rarely leave managed abstractions. The argument connects technical literacy with meaningful consent: a privacy policy is hard to evaluate when the underlying system is inaccessible.</p>
</li>
<li>
<p><strong><a href="https://justinbutlion.substack.com/p/first-10k-month-from-saas-4-areas" target="_blank" rel="noopener">First 10k Month From SaaS, 4 Areas of Focus, and a Mental Model for Growing a New SaaS</a>:</strong> Justin Butlion&#8217;s monthly update covers his bootstrapped SaaS portfolio crossing $10,000 in monthly revenue for the first time, mostly through Monday.com marketplace apps. His &#8220;four areas of focus&#8221; model limits him to four active projects and rejects work outside them. I am going to try the same constraint on my side projects.</p>
</li>
<li>
<p><strong><a href="https://ethanmarcotte.com/wrote/the-house-is-valuable-because-it-is-the-house/" target="_blank" rel="noopener">The House Is Valuable Because It Is the House</a>:</strong> Ethan Marcotte reflects on redesigning his personal site after The New Yorker described the aesthetic sameness of LLM-generated websites, including beige backgrounds and rusty orange accents. He chose texture over forced novelty: hand-picked typefaces that mix old and new, a watercolor motif, and a relief map adapted from a mountain near where he grew up. His redesign asks a practical question that has become more urgent: does this site look distinctly mine?</p>
</li>
</ul>
<p>The post <a rel="nofollow" href="https://cristiannebunu.com/bootstrapping-redesigning-reclaiming-technical-skill-3/">On Power, Attention &#038; Building What&#8217;s Actually Yours</a> appeared first on <a rel="nofollow" href="https://cristiannebunu.com">Cristian Nebunu</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Trust, Ownership &#038; the Open Web: 3 Essays on What We&#8217;re Losing</title>
		<link>https://cristiannebunu.com/ai-fake-news-digital-ownership-resisting-big-tech-3-essays/</link>
		
		<dc:creator><![CDATA[Cristian N]]></dc:creator>
		<pubDate>Thu, 01 Oct 2026 20:30:00 +0000</pubDate>
				<category><![CDATA[Thoughts]]></category>
		<guid isPermaLink="false">https://cristiannebunu.com/?p=957</guid>

					<description><![CDATA[<p>Three essays about the same underlying question, approached from very different angles: who controls the infrastructure we depend on, and what happens when nobody&#8217;s watching closely enough. Now We&#8217;re Getting AI Fake News Complaining About How AI Fake News Is the Death…</p>
<p>The post <a rel="nofollow" href="https://cristiannebunu.com/ai-fake-news-digital-ownership-resisting-big-tech-3-essays/">Trust, Ownership &#038; the Open Web: 3 Essays on What We&#8217;re Losing</a> appeared first on <a rel="nofollow" href="https://cristiannebunu.com">Cristian Nebunu</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">Three essays about the same underlying question, approached from very different angles: who controls the infrastructure we depend on, and what happens when nobody&#8217;s watching closely enough.</p>



<ul class="wp-block-list">
<li>
<p><strong><a href="https://www.niemanlab.org/2026/07/now-were-getting-ai-fake-news-complaining-about-how-ai-fake-news-is-the-death-of-real-news/" target="_blank" rel="noopener">Now We&#8217;re Getting AI Fake News Complaining About How AI Fake News Is the Death of Real News</a>:</strong> Joshua Benton traces a viral story about 47 Alabama weekly newspapers supposedly killed by an AI content mill. Its source was a site with no real staff, invented bylines, and fabricated named sources, all pointing back to a Finnish tech company. He started investigating after noticing that every other &#8220;Politics&#8221; story on the site undermined Taiwan&#8217;s position against China. The result is unsettling: fabricated reporting can target a niche so specific that almost nobody has the local knowledge to catch it.</p>
</li>
<li>
<p><strong><a href="https://zeldman.com/2026/07/02/the-human-story-of-the-open-web/" target="_blank" rel="noopener">The Human Story of the Open Web</a>:</strong> Jeffrey Zeldman writes about a preview screening of &#8220;Code for the People,&#8221; a short documentary on reclaiming the open web from a handful of &#8220;digital landlords.&#8221; His prescription is the same one he has followed since the 1990s: keep your content on a domain you control and prefer open-source tools over proprietary services that can change the rules overnight.</p>
</li>
<li>
<p><strong><a href="https://airesistlist.org/" target="_blank" rel="noopener">The AI Resist List</a>:</strong> Researchers including Karen Hao, author of <em>Empire of AI</em>, built this living global directory of organized opposition to harms from large-scale AI development. Entries are grouped by the part of the industry they target, including funding, data, labor, surveillance, and policy. Examples range from a Japanese union petition about algorithmic wage-setting to a Uruguayan campaign for data-center transparency and an Amazon employee letter about AI and climate goals. The directory shows who is organizing, where, and by which method.</p>
</li>
</ul>
<p>The post <a rel="nofollow" href="https://cristiannebunu.com/ai-fake-news-digital-ownership-resisting-big-tech-3-essays/">Trust, Ownership &#038; the Open Web: 3 Essays on What We&#8217;re Losing</a> appeared first on <a rel="nofollow" href="https://cristiannebunu.com">Cristian Nebunu</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Today&#8217;s recommendations: An agent is a model plus a harness, the coming loop, whether small software businesses survive AI, and why good money still feels like a treadmill</title>
		<link>https://cristiannebunu.com/agent-model-plus-harness-small-software-businesses/</link>
		
		<dc:creator><![CDATA[Cristian N]]></dc:creator>
		<pubDate>Thu, 24 Sep 2026 20:30:00 +0000</pubDate>
				<category><![CDATA[Thoughts]]></category>
		<guid isPermaLink="false">https://cristiannebunu.com/?p=890</guid>

					<description><![CDATA[<p>A closing batch about where the work, and the money, is heading, from the codebase out to the economy, including whether small software businesses survive AI. Addy Osmani&#8217;s The New Software Lifecycle pulls the ideas that matter out of a Google whitepaper…</p>
<p>The post <a rel="nofollow" href="https://cristiannebunu.com/agent-model-plus-harness-small-software-businesses/">Today&#8217;s recommendations: An agent is a model plus a harness, the coming loop, whether small software businesses survive AI, and why good money still feels like a treadmill</a> appeared first on <a rel="nofollow" href="https://cristiannebunu.com">Cristian Nebunu</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>A closing batch about where the work, and the money, is heading, from the codebase out to the economy, including whether small software businesses survive AI.</p>
<p>Addy Osmani&#8217;s <a href="https://addyosmani.com/blog/new-sdlc-vibe-coding/" target="_blank" rel="noopener">The New Software Lifecycle</a> pulls the ideas that matter out of a Google whitepaper he co-wrote. The framing I keep reusing: an agent is a model plus a harness, roughly 10% model and 90% harness (the rules, tools, sandboxes, orchestration, guardrails, observability), so when an agent does something dumb, debug the <em>harness</em> first, because most agent failures are configuration failures you can fix today. Context engineering (static vs dynamic) is a financial lever, not just a technical one; verification (tests plus output <em>and</em> trajectory evals) is the line between vibe coding and engineering; and the lifecycle compresses unevenly: implementation collapses to hours while specification and verification stay slow, so spec quality becomes the bottleneck. &#8220;Set the bar at the eval, not the demo&#8221; is the sentence to hand a skeptical lead.</p>
<p>Armin Ronacher&#8217;s <a href="https://lucumr.pocoo.org/2026/6/23/the-coming-loop/" target="_blank" rel="noopener">The Coming Loop</a> is the uneasy counterweight, and, full disclosure, his <em>third</em> appearance across this series, so I&#8217;m flagging it (more on that in the dedup note; you may want to space him out). He&#8217;s watching harness-level loops (a queue, a machine that attempts work, a harness that decides whether it&#8217;s actually done and keeps it alive past &#8220;I&#8217;m done&#8221;) take over agentic engineering, and he&#8217;s honest that they already work astonishingly well for porting, performance exploration, security scanning, anything that transforms existing code or produces short-shelf-life artifacts. His worry is lasting code you care about: loops amplify the model&#8217;s instinct to add local defenses instead of making bad states impossible, and the deeper fear is dependency: codebases produced, reviewed, and maintained by loops that assume machine participation, that you can no longer understand without the machine. And you can&#8217;t fully opt out, because attackers and competitors will loop against you. It pairs naturally with the Osmani piece: same future, opposite temperament.</p>
<p>Brandur Leach&#8217;s <a href="https://brandur.org/minimum-viable-unit" target="_blank" rel="noopener">The Minimum Viable Unit of Saleable Software</a> is the SaaS-economics read, and a genuinely useful mental model given your own product ambitions. Starting from the viral &#8220;we replaced $400/mo Jira with a Claude-built tracker&#8221; anecdote, he does the actual math: cheap isn&#8217;t zero, LLM-built software still costs feedback loops and maintenance labor, and the Jira clone takes ~37 months to break even while a $25k/mo Salesforce is closer to a real build decision. He proposes a &#8220;zone of viability&#8221; (enough novelty that a rebuild is non-trivial, priced low enough not to provoke one) and the &#8220;minimum viable unit of saleable software&#8221; below which buying beats building. He&#8217;s betting his own job queue business on landing above that line. Required reading before you price anything.</p>
<p>Finally, Hanna Horvath&#8217;s <a href="https://yourbrainonmoney.substack.com/p/i-make-good-money-why-do-i-still" target="_blank" rel="noopener">I Make Good Money. Why Do I Still Feel Like This?</a> zooms all the way out to the economy the rest of us are building software inside. It&#8217;s a sharp essay on the K-shaped economy and the &#8220;missing middle&#8221;: the American middle class as a deliberate postwar policy project that got unbundled and repriced piece by piece, splitting into &#8220;material precarity&#8221; (the basics slipping) and &#8220;positional precarity&#8221; (high earners whose expectations no longer resolve). The real line, she argues, isn&#8217;t income but capital (whether your money generates its own returns), and both groups misdirect their frustration sideways instead of up. US-centric, but the psychology of the treadmill travels. A good, humane palate cleanser after a lot of AI discourse.</p>
<hr />
<p><em>End of batch.</em></p>
<p>The post <a rel="nofollow" href="https://cristiannebunu.com/agent-model-plus-harness-small-software-businesses/">Today&#8217;s recommendations: An agent is a model plus a harness, the coming loop, whether small software businesses survive AI, and why good money still feels like a treadmill</a> appeared first on <a rel="nofollow" href="https://cristiannebunu.com">Cristian Nebunu</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Today&#8217;s recommendations: Engineering for a four-slot mind, why duplication beats the wrong abstraction, and knowing what not to build</title>
		<link>https://cristiannebunu.com/four-slot-mind-wrong-abstraction-what-not-to-build/</link>
		
		<dc:creator><![CDATA[Cristian N]]></dc:creator>
		<pubDate>Thu, 17 Sep 2026 20:30:00 +0000</pubDate>
				<category><![CDATA[Thoughts]]></category>
		<guid isPermaLink="false">https://cristiannebunu.com/?p=889</guid>

					<description><![CDATA[<p>Three essays that circle the same truth from different angles: good engineering is mostly about restraint, about respecting the limits of the person doing it, and about why duplication beats the wrong abstraction. Matt Williams&#8217; Engineering for Bounded Cognition is the piece…</p>
<p>The post <a rel="nofollow" href="https://cristiannebunu.com/four-slot-mind-wrong-abstraction-what-not-to-build/">Today&#8217;s recommendations: Engineering for a four-slot mind, why duplication beats the wrong abstraction, and knowing what not to build</a> appeared first on <a rel="nofollow" href="https://cristiannebunu.com">Cristian Nebunu</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Three essays that circle the same truth from different angles: good engineering is mostly about restraint, about respecting the limits of the person doing it, and about why duplication beats the wrong abstraction.</p>
<p>Matt Williams&#8217; <a href="https://shapeofthesystem.com/posts/2026/02/03/bounded-cognition" target="_blank" rel="noopener">Engineering for Bounded Cognition</a> is the piece I&#8217;ll be quoting for a while. The honest number for how many things a mind can hold at once, with no tricks, is about four, and we build systems of tens of millions of lines with that. The gorilla experiment and the door-swap study drive it home: attention is a narrow torch beam, and &#8220;human error&#8221; is usually a system built for an operator who never gets tired, never looks away, and holds the whole machine in their head: an operator who was never born. Everything we call good engineering (naming, boundaries, tests, anything undoable) is a way to move state out of a fragile four-slot mind and into the structure. And LLMs, with their context windows and &#8220;lost in the middle&#8221; attention, fail the same way. The OXO peeler coda (design for the constrained case and you get a better thing for everyone) is the quiet heart of it.</p>
<p>Sandi Metz&#8217;s <a href="https://sandimetz.com/blog/2016/1/20/the-wrong-abstraction" target="_blank" rel="noopener">The Wrong Abstraction</a> is a 2016 classic that&#8217;s only gotten more relevant. The thesis (&#8220;duplication is far cheaper than the wrong abstraction&#8221;) and the eight-step decay it describes (extract the shared thing, then watch each new requirement bolt on a parameter and a conditional until it&#8217;s incomprehensible) is a pattern you&#8217;ll recognize in your own codebase immediately. The sunk-cost trap is the villain: the more effort the abstraction took, the harder it is to let go. Her advice is counterintuitive and correct: when the abstraction is wrong, the fastest way forward is back: re-inline the duplication, delete what each caller doesn&#8217;t need, and re-extract from what&#8217;s actually there. Read it right after the Expressive piece in the programming list; they&#8217;re arguing for the same instinct about boundaries.</p>
<p>Jakub Krehel&#8217;s <a href="https://jakub.kr/writing/less-is-more" target="_blank" rel="noopener">Less Is More, More or Less</a> brings it into the AI present. When every feature, animation, and idea is a couple of prompts away, the constraint stops being <em>can</em> you build it and becomes <em>should</em> you. His context-menu example is perfect: animating both open and close feels obviously better until you realize the menu opens 200 times a day, and then not-animating becomes the obvious call, a judgment agents can&#8217;t make yet because they execute without understanding how something is used. Removing is harder than adding, because removing requires intention. His conclusion, that in the age of AI knowing what <em>not</em> to build might be the most important skill of all, is the through-line of this whole cluster.</p>
<p>The post <a rel="nofollow" href="https://cristiannebunu.com/four-slot-mind-wrong-abstraction-what-not-to-build/">Today&#8217;s recommendations: Engineering for a four-slot mind, why duplication beats the wrong abstraction, and knowing what not to build</a> appeared first on <a rel="nofollow" href="https://cristiannebunu.com">Cristian Nebunu</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Today&#8217;s recommendations: Writing an effective design doc, winnowing sentences, naming the modal-popup scourge, and why blogging the obvious is worth it</title>
		<link>https://cristiannebunu.com/design-docs-winnowing-sentences-blogging-the-obvious/</link>
		
		<dc:creator><![CDATA[Cristian N]]></dc:creator>
		<pubDate>Thu, 10 Sep 2026 20:30:00 +0000</pubDate>
				<category><![CDATA[Thoughts]]></category>
		<guid isPermaLink="false">https://cristiannebunu.com/?p=888</guid>

					<description><![CDATA[<p>A batch about writing well and about writing at all, plus a righteous rant that connects the two, starting with how to write an effective design doc. Michael Lynch&#8217;s How to Write an Effective Software Design Document is an excerpt from his…</p>
<p>The post <a rel="nofollow" href="https://cristiannebunu.com/design-docs-winnowing-sentences-blogging-the-obvious/">Today&#8217;s recommendations: Writing an effective design doc, winnowing sentences, naming the modal-popup scourge, and why blogging the obvious is worth it</a> appeared first on <a rel="nofollow" href="https://cristiannebunu.com">Cristian Nebunu</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>A batch about writing well and about writing at all, plus a righteous rant that connects the two, starting with how to write an effective design doc.</p>
<p>Michael Lynch&#8217;s <a href="https://refactoringenglish.com/excerpts/write-an-effective-design-doc/" target="_blank" rel="noopener">How to Write an Effective Software Design Document</a> is an excerpt from his <em>Refactoring English</em> book, and it&#8217;s the best structured treatment of design docs I&#8217;ve read. The framing question that organizes everything (&#8220;what&#8217;s the penalty for being wrong?&#8221;) is what tells you which decisions belong in the doc (language and storage choices: yes; a &#8220;load more&#8221; button: no). He walks every section you might include (objective, background, goals/non-goals, scenarios, SLOs, security, open/resolved issues, alternatives considered) with real examples, and ships a full public design doc since he&#8217;d never seen a good one online. Even as a solo dev writing for future-you, the discipline of forcing the hard decisions before you code is the whole payoff.</p>
<p>Robin Rendle&#8217;s <a href="https://robinrendle.com/notes/several-short-sentences-on-writing/" target="_blank" rel="noopener">Several Short Sentences on Writing</a> is the one for the novelist in you. Riffing on Verlyn Klinkenborg&#8217;s book, he lands on the idea that a writer&#8217;s real work is the endless winnowing of sentences, and that cutting long sentences into short ones is usually fear management, the urge to show off that you <em>can</em> write a sentence that never stops. The reframe that helps me: your job is making sentences, one at a time, which dissolves the overwhelm of a big project into something you can actually pick up. He also writes publicly precisely because knowing strangers will read it forces the winnowing. Directly useful for the HARDLOCK line-editing pass on <em>The First Legion</em>.</p>
<p>John Gruber&#8217;s <a href="https://daringfireball.net/2026/05/what_is_a_dickover" target="_blank" rel="noopener">What Is a Dickover?</a> is a rant, and a glorious one. He coins a word for the modal panels, popovers, and full-screen curtains that obscure the content you came to read (cookie banners, newsletter nags, app-install pleads), the ones that &#8220;deliberately obscure their own content.&#8221; The Substack curtain gets a special beating, as do the sites that sucker-punch you <em>after</em> you start scrolling. His principle is one I keep coming back to: a webpage should show the webpage. It&#8217;s crude, funny, and completely correct.</p>
<p>Which leads straight to Jim Nielsen&#8217;s <a href="https://blog.jim-nielsen.com/2026/blogging-stating-the-obvious/" target="_blank" rel="noopener">Blogging Can Just Be Stating the Obvious</a>, a short piece written <em>in response</em> to Gruber. He fixes on Gruber&#8217;s aside (&#8220;I should not have to explain this&#8221;) and turns it into a small thesis about blogging: the best posts are often someone playing the child in <em>The Emperor&#8217;s New Clothes</em>, saying the thing that&#8217;s obvious to them but nobody else is saying. If someone&#8217;s already said it, just link them and shout &#8220;yes, this.&#8221; A permission slip for publishing, and a reminder that &#8220;is this even worth saying?&#8221; is usually the wrong question. (This is Jim&#8217;s second appearance in the series; he wrote the &#8220;pedantry of computing&#8221; piece a couple of batches back.)</p>
<p>The post <a rel="nofollow" href="https://cristiannebunu.com/design-docs-winnowing-sentences-blogging-the-obvious/">Today&#8217;s recommendations: Writing an effective design doc, winnowing sentences, naming the modal-popup scourge, and why blogging the obvious is worth it</a> appeared first on <a rel="nofollow" href="https://cristiannebunu.com">Cristian Nebunu</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Today&#8217;s recommendations: AI, Openness &#038; the Web: Five Essays on Where This Is Going</title>
		<link>https://cristiannebunu.com/ai-open-web-five-essays/</link>
		
		<dc:creator><![CDATA[Cristian N]]></dc:creator>
		<pubDate>Thu, 03 Sep 2026 20:30:00 +0000</pubDate>
				<category><![CDATA[Thoughts]]></category>
		<guid isPermaLink="false">https://cristiannebunu.com/?p=852</guid>

					<description><![CDATA[<p>These are the pieces I keep turning over. Less &#8220;how to&#8221; and more &#8220;where is this all heading&#8221;: the tension between capability and access, and what happens to the open web and the people who make it. Where my head is at…</p>
<p>The post <a rel="nofollow" href="https://cristiannebunu.com/ai-open-web-five-essays/">Today&#8217;s recommendations: AI, Openness &#038; the Web: Five Essays on Where This Is Going</a> appeared first on <a rel="nofollow" href="https://cristiannebunu.com">Cristian Nebunu</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>These are the pieces I keep turning over. Less &#8220;how to&#8221; and more &#8220;where is this all heading&#8221;: the tension between capability and access, and what happens to the open web and the people who make it.</p>
<p><strong><a href="https://paul.kinlan.me/where-my-head-is-at-with-llms-and-the-web/" target="_blank" rel="noopener">Where my head is at with LLMs and the web</a></strong><br />
Paul Kinlan (Chrome DevRel) pulls together a year of his AI writing into one thesis. The idea that grabbed me: the models we now code with learned from a web that&#8217;s already a year-plus stale, so &#8220;the web inside the model is the web developers actually inherit,&#8221; and frameworks that stop appearing in training data quietly die. From there he&#8217;s optimistic: WebMCP as a revival of &#8220;web intents,&#8221; the browser as the safest sandbox for prompt-shaped programs, content negotiation reborn as on-demand generation. A dense, generative read on where the platform could go.</p>
<p><strong><a href="https://pawelgrzybek.com/fuck-thank-you/" target="_blank" rel="noopener">Fuck | Thank you</a></strong><br />
Paweł Grzybek&#8217;s two-part cri de coeur: a blast at the companies obfuscating links and hollowing out the web (AI answers with no attribution, search that stops sending you anywhere), followed by a long, sincere thank-you to the creators who made the web interesting for him. It captures a mood a lot of us share right now: half anger at what&#8217;s being taken, half determination that the answer is to keep making and to tell people you appreciate them. The gratitude half is the part I want to steal the energy of.</p>
<p><strong><a href="https://chrislema.com/encoded-judgment-cheap-model-performs-like-expensive" target="_blank" rel="noopener">Encoded Judgment: How a Cheap Model Performs Like an Expensive One</a></strong><br />
Chris Lema maps an old product-team discipline (onboard three customers, write down every question, hand off the playbook) onto AI cost. The frame: every decision lives in one of three tiers (frontier model, cheap model with a checklist, or plain code), and the win is capturing judgment <em>once</em> into a reference doc so a cheap model can do work you&#8217;d have sworn needed the expensive one. &#8220;Judgment you capture once is an asset; judgment you pay for on every request is rent.&#8221; A clean way to think about token spend.</p>
<p><strong><a href="https://steve-yegge.medium.com/the-flat-curve-society-36c8b01eb33b" target="_blank" rel="noopener">The Flat Curve Society</a></strong><br />
Steve Yegge&#8217;s long, characteristically confident essay arguing that frontier models will keep improving exponentially, but behind lock and key, so <em>for most of us</em> the curve will appear to flatten. He layers on the &#8220;discernment horizon&#8221; (you can&#8217;t tell two models apart once the problem, or the answer, exceeds you), a surprisingly concrete AI-literacy framework from a Netflix training study (token-spend cohorts, ~5 hours to jump a level), and a bullish take that SaaS is back because rebuilding everything with AI is too expensive and unsupervisable. Whether or not he&#8217;s right, it&#8217;s the most stimulating AI-industry piece I&#8217;ve read this month.</p>
<p><strong><a href="https://lucumr.pocoo.org/2026/6/10/gaslighting/" target="_blank" rel="noopener">Gaslighting Openness</a></strong><br />
Armin Ronacher&#8217;s short, sharp argument that a lot of today&#8217;s fight over open source and AI is narrative manipulation: framing <em>access</em> as irresponsibility and wrapping restriction in the language of safety and security. His examples (Apple vs. the DMA, model vendors training on public works then blocking distillation) may divide readers, but the core worry lands for me as a European: democratized access to technology is in all our interest, and we shouldn&#8217;t let companies convince us that closing the gates is for our own good.</p>
<p>The post <a rel="nofollow" href="https://cristiannebunu.com/ai-open-web-five-essays/">Today&#8217;s recommendations: AI, Openness &#038; the Web: Five Essays on Where This Is Going</a> appeared first on <a rel="nofollow" href="https://cristiannebunu.com">Cristian Nebunu</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Today&#8217;s recommendations: Rediscovering the Indie Web: Directories, Blogs &#038; Launch Spots</title>
		<link>https://cristiannebunu.com/indie-web-directories-blogs-launch-spots/</link>
		
		<dc:creator><![CDATA[Cristian N]]></dc:creator>
		<pubDate>Thu, 27 Aug 2026 20:30:00 +0000</pubDate>
				<category><![CDATA[Thoughts]]></category>
		<guid isPermaLink="false">https://cristiannebunu.com/?p=851</guid>

					<description><![CDATA[<p>Half the reason I keep a bookmarks series at all is a stubborn belief in the small, human, link-driven web. This set is about finding it again: where to read good independent writing, and where to put your own work so people…</p>
<p>The post <a rel="nofollow" href="https://cristiannebunu.com/indie-web-directories-blogs-launch-spots/">Today&#8217;s recommendations: Rediscovering the Indie Web: Directories, Blogs &#038; Launch Spots</a> appeared first on <a rel="nofollow" href="https://cristiannebunu.com">Cristian Nebunu</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">Half the reason I keep a bookmarks series at all is a stubborn belief in the small, human, link-driven web. This set is about finding it again: where to read good independent writing, and where to put your own work so people (and crawlers) actually find it.</p>



<p class="wp-block-paragraph"><strong><a href="https://www.submission.directory/" target="_blank" rel="noopener">Submission.Directory: websites to submit your website to</a></strong>
A hand-picked directory of places to submit a site, startup, or product, including launch platforms, SaaS directories, AI-tool catalogs, maker communities, design galleries, and indie-web listings. Each entry shows domain rating, link type, and cost. It answers the recurring question of where to list a newly shipped project. Appropriately, the directory launched through Show HN.</p>



<p class="wp-block-paragraph"><strong><a href="https://bubbles.town/" target="_blank" rel="noopener">Bubbles.town: Hacker News, but for independent blogs</a></strong>
A community-ranked feed of independent blog posts, filterable by topic and vote count: &#8220;good stuff bubbles up, the rest pops.&#8221; It surfaces personal-site writing that is otherwise hard to find, with recent topics including color perception, indie-web ladders, and &#8220;your app could&#8217;ve been a webpage.&#8221; A daily or weekly Briefing collects the most-voted posts. It has quickly become one of my regular reading sources.</p>



<p class="wp-block-paragraph"><strong><a href="https://news.ycombinator.com/item?id=48528779" target="_blank" rel="noopener">Ask HN: What are you working on? (June 2026)</a></strong>
The recurring &#8220;what are you building&#8221; thread, which is basically a live cross-section of what indie makers are shipping right now: search engines, k8s clients, optics simulators, SQL-canvas agents, tiny health-tracking apps. I skim these both for ideas and for a gut-check on where builder energy is going.</p>



<p class="wp-block-paragraph"><strong><a href="https://news.ycombinator.com/item?id=48466488" target="_blank" rel="noopener">Ask HN: Favorite text-heavy blogs that are a joy to read</a></strong>
A thread born from someone redesigning their own blog and wanting examples where the <em>reading experience</em> is great: good fonts, sane line length, well-formatted code, thoughtful navigation. The replies are a mini-syllabus of beautifully typeset sites (gwern, matklad, Julia Evans, Maxime Heckel, and more). I&#8217;m mining this for my own site.</p>



<p class="wp-block-paragraph"><strong><a href="https://buttondown.com/hacker-newsletter/archive/798/" target="_blank" rel="noopener">Hacker Newsletter #798</a></strong>
This weekly Hacker News recap surfaced several links in these recommendation posts. It is a low-effort alternative to following HN directly, and the June 19 issue provides a representative sample of the format.</p>
<p>The post <a rel="nofollow" href="https://cristiannebunu.com/indie-web-directories-blogs-launch-spots/">Today&#8217;s recommendations: Rediscovering the Indie Web: Directories, Blogs &#038; Launch Spots</a> appeared first on <a rel="nofollow" href="https://cristiannebunu.com">Cristian Nebunu</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Today&#8217;s recommendations: On Writing &#038; Reading: Craft, Memory, and Where Stories Go</title>
		<link>https://cristiannebunu.com/writing-craft-memory-stories/</link>
		
		<dc:creator><![CDATA[Cristian N]]></dc:creator>
		<pubDate>Thu, 20 Aug 2026 20:30:00 +0000</pubDate>
				<category><![CDATA[Thoughts]]></category>
		<guid isPermaLink="false">https://cristiannebunu.com/?p=850</guid>

					<description><![CDATA[<p>Most of my non-technical reading orbits the same question: how do stories work, and how do you get better at making and remembering them. This set is squarely that: craft, memory, and the practical business of putting fiction in front of people.…</p>
<p>The post <a rel="nofollow" href="https://cristiannebunu.com/writing-craft-memory-stories/">Today&#8217;s recommendations: On Writing &#038; Reading: Craft, Memory, and Where Stories Go</a> appeared first on <a rel="nofollow" href="https://cristiannebunu.com">Cristian Nebunu</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">Most of my non-technical reading orbits the same question: how do stories work, and how do you get better at making and remembering them. This set is squarely that: craft, memory, and the practical business of putting fiction in front of people.</p>



<p class="wp-block-paragraph"><strong><a href="https://sive.rs/book/WritEmotionImpact" target="_blank" rel="noopener">Writing for Emotional Impact: Derek Sivers&#8217; book notes</a></strong>
Sivers distills Karl Iglesias&#8217;s screenplay-craft book into notes dense with usable ideas. Several map directly onto my novella work: the reader&#8217;s emotion matters more than the character&#8217;s, plot is &#8220;the ordering of emotions,&#8221; scenes should advance the story and deepen character while landing a visceral response, and writers should enter late and leave early. Sivers rates the repetitive book only 6/10, but its craft lessons apply beyond film.</p>



<p class="wp-block-paragraph"><strong><a href="https://herman.bearblog.dev/active-recall/" target="_blank" rel="noopener">Active recall</a></strong>
Herman argues that he remembers things because he writes about them, not because he has an unusual gift. He cites the Karpicke and Blunt (2011) retrieval-practice study, where free recall beat rereading and concept mapping on a delayed test, even when the test itself used concept mapping. His decade of journaling and a <code>notes.txt</code> full of scribbles amount to free-recall practice. He rarely rereads them; the act of writing does the work.</p>



<p class="wp-block-paragraph"><strong><a href="https://lithub.com/the-man-who-reads-books-for-a-living-one-every-two-days/" target="_blank" rel="noopener">The Man Who Reads Books for a Living (One Every Two Days)</a></strong>
A profile of Clarke Speicher, a freelance &#8220;reader&#8221; who evaluates roughly one book every two days for screen-adaptation potential and writes coverage that influences Hollywood options. The invisible craft job has no salary or security, now happens entirely by email, and carries the uncomfortable possibility that an author may learn their book was reduced to a report in three hours. It is an unusual view from the other side of a writer&#8217;s submission.</p>



<p class="wp-block-paragraph"><strong><a href="https://www.reddit.com/r/WritingWithAI/comments/1uawxh1/where_do_you_publish_or_share_your_novel_stories/" target="_blank" rel="noopener">Where do you publish or share your novel stories? (r/WritingWithAI)</a></strong>
A community thread of writers comparing where they actually put longer fiction (personal sites, Wattpad, Royal Road, newsletters, and so on) and what each venue is good and bad for. Practical if you&#8217;re weighing how to share a novella beyond your own blog.</p>



<p class="wp-block-paragraph"><strong><a href="https://wizardzines.com/comics/write-for-one-person/" target="_blank" rel="noopener">Write for one person</a></strong>
Julia Evans&#8217;s comic argues for writing to one specific person. The result becomes sharper, warmer, and easier to produce than a piece aimed at &#8220;everyone.&#8221; It is short enough to remember.</p>



<p class="wp-block-paragraph"><strong><a href="https://sffawards.com/?g=science-fiction&amp;sort=latest-award" target="_blank" rel="noopener">Science Fiction and Fantasy Book Awards</a></strong>
A browsable database of award-winning and finalist SFF novels from the Hugo, Nebula, Locus, World Fantasy, Arthur C. Clarke, and other awards. Filters include award, year, subgenre, winner status, and Goodreads rating. I can use it to build a reading list and see what the field currently rewards while writing in the genre myself.</p>
<p>The post <a rel="nofollow" href="https://cristiannebunu.com/writing-craft-memory-stories/">Today&#8217;s recommendations: On Writing &#038; Reading: Craft, Memory, and Where Stories Go</a> appeared first on <a rel="nofollow" href="https://cristiannebunu.com">Cristian Nebunu</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
