In college I studied theoretical math. I had plenty of friends in the computer science department and took a lot of their classes, but I veered toward computability, which is the theoretical part of CS that borders on philosophical. How to actually make a computer do anything useful was not my focus.
So I didn’t leave college as a developer (although I did once write a Scheme interpreter in Scheme, so there’s that). And while I’ve had a technical job my whole career, I’ve never crossed over from understanding how something works to being able to build it myself.
Claude closed that gap. I’m using it a ton at work, of course, for messaging and personas and all the product marketing things you’d expect. This post isn’t about those. It’s about the things I built in the evenings and weekends that I never would have known how to do before.
Welcome to my science fair.
Exhibit 1: The grocery list
My first project was a shopping list that syncs between my phone and any browser. It’s a single-user app, and the app itself was the easy part. I asked for changes like hitting Enter instead of clicking a button, a “frequently used” list, and a better way to sort items into categories, and those all went fine. I’m currently working on being able to paste a URL and extract shopping list items from a recipe.
What would have stopped me from doing this previously was everything around the app: where to host it, how to sync it between devices, how to log in. That “meta” work is the part of development I’ve always found hardest to grok. With Claude, I got my first Firebase account, used my first API key, and did my first remote debugging. Mobile got sticky with caching and refreshing, but we found a fix.
I learned a lot.
Exhibit 2: Alexa, add milk
The next rev was adding things to the list by voice. There were several ways to do it, and most of them failed for small, maddening, tactical reasons. Like you can’t just say, “Alexa, add milk to my shopping list,” because Alexa uses her built-in shopping list. Finally, we got something close enough working with a Lambda function, and it took hours.
This was the project where I started to side-eye the claims that Claude writes production-ready code in minutes. If it’s that accurate, wiring up Alexa should be easy, right? Instead I spent an afternoon on it. And this is a grocery list. Upside: I got to complain about a poorly implemented API, which made me feel legit.
Exhibit 3: Sudoku, delivered
I’m obsessed with a very niche corner of the internet called variant sudoku. (Yes, I’ve been called a nerd my whole life.) I wanted a task in Todoist every time a certain YouTube channel posted a new puzzle, skipping some puzzle types and linking straight to the puzzle instead of the video. I also wanted the puzzles from a weekly Substack email subscription pulled out and turned into tasks.
This one had no front end at all, just scripts. I learned about RSS feeds, Gmail parsing, Apps Script, and the YouTube Data API.
I also got bolder. On the grocery list I mostly did what Claude said. Here I vetoed ideas and brainstormed alongside it. At one point I noticed some API tokens were stored as environment variables and others were sitting right in the code, and I knew the environment variables were the better way. I told Claude to fix it, and it did.
Here’s the thing, though: it made me wonder what else I didn’t know that would be “wrong” or “unoptimized” in my app.
Exhibit 4: My own Todoist
There’s nothing like procrastinating on a Gartner Magic Quadrant submission to spur innovation. This summer, I decided I needed a custom front end for Todoist with a work-only view because I use it for personal tasks too. That grew into a work-only triage inbox, a hotkey for new tasks, a one-click tag for things I want done before I shut down for the day, and my favorite, a “boomerang.” When I ask someone to get back to me, I can mark the task done and a new one pops up two days later to check in.
The biggest thing I learned is that at this point, Todoist is kind of irrelevant. I could swap in any task manager, or write my own. That made me think about how much a good UI used to set a product apart, and how easy it can be to personalize front ends today.
The other thing I learned is the difference between firebase deploy --only hosting and firebase deploy --only functions, which I mention only so you know I earned it.
Exhibit 5: Bedtime, engineered
My daughter falls asleep to white noise. My son falls asleep to the Celtics or the Red Sox on the radio, and then needs white noise once the game is over. I wanted both on their Echos, playing from their own Spotify accounts so my own late-night podcasts wouldn’t get bumped. (We pay for Spotify Family! This should be easy!)
Reader, it was not easy. Claude’s first idea was a custom Alexa skill. Then it cheerfully discovered that Alexa Routines could do the whole thing with no code at all. Then we discovered that Alexa links one Spotify account for the entire house. So it was back to the custom skill, a Lambda function, and a long afternoon of devices that didn’t show up, a 404 that wouldn’t go away, and me accidentally pasting a live access token into the chat. At one point Claude told me to try Postman. I work at SmartBear. I called the whole thing an emotional rollercoaster, and Claude didn’t argue.
In the end we dropped Spotify entirely. The white noise is now an audio file in an Amazon S3 bucket, and a custom skill plays it on a loop. For my son, a routine plays the game, waits 15 minutes, then hands off to the white noise. (His white noise lives in his sister’s bucket. Please don’t tell him.)
My next idea was to add a capability for them to be prompted to set their alarm for the morning when they turn on their white noise. Except Alexa no longer allows “set an alarm” to be triggered by a routine. Because why would you want to do something so…basic. So that stays on the backlog for now.
The last exhibit: git
When I wanted to keep my code somewhere safer than my laptop, I asked Claude to teach me git. For the first few commits, Claude had me type every command myself in the terminal, the commit messages and all. Then, somewhere along the way, it just started doing it for me. The same thing happened for my Firebase app files. The first few times, Claude gave me the edits to make, then at some point it just started making them directly.
Existentially, I wonder: Do I even need to learn git on my own?
Part of me says yes, obviously. I root my Android phone. I open the Windows command line on purpose. I’ve always taken pride in knowing how things work under the hood. But part of me recognizes that hardly anyone knows assembly anymore, or even how to write HTML by hand. Does that matter?
On the grocery list, I learned every layer because I wanted to. Over time, this varied. Sometimes I liked setting up all the technology pieces and learning how it all worked. But what started to become more fun was learning to clearly define the boundaries of what I wanted, not doing the work.
Stay tuned, my science fair is never over.