Proof of Work

Think about the last time someone tried to convince you they were good at something.

Now think about the last time someone just showed you their work.

One of those needed your buy-in. The other already had it, before a word was said. That gap is the whole subject here, and most people are standing on the wrong side of it.

Promising Versus Proving

Proof of work isn't shouting for attention. It's quietly demonstrating: here's what I built, here's what it did.

Not a pitch. Not a portfolio deck. Just a visible thread connecting what you've done to the value it created.

It isn't supposed to sell. It's supposed to show.

Meanwhile most people are still tweaking bios, rewriting taglines, optimizing headlines, trying to build a reputation out of words instead of work. And the person who just shipped something real already has the credibility the words are chasing.

Cal Newport calls this career capital: real skills, demonstrated through real output, are what create opportunities. Not passion, not positioning, not a clever tagline. His argument is that "follow your passion" is bad advice and "get so good they can't ignore you" is the actual mechanism.

Which sounds obvious said out loud. Then look at how the time actually gets spent. Most people are optimizing the pitch instead of improving the product.

The Proof That Lands Isn't the Polished Version

Here's what I think people get wrong.

They hear "proof of work" and picture a highlight reel. The best stuff, curated, shot well.

But the proof that actually moves someone is rarely the polished case study. It's the thing that solved a real problem, even when the process was ugly getting there.

I've shipped projects before they felt ready. I've delivered final versions that looked nothing like what I pitched, because the build taught me something the plan didn't.

When I built my portfolio site I redesigned it three times before shipping. The first version was technically fine and completely hollow, a resume in a nice outfit. The second was overdesigned, trying too hard to impress. The third one just showed the work: real projects, what they did, what I learned. That's the one that opened doors.

And the client projects that came from it weren't the ones with the prettiest case study. They were the ones where the work clearly solved something specific, so a real business with a real problem could look at it and think, this person gets it.

That's the proof. Not the screenshot. The thinking visible behind it.

Building in Public Versus Performing It

There's a culture now of building in public that is often just performing the appearance of building. Screenshots of dashboards. Revenue numbers. Posts about the grind.

Some of it is real. A lot of it has quietly become its own genre of curation.

Nassim Taleb has the sharpest filter for this, and it comes out of his skin in the game argument, which is that credibility requires exposure to risk.

So: are you sharing because you're genuinely building and the visibility is a byproduct? Or are you performing "builder" as an identity?

The audience can tell. Maybe not immediately. Eventually the signal separates from the noise, because one of them has consequences attached and the other only has aesthetics.

Sahil Lavingia is the clearest modern example of the real version. He built Gumroad and shared every number publicly, including the failures and the layoffs. Not as a content strategy. Radical transparency just turned out to be the strongest trust engine available to him. He didn't pitch Gumroad. He showed the numbers and let people decide.

Why It Compounds

When the work is visible, you stop having to explain yourself. The right people notice, not because you asked, but because they saw something and recognized it.

Every project you ship is a trust signal, and unlike a pitch, trust signals stack.

Austin Kleon wrote the book on this, and Show Your Work is essentially a permission slip for people who hate self-promotion. You don't need to be an expert to share. You need to be learning and building visibly. The process is the product.

That's the part that compounds. It was never about one project or one launch. It's the body of work accumulating, where each piece adds credibility to the next and each shipped thing makes the next one easier to believe.

I think about this with my own stuff. Every site, every system, every brand. None of them were perfect. All of them were real, and the thread connecting them says something no bio rewrite could.

The Quiet Part

The irony is that the people with the most proof of work talk about it the least. They don't need to explain what they do, because the work is sitting right there.

The people who talk about it most are usually compensating for work that isn't.

So the question worth sitting with: if you stripped away the descriptions, the titles, and the context, would the work still say anything?

That's the only test that matters, and it doesn't care how good your headline is.