When I want to look at my own data while I’m out, the quickest option is usually to check the cloud. But logging in can be a hassle, and I also have to remember which service I saved it on, which feels a bit tedious. Even if I know the right service, if I’m logged out and can’t check my password at that moment, I’m locked out.

And if the data isn’t on the cloud at all, then I’m out of options. If what I need is simply quick and easy access, the most straightforward solution is to make it public.

The same is true for my writing: it’s much easier to find the pieces I’ve published. I post my technical articles on platforms like Hatena Blog and Zenn, and when I want to revisit them later, they’re easy to track down. By contrast, when I keep something private—visible only to myself—I often forget where I stored it. Publishing has the side effect of organizing things, making them more accessible. And while the odds are slim, the possibility that someone else might read my work adds just enough pressure to help me improve the quality of my writing.

Recently, Yoichi Ochiai mentioned in an interview that he uses SoundCloud to listen back to his own compositions. He pointed out that making them public ensures compatibility across devices and gives them greater longevity. Exactly so—even if you’re sharing only for your own enjoyment, putting something out in public helps it last.

Publishing doesn’t have to be about showing your work to others. It can simply be for your future self: to make access easier and to reduce the risk of losing data. That’s why it makes sense to treat the public sphere as a kind of storage vault.