Automation

This is the map. If you’ve followed the series, this ties the pieces together. If you’re starting here, this is the whole system in one view — how my daughter’s photos and videos get from two phones to my eighty-seven-year-old mother’s tablet, sorted by month, for nothing per month. The Whole Pipeline [Dad's phone] [Mom's phone] | | Synology Drive auto-backup (over the internet) | | v v [ Home NAS: two backup folders ] <- never edited | hourly check copies NEW files (skips anything already handled) v [ Working folder: the "cutting board" ] | I open a browser gallery and pick the keepers v [ One "Import" button ] - convert videos to H.264 720p (ffmpeg) - resize photos - file into Year / Month by the file's date v [ Growth archive on the NAS ] | served over a free Cloudflare tunnel v [ Kids Player app -> "My Records" tab ] - tap a month - videos play continuously - photos drift by, gently zooming v [ Grandmother's tablet. Daughter's tablet. ] Every arrow except one is automatic. The single human step is “pick the keepers,” and it takes about a minute a day. ...

Here’s a problem that sounds harder than it is. New files arrive on the cutting board every hour. I sort them in passes, over several days. The automatic check keeps copying. So how does the same photo never get imported twice? No database. One small ledger, plus a cheap shortcut, do the whole job. The Ledger Does the Real Work When the hourly check copies a file onto the cutting board, it writes one line in a small record — a plain text ledger I’ve been calling R throughout this series. ...

By this point in the pipeline, the boring parts are done. New files have been copied to the cutting board. I’ve picked out the ones that are my daughter. What’s left is the step that turns “a pile of selected files” into “a browsable month in her archive.” That’s one button. By now the picker has already moved my chosen files into a hand-off folder. In the app’s My Records tab, there’s a count of what’s waiting in that folder, and next to it a button that says, in effect, bring these in. I press it, and the rest happens on its own. ...

There’s a boring step in the middle of this pipeline, and it’s the step that used to kill the whole thing. Photos land on the NAS from two phones. Before I can sort them, someone has to copy the new ones onto the working folder — the cutting board — while skipping everything already handled. That’s dull, repetitive, and easy to forget. For two years, “I’ll copy them over later” was where the process died. ...

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. ...

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. ...

Every time I type a prompt that actually matters — one that solved a real problem or unlocked something I didn’t know how to do — I prefix it with //. That double slash is a convention I made up. It tells my Claude Code hook: this one is worth keeping. The hook saves it to a file. Eventually I want those files to feed an app that writes blog drafts automatically. That is the plan for episode 20 of this series. ...

There is a 1974 German theology book that exists in almost no library. One copy lives with its owner here in Korea. He wanted it translated into Korean. I offered to help. First step: get it scanned properly. I visited a professional scanning company. They said the book needed to be taken apart — pages separated, binding cut — before they could run it through their equipment. I relayed this to the owner. He said: do not cut this book. The scanning company said: then we cannot help you. ...