I Rested. Then Shipped An App in 72 Hours.

December 28th. Three days after Christmas.

I was lying on the couch, scrolling through nothing in particular, when I realised something uncomfortable: I was bored.

Not tired. Not burnt out. Just... bored.

For the first time in months, my brain had nothing demanding its attention.

No bugs to fix. No features to ship. No urgent Google Chat messages about my meeting agent. Just empty space.

And in that empty space, an idea appeared.

Three days later, I had a working app.

The Break Worked (Too Well)

A month ago, I wrote 5 Founder-Approved Tips for a Christmas Reset. The core message: founders need real breaks. Not "I'll just check email once" breaks. Real ones.

I took my own advice.

I switched off. I spent Christmas doing decidedly non-productive things. I went on a long trip with my wife, and it was a lot of fun.

By December 28th, I was genuinely recharged.

And the funny thing about being recharged? Your brain doesn't just sit quietly. It starts looking for things to do.

The Idea That Wouldn’t Wait

I was just scrolling through Twitter (sorry, X, but I'm never calling it that naturally) when I noticed something: everyone was sharing their year-end recaps.

Spotify Wrapped dominated my feed. Since 2016, Spotify's annual recap has become a cultural phenomenon, with users eagerly sharing their listening statistics on social media each December.

The recap format has been mimicked by rival platforms like Apple Music and Amazon Music, as well as other services like Duolingo and Reddit.

Then it hit me: developers don't have this.

Sure, GitHub shows your contribution graph. But it's not shareable in that same satisfying, social-media-friendly way.

So, I was thinking, how do I turn these commits, pull requests, issues, and code reviews into a social image? Something visual. Something people could actually post.

That's when TrustPRR was born.

72 hours to ship

I started building on December 28th. By December 31st, I had a working app.

TrustPRR takes your GitHub activity and transforms it into a polished, shareable image. Your commits. Your PRs. Your reviews. All visualised in a format designed for social media.

Three days. From idea to deployed product.

Now, I want to be clear about something. This wasn't some superhuman coding sprint fuelled by caffeine and no sleep. It was the opposite.

I was well-rested. My brain was working properly. I wasn't context-switching between twelve different priorities. I had clarity.

And that clarity made everything faster.

Why Rest Enables Speed

Here's what I've learned about building while burnt out versus building while rested.

When you're exhausted, your brain struggles with decisions. Every fork in the road requires conscious deliberation. Should I use this library or that one? Should I structure the code this way or that way? Each choice burns cognitive resources you don't have.

So you stall. You defer. You go down research rabbit holes looking for certainty that doesn't exist. Hours pass without meaningful progress.

A rested brain works differently.

Decisions feel intuitive. You can hold more context in your head at once. You see the whole problem instead of getting lost in pieces. Trade-offs are clearer. The "good enough" threshold is easier to identify.

I've been building things for years. The work itself hasn't changed. But the speed varies wildly based on my mental state.

December 28th through 31st was fast because my mental state was good. Simple as that.

The ‘Momentum’ Element

There's another factor worth mentioning: urgency.

Not manufactured urgency. Not "I should ship fast because hustle culture says so." Real, external urgency tied to the idea itself.

Year-end recaps are a cultural moment. Everyone packages their year into something shareable right around now.

That moment has a window. Late December. Early January. Miss it, and the idea loses most of its relevance.

I recognised that window. And I had the capacity to move.

If this idea had struck in October, I might have written it down and returned to it later. But it struck during the window, with a rested brain ready to execute.

Sometimes timing aligns. When it does, you move.

Where TrustPRR Stands Today

The app exists. You can use it right now at trustprr.vercel.app.

Don’t worry. No credit cards needed.

You just need to sign in with your GitHub account.

But I'll be honest: it's not polished yet. Three days get you functional, not perfect. I have some UI improvements I'd like to make. Features I want to add. Rough edges I can see clearly now that the build sprint is over.

But it works. It ships. It does the thing.

(What should I add- Need some advice here!)

I built it primarily to visualise my own GitHub contributions heading into 2025. The fact that other people might find it useful is a bonus. Maybe it goes somewhere unexpected. Maybe it stays a fun little side project.

Either way, I'm glad it exists!

The Meta-Lesson

So what's the takeaway from all this?

Take your breaks. Real breaks.

Step away from your main work completely. Let the compulsive cycle interrupt itself.

But don't feel guilty if ideas find you anyway. Don't force yourself to ignore genuine creative energy just because you're "supposed" to be resting.

The goal is to break the compulsive cycle, not to punish yourself for having ideas.

And if something time-sensitive lands in your lap? If there's a genuine window that won't stay open?

Maybe that's worth three days.

You'd be surprised what a rested brain can build.

Try TrustPRR today. It's free. No credit card needed.