Working in public

Journal

Not the highlights. The whole thing.

What I'm shipping, what's stuck, what surprised me. Things I'm learning. Occasional strong opinions about design tools.

Showing 24 of 141

Minimus Weather
iOSSide Project

Apple's emails remember more than I do

I went looking for the history of this app last night, and there's almost nothing. No Cursor chats. No transcripts. My best guess is they lived in the project folder, and that folder got cleaned up at some point. All that's left is the app, the support site, four commits and a couple of chats where I talked about it.

WorkBrain
AIZoro

Did we just build it once?

I'm writing this journal, and today I realized I didn't actually know WorkBrain's own story. So I asked my work Claude Code: "Is it just one? Did we just build it once and then call it a day and continue using it?"

Gary
AISecond Brain

Two culprits

Gary's Friday reminders have been haunting me since June. They never had a time on them, so they never actually reminded me of anything. No alert, no little red badge telling me something was overdue. They just quietly appeared on my list. Then some Fridays there were two. So I made my own repeating reminder, the normal way, in the Reminders app, and asked Claude Code to cancel Gary's job. It said it did. It didn't. Every Friday since: my reminder, one of Gary's, and sometimes a second one of Gary's.

Gary
AISecond Brain

Nothing matches her Avoid list

This week I gave Gary my wife's Christmas wish list. He added all ten items to her page with prices, sizes and links, pointed out that the HydroPeptide moisturizer is the priciest thing on it but an easy pick since she loves two of their other products, and then checked the whole list against the things she's tried and didn't like. "No conflicts: nothing on the list matches anything in her Avoid section."

WorkBrain
AIZoro

Stop and figure out why

Claude Code was updating some content in our CMS today, and instead of editing an existing entry, it made a brand-new one. When I asked why, it turned out it couldn't edit the original, so it worked around the problem by making a copy and planning to delete the old one. I stopped everything: "If you can't edit what's there, we need to stop and figure out why, and not just try to recreate them and delete old ones."

WorkBrain
AIZoro

Five became two

Yesterday I went into the office in person, and Robyn flew in from Atlanta, because we knew that if the two of us got in a room with our marketing strategy lead, we could turn our open questions into real recommendations. Over the last few weeks, Robyn and I had already worked the sheet from 57 down to 12, and walked product and design leadership through those 12, one row at a time. That left five for the full steering committee. So yesterday, the three of us built a recommendation for each one.

WorkBrain
AIZoro

Three different dates

I ran a check on a project that's gone quiet for a while, and WorkBrain flagged something buried across several meetings: three different versions of the same launch date. Each one sounded fine when someone said it. Side by side, they don't agree. It didn't pick one. It asked me.

Gary
AISecond Brain

Hey Sam, Gary here. What's up?

This morning Gary's first reply was "Failed to authenticate: OAuth session expired and could not be refreshed." Claude Code signed itself out, and with nobody at the Mac Mini to sign it back in, Gary was just gone until I got home. Once he was back, he greeted me with "Hey Sam, Gary here. What's up?" Four times in thirty minutes.

WorkBrain
AIZoro

Two systems, one brain

Aaron rebuilt WorkBrain to run in Google Drive, because that's how he works, and now I have a new problem: two versions of the same idea, running side by side. Today I had to ask, "What I need to know is the order of operations. I have new notes I'd like to dump into the inbox in Google Drive. Do I then tell you to process it and update the documents in Drive and my local documents?"

WorkBrain
AIZoro

Seven meetings, one morning

I got back from a week off today, and seven Loyalty meetings happened while I was gone. Seven. Normally that's a morning of rewatching recordings and a week of feeling one step behind. Instead I dropped all seven transcripts into the inbox and let WorkBrain work through them. It even made a new project folder for the team meetings that didn't belong to anything else.

Storybook
Design SystemsZoro

What do we do with this now?

I'm not really sure what to do next here. I built this library as a side-quest and I feel a good sense of ownership about it. But it's been absorbed into the Design System. Our initial Design System work is complete, and now we hand it off to engineering to build and maintain, and set up the automations.

Gary
AISecond Brain

48 deploys a day

Vercel emailed today to say my free account is running out of storage. Ten gigabytes, for a couple of tiny websites. The site is supposed to publish only when something changes. But a log file changes every time Gary syncs, every 30 minutes, so the site has been publishing every 30 minutes: 48 builds a day, for weeks. The fix is one line. Stop tracking the log file. It actually took longer to clean up all the old build data in Vercel than it did to fix the automatic publishing.

LabelSpace
CodeZoro

Launch

LabelSpace is open to real users on real projects as of this week. Every new project starts there now, and once the last few older projects finish the old way, the spreadsheets are done. When people find a problem, I design the fix, build it and open the pull request, and it ships in the next release. In April, I wasn't sure "pull request" was the right term. Now I open them for my own fixes.

Storybook
Design SystemsZoro

Why does it feel like everything is breaking?

"Why does it feel like everything is breaking right now?" A mistake in how a component's variables were set up means editing one component silently edited all of them. Hours of work are gone, and it's due today. Twenty minutes later I asked for a retro: "Tell me what happened, step by step, so we can see where we went wrong." I wasn't calm about it. But asking an AI to walk back through its own mistakes is one of the most useful things I've learned to do.

WorkBrain
AIZoro

Muddying the water

I'm starting concept work today, and I already have a problem. Two related projects are blurring together in my head, and I said so out loud: "I'm starting to muddy the water between Full Loyalty and Rewards MVP, because they DO have" so much overlap. And then I admitted the other thing: "I'm mostly working backwards, because I jumped the gun a bit and started designing solutions."

LabelSpace
CodeZoro

Three piles

Launch is getting close, so every request from the data team now goes into one of three piles: critical for launch, nice to have, or backlog. Without the piles, launch would wait on everything. With them, we can say yes to the right things and "not yet" to the rest.

Storybook
Design SystemsZoro

The task board got too big to read

The task board from May has grown to almost 1,400 lines, about a megabyte, and every new AI session reads the whole thing before doing anything. We've also been asked to be more cost-efficient with our AI usage, and the board is a big part of the cost. So today I froze it, archived it and told Cursor to ignore it. The work coordinates through git now.

WorkBrain
AIZoro

Pulling the conflicts into a sheet

The Loyalty context file has everything from every meeting in it, including how the engineers plan to build it. That's great for me and useless for the steering committee. They don't need the engineering questions. They need the business and experience ones: how much we're willing to give away in discounts, and what customers will actually see. And some of those answers contradict each other, depending on which meeting you were in.

Storybook
Design SystemsZoro

No more dragging and dropping

Until today, the live library got updated by me dragging a build folder onto Netlify Drop by hand, on my own account. We don't have a hosting setup for designers, and the usual outside hosting services aren't an option for us. The free drag-and-drop version was fine when only one person was publishing changes. But there are five of us in here now, and we need a better way.

WorkBrain
AIZoro

Credit is now rewards

I started a new project in WorkBrain last week and called it "credit." Today it's "rewards," because we got asked to change the terminology. The folder has the new name, and the history still shows the old one, with the date and the reason. Anyone who opens it later can see what happened. That's the whole reason for the two rules, and it's nice to see one actually do its job.

Storybook
Design SystemsZoro

Storybook, not Confluence

Today we moved the elevation guidance out of Confluence and into Storybook, as the one place Figma gets aligned to, word for word. On the way, a table in the docs showed up as a row of literal pipe characters. Markdown tables needed one more setting turned on. Documentation is code now, and code has opinions.

WorkBrain
AIZoro

Just For You

We settled a naming question this afternoon: "Just For You" replaces "exclusive" on our deal badges and cards. I logged it in WorkBrain at 2:36. Eleven minutes later, I logged it again, this time as the official standing rule, so every project that touches deals uses it from now on. It's a small decision. But it's exactly the kind of thing that gets decided in one meeting and re-argued in the next three, and now it's written down where everything can find it.

WorkBrain
AIZoro

The transcripts keep getting names wrong

This week has been mostly corrections. A task got tagged to the wrong project. Two kinds of work I'd been lumping together turned out to need separate folders, so now they have them. People's names come through the transcripts misspelled, and their roles get mixed up. Today I corrected the same two people twice. First I said they were leadership. Then I realized they're leadership and genuine subject experts, not one or the other.

Storybook
Design SystemsZoro

Every one of them rendered at 16px

The new type scale went in, and some of the docs pages suddenly look flat. Headings and body text are the same size. The first migration pass only checked two kinds of files, and 61 other files set their type a different way, using names that no longer exist. When a name doesn't exist, the browser shrugs and uses 16 pixels. So every one of them rendered at 16px. We fixed 242 references across those 61 files. Then, while merging, I learned the migration script would quietly delete letter spacing from seven card labels if you ran it twice. Now it doesn't. Running it again changes nothing, which is how it should have worked the first time.

Only 117 more to go.