Building things solo is 80% self-doubt, 20% git commits.

Me, writing a function: “What’s the cleanest, most elegant way to solve this?”

Also me, 30 minutes later: doThing2()

Sometimes the hardest part of writing code is remembering what you named that one helper function three months ago.

Curious — where do you actually keep your reusable text or code snippets?

Notion? VS Code? Slack DMs? A sticky note on your second monitor?

(Asking for a friend. Kind of.)

#buildinpublic

There’s a quiet kind of productivity no one talks about:

- Reusing a good sentence
- Pasting a code block you already wrote
- Not reinventing the wheel at 11pm

Shipping faster starts with remembering what you already solved.

#buildinpublic

Some of the highest-leverage things I’ve ever written:

- A well-timed Slack message
- A helpful PR comment
- A reusable block of text

Not everything worth saving is code.

#buildinpublic

I’ve shipped client work, managed teams, launched side projects…

But this is the first time I’m building something just because I wish it existed.

It’s different. It’s harder. It’s better.

Building solo is weird.

Some days it feels like progress.
Some days it feels like pretending.

Still… one foot in front of the other.

(hello to the other folks building something small + useful out there 👋)

Freelancing taught me two things:

- Clients want speed and clarity, not cleverness
- "Let me reuse something I’ve already written" is the highest-leverage move in any project

Curious — what’s the one block of text or code you’ve copied more than 10 times this year?

I don’t journal.

I don’t meditate.

But I do refactor code to relax.

Close enough?

Code you rewrite 3 times becomes a function.

Text you rewrite 3 times… just gets rewritten.

Weird double standard.

Freelancers. Devs. Support folks.

We all do the same thing:

- Open Notion
- Copy a block of text
- Paste it into Slack/email/GitHub

I’m building something to make that less dumb.