On building software in the open
There's a particular kind of patience you only develop when you ship software to people who can read the source. You stop writing for the demo. You start writing for the person scrolling through your repo at 11pm wondering if your project is the right thing to depend on.
The shape of the work changes. Naming becomes a public act. The "good enough for now" comment in a private codebase becomes a quiet embarrassment in a public one. You make different tradeoffs, and usually, better ones.
What changes
Most of the difference isn't in the code itself. It's in the small decisions around it: which examples to put in the README, whether to ship the test fixtures, what the changelog actually says.