My wife takes a photo of our daughter at lunch. That evening, my eighty-seven-year-old mother taps 2026 → July on her tablet, and there it is. No one uploaded anything. No one shared a link. The photo just traveled, on its own, from a phone to a grandmother’s screen. This post walks the whole path and tells you honestly how long each step takes. The Path, Stage by Stage Here’s the trip a single photo makes: ...
This is the post the whole series turns on. Everything before it is the problem; everything after it is possible because of the idea here. For two years I couldn’t sort my daughter’s photos. Not because there were too many — because I was trying to do it in the wrong place: inside the backup folder itself. Why Sorting Inside a Backup Is a Trap My phone auto-backs up to a folder on my NAS. My wife’s phone backs up to another. Those folders are my only copies of my daughter’s baby years. Naturally, I wanted to open them and pick out her best moments. ...
My daughter was born in 2024. By the time she turned two, my wife and I had taken about 10,000 photos and videos of her. Every one of them was safely backed up to my home NAS. And every one of them was, in practice, lost. Not lost like deleted. Lost like a box in the attic you keep meaning to open. The files were there — I just could never find the ones I wanted, because they were mixed in with screenshots, receipts, memes, and every other photo two adults take in two years. “Backed up” had quietly become “buried.” ...
Give a two-year-old a tablet and you know what usually happens. A cartoon starts, then autoplay picks the next one, louder and faster, and twenty minutes later she’s somewhere you never chose. My daughter has a different first choice now. She opens her own player, taps My Records, and watches herself — as a baby, at her first birthday, on an ordinary Tuesday last month. She’ll do this for an hour. She skips the cartoons to get to it. ...
I use Claude Code every day on my main PC. It’s the tool I talk to when making apps for my family. It worked well without problems for several weeks. Then I wanted to use it on a second device. This is my daughter’s PC. Sometimes I work on her apps there. Same subscription, same account, everything was the same. I installed the VS Code extension and opened it. Then I saw this error: ...
My mother is eighty-seven. She lives in the countryside, by the Boseong River. She has never made an account for anything, never typed a password she chose herself, and she would not know what “the cloud” means. But tonight she is holding a Galaxy tablet, and on it she is watching her granddaughter — my daughter — as a newborn. Then at six months. Then last week. She taps a folder marked 2026, then July, and there is a video my wife shot this afternoon. ...
When you make software for yourself, ‘reliable’ is usually good enough. If it breaks, you can fix it yourself. You can log in with SSH, read the logs, and restart it. You are your own support team. But this server was not for me. I made it as a gift for an 80-year-old man. It holds his life lessons on a tablet in his living room. And one fact changes things: he cannot fix problems. Not because he isn’t smart. He is smart. But the moment a server in someone else’s home needs any technical help to keep running, it has already failed for a non-technical owner. ...
Let me tell you about the bug that made me doubt myself more than any other in this series. I’d fix something — say, a misheard word in a transcript. I’d save the corrected file to the server. I’d open the app on my phone to admire the fix. And the old, wrong word would still be sitting there. So I’d fix it again. Save again. Still wrong. I started to wonder if I’d forgotten how to edit a text file. ...
While working on this project, I had to transcribe and edit hundreds of audio files — 145 at first, later almost 400 — using a paid AI service. Each file cost real money. The whole job took hours, sometimes even overnight. If you’ve ever started a long task where each step costs money, you know the worry. Three problems can happen, and I ran into all three before I learned how to prepare for them. ...
In an earlier post I described cloning an app — copying the audio player I’d built onto a tablet to give away. That was a copy: same content, same speaker, a second home. This post is about a step further. I took that same engine and pointed it at a different speaker, and then at a different kind of media — and it just worked. Each time, what should have been “build a whole new app” turned out to be “feed the engine something new.” ...