What a portfolio doesn't tell you (including mine)
A portfolio is a highlight reel. Every project in it ended well, looks good in a screenshot, and has a short, confident caption. That's not dishonest. It's just that the part of the work you're hiring for, the part where something goes wrong on a Wednesday and someone has to deal with it, never makes the reel.
I have a work page, so I'm part of this. Here's how to read portfolios, mine included, with some skepticism.
What it hides
Who did what. "Built by" can mean a person, a team, or a person plus a template plus a freelancer. A beautiful result tells you nothing about which part was the author's.
The constraints. A site built on a tiny budget in two weeks and one built over six months can look the same. Only one of those tells you what the person is like under pressure.
Whether it's still alive. Projects age. A site that was fast in 2021 may be slow now because nobody maintained it. Some links on any portfolio are broken or redirect somewhere else.
What went wrong. There is always something: a scope change, a delayed asset, an integration that didn't behave. How it was handled is the real skill, and it's invisible.
What the numbers mean. A card that says "fast" or "78% mobile" is a claim, supplied by whoever built the page. It might be perfectly honest. You still can't check it from the card.
Six questions to ask anyone
- Which part did you do? Design, code, both, or something in between?
- What were the constraints? Budget, deadline, team size, existing systems.
- Is it live, and who maintains it? Open it. Does it still work on your phone?
- What went wrong, and what did you do about it? A good answer is specific and a little unflattering.
- Can I talk to the client? Not every client will agree, but willingness to try tells you something.
- How did the scope change? Projects drift. A person who can describe the drift honestly has done real work.
If someone can't answer these without getting vague, you've learned something a gallery of screenshots never would.
What my work page leaves out
You'll see 17 projects, dated from 2020 to 2026. Some are old. Style and tooling change, and a 2020 store doesn't represent how I'd build today. I'd rather the dates be visible than pretend the list is all current.
I also don't publish a full case study for every project. A case study makes claims, and I only turn one on after I've checked each claim, so most rows link out to the live site instead. That's slower and it means fewer long write-ups than you may see elsewhere. I think it's the right trade.
And the work page won't show you my bad weeks. For that, the build log of this site is closer to the truth than any project card.
What to do with this
Don't hire on screenshots alone. Open the live site on your phone, ask the questions above, and, if the project is big enough to matter, ask for a small paid first step before committing to the whole thing.
I'm happy to answer all six about anything on my Work page. Ask me, and I'll tell you what I did, what I didn't, and what I'd change.
Have something in mind?
Let’s talk