What I Learned Building an App at 73 — and Why It Changed How I Think About Our Stuff
Coffee & Code LLC ·I'm 73. Five months ago, I didn't know Swift. This is the app I built anyway — and what I learned along the way about building, AI, and the stuff we own.
A personal essay about building Stuffolio, learning something new later in life, and finding a calmer way to manage the things we own.
This wasn’t part of some grand plan. I just wanted something new to work on, something to keep my mind engaged. What I didn’t expect was that it would turn into an actual app.
It took much longer than I expected, with more than a few “Damn, I think I need to start over” moments along the way. But somehow it turned into something I’m genuinely excited to share.
It started with a manual
The idea for the app, which I eventually named Stuffolio, didn’t come from a brilliant insight. It came from standing in front of something that wasn’t working and thinking, I know I’ve seen the manual for this … somewhere.
That moment kept repeating itself.
I was always looking for the same things: manuals, serial numbers, setup instructions, repair videos, or trying to remember whether a warranty was still valid or had quietly expired. Sometimes the information was in a folder. Sometimes it was buried in an email. And more often than I’d like to admit, it was in “that drawer.”
You know the one.
Eventually, I had to admit that “that drawer” was not a filing system.
So I built something simple: a place to keep track of what we own, along with the information we actually need — warranty dates, manuals, support contacts, even online help videos. One place instead of twelve.
But as I worked on it, the questions got bigger.
The questions that changed the app
My wife and I started looking around our home and asking ourselves: Where did all of this stuff come from? And maybe more importantly, what are we eventually going to do with it?
Things have a way of accumulating quietly. Some we bought. Some were gifts. Others just seemed to appear over the years. Along the way, we assumed certain items would naturally become heirlooms — things we’d pass down to our daughters because they mattered to us.
What we’ve learned, sometimes gently and sometimes not, is that what feels meaningful to one generation doesn’t always feel that way to the next. Some of the things we thought our kids would treasure turned out to be things they simply don’t want.
That led to a different kind of question. How do you even talk with your kids about that? Not as a legal conversation, and not as something heavy or uncomfortable, but as a practical way to make things easier for them later?
So we tried it.
One evening, we FaceTimed our two daughters and walked through some of the things we’d always assumed they’d want. The oak school desk we’d picked up at a yard sale. A set of china that had been in the family for decades. Pieces we’d collected while traveling.
They were honest with us. The desk wouldn’t fit either of their lives. The china wasn’t their style. But a few things surprised them — items we’d almost overlooked meant more to them than we expected. And some things we thought were just ours, one daughter asked if she could have someday, while the other had no interest at all.
It was clarifying for everyone.
It wasn’t a difficult conversation. It was a relief.
What I noticed afterward was that none of us had been avoiding the topic, exactly. We just hadn’t had a reason to start it. Once we did, it turned out our daughters had been quietly forming their own opinions for years, the same way we had — and they were waiting for someone to ask. We agreed to do it again, with different items, whenever it felt natural.
That conversation changed what I was building. I added something I eventually called Legacy Wishes: a simple way to leave context behind. We could describe an item, note why it mattered, and indicate which of our daughters might want it. Just as important, it gave them a way to tell us if they didn’t. If neither wanted something, we could note whether to donate it, sell it, or let it go.
It wasn’t about control or planning everything out. It was about clarity — and removing a little uncertainty for everyone involved.
Learning something new later in life
Building the app became its own education.
I started the way a lot of people do now: watching instructional videos and trying things out, often without fully understanding what I was looking at. I spent a lot of time staring at development screens thinking, Well, that didn’t work.
Along the way, I discovered that modern AI tools could be surprisingly helpful. At first, it felt like they were doing too much of the work, and that made me uneasy and feel a bit like an imposter. But over time, something shifted. They stopped feeling like a replacement and started feeling more like an airplane — and I was the pilot.
They could help with navigation and smooth things out, but I was still deciding where to go and when to land.
As I got more comfortable, I noticed something else. I wasn’t just asking questions anymore. I was pushing back, debating answers, and occasionally correcting the tools themselves. Sometimes I was clearly the student. Other times, I found myself in the role of teacher.
That back-and-forth is where the learning really stuck.
The AI was the airplane. I was the pilot.
There’s a phrase people use dismissively these days: “AI slop.” It refers to apps and content generated by AI with no human thought behind them — things that work on the surface but fall apart the moment you look closely. Ship it and move on. I understand the criticism. I’ve seen those apps.
But that label gets applied too broadly. It assumes that if AI was involved, the human wasn’t. And that hasn’t been my experience at all.
Yes, AI wrote most of Stuffolio’s code. I’ll say that plainly. I didn’t know Swift five months ago — I couldn’t have written this app by hand. But what I did was something the AI couldn’t do on its own. I decided what the app should be, who it was for, and what mattered.
When the AI suggested using green and red for status indicators, I pushed back. I’m part of the roughly 8% of men with red-green colorblindness, and it was a chance to assert something most developers don’t even think about. I wanted the app to work for everyone, so I set clear accessibility standards. Colors could never carry meaning on their own. Important information had to be readable without guessing. And the app had to work properly with VoiceOver for people who rely on it.
Other times, the AI produced code that was technically correct but quietly wrong. Once, it generated a swipe-to-delete gesture for maintenance records — efficient, until I deleted one by accident and realized a confirmation step wasn’t optional after all. Small lessons like that accumulated.
Over months, those decisions became an 800-line document of standards: a colorblind-safe palette, accessibility rules, naming conventions, and patterns for styling and error handling. The AI didn’t write that document. I did, because I learned through trial and error that without it, the codebase would drift into inconsistency every time I added a feature.
That document is the artifact that separates development from “slop.” It represents opinions I formed by engaging with what the AI produced — questioning it, rejecting parts of it, learning from the parts that worked, and building a mental model of what good looked like for this particular app.
The AI was the airplane. I was the pilot. The flight plan was mine.
The moment it felt real
One afternoon, we were in a Goodwill store and came across a set of dishes that looked interesting. I took a quick photo, ran it through Stuffolio’s Stuff Scout feature, and learned just enough about what they were and what they were worth to make a simple decision.
We passed. We already have too much stuff.
That was the whole point. I wasn’t looking for a perfect answer. I just wanted enough information to decide and move on — the same kind of clarity I wanted to leave for our daughters.
What I’m still figuring out
Somewhere along the way, the technical questions gave way to more personal ones. Would someone know what this is? Would they understand why it mattered, or feel comfortable letting it go? Would the people I care about most be left guessing — or have enough context to decide for themselves?
I realized we don’t need more complexity. We need clarity, on our own terms.
That’s what I tried to build. And honestly, that’s what I’m still figuring out — like everyone else at this stage of life, trying to make a little more sense of the things we own and what they mean … if anything at all.
What mattered most was that the learning was still mine. The tools didn’t replace effort or judgment. They supported it. Slowly, things that once felt completely opaque started to make sense.
It reminded me that learning later in life isn’t about speed. It’s about curiosity, patience, and being willing to feel uncomfortable long enough for things to click.
Terry Nyberg, 73, lives in Colorado with his wife, two daughters’ worth of forthcoming inheritance decisions, and a junk drawer he’s stopped calling a filing system.
---
Every feature in Stuffolio started the same way: standing in front of something and not having the answer.
The warranty I couldn't find became a tracking system that tells me when coverage is about to expire and what's still actually covered when something breaks. The vacuum that broke six months after we bought it became a feature called Repair, Keep, or Replace, which pulls in repair costs, replacement prices, and the item's age to help make that decision without guessing. The dishwasher manual I swore was in the filing cabinet became a product memory that stores manuals, receipts, setup notes, and support contacts in one place.
And the conversation with our daughters, the one I almost didn't have, became Legacy Wishes.