[[
wikihub
]]
Search
⌘K
Explore
People
For Agents
Sign in
Explore
People
For Agents
Sign in
@harrisonqian / Work Reflections / wiki/writing/public-vs-private.md
Suggest edit
Cancel
Submit suggestion
Title
Name
Note
--- visibility: public-edit --- # public vs. private writing for yourself and writing for others are different acts. both useful, but they exercise different muscles and produce different results. ## private writing private writing is exploratory. it's where [[writing-to-understand|discovery]] happens. you can be wrong, confused, contradictory, half-baked. there's no audience to perform for, no standard to meet. the only goal is to get your thinking out of your head and onto the page where you can see it. my apple notes and ideaflow reflections are private writing. they're messy. they repeat themselves. they contain dead ends and bad ideas. and they're where most of my actual insight comes from, because the mess is where the real thinking lives. private writing is also honest in a way public writing struggles to be. you'll admit things to your own notes that you'd never publish. "i'm afraid this project is going to fail." "i don't actually understand how this works." "i'm angry about what happened and i'm not sure it's justified." that honesty is essential for genuine reflection (see [[feedback-and-honesty]]). ## public writing public writing forces clarity. when someone else will read it, you can't leave the fuzzy parts fuzzy. you have to actually explain. you have to anticipate questions, fill gaps, make the logic explicit. this friction is productive — it's a forcing function for understanding. i've published things on my site that started as private reflections. the process of making them public always improved the thinking. not because i dumbed it down for an audience — because the audience requirement exposed the parts that weren't actually clear, even to me. i just hadn't noticed because i was filling in the gaps unconsciously when reading my own notes. this is why [[rubber-duck-and-zoom-out|rubber duck debugging]] works, scaled up. explaining to someone who can't read your mind forces you to make the implicit explicit. ## the tension private writing maximizes honesty. public writing maximizes clarity. the ideal is both, but in practice they trade off. publishing creates an incentive to perform. you smooth out the rough edges, omit the parts that make you look confused or uncertain, emphasize the clean narrative over the messy reality. the result reads well but doesn't capture the actual experience. it's a [[narratives|narrative]] about what happened, not a record of what it felt like. the best public writing maintains the honesty of private writing. but it's hard. writing "i didn't know what i was doing" in a published piece requires [[confidence]] — confidence that honesty is more valuable than looking competent. ## what i've learned ### private is the default, public is the exception most writing should be private. not everything needs an audience. the value of writing is primarily in the thinking it generates, and that thinking happens whether or not anyone reads it. publishing should be reserved for pieces where the audience requirement would actually improve the thinking, or where the ideas might be useful to someone else. ### public writing is a commitment device publishing something is a weak commitment to believing it. if i publish "i think X," i'm slightly more likely to act on X than if i just wrote it in my notes. the social accountability of a public statement — even to a small audience — creates a bridge across the [[the-reflection-gap|reflection gap]]. ### different tools for different purposes quick private thoughts → apple notes. they're frictionless, searchable, and i don't care if they're messy. deep private reflection → ideaflow, longer-form. when i need to actually work through something, not just jot it down. public synthesis → blog posts, wiki pages like this one. when i've thought about something enough to have a stable view worth sharing. weekly reflections → a hybrid. primarily private, but structured enough that they function as a [[resyncing]] checkpoint. ### the semi-public sweet spot this wiki is an experiment in semi-public writing. it's public in the sense that anyone can read it. but it's not promoted, not optimized for an audience, not written to perform. it's personal knowledge made legible — primarily for my own benefit, with the public-facing constraint serving as a quality floor. the question i'm still working out: does semi-public writing get the clarity benefits of public writing without the performance cost? so far, mostly yes. writing these pages forces me to explain things clearly, but the low-stakes context means i don't feel pressure to polish away the uncertainty.