A portfolio when your work is not visual
Writers, analysts, engineers and operators have proof too. How to show work that produces documents and decisions, not screens.
Topic
Portfolios
9 articles.
Showing work you signed an NDA about
Most professionals cannot show their best work. What is actually permitted, and how to make the constraint visible instead.
How many projects belong in a portfolio
Adding work usually weakens a portfolio. The arithmetic behind that, and how to decide which projects to cut.
Portfolio PDF versus portfolio website
The deck still wins in some hiring processes and loses badly in others. Which one to send, and how to keep both current.
GitHub profile versus a portfolio site
A profile shows that you code. A portfolio explains what you decided. When the README is enough and when it is not.
Building a portfolio when you have no client work
The chicken-and-egg problem, treated seriously. Which substitute projects convince a reviewer and which ones they discount.
How to write a case study someone will finish
The structure that survives a sceptical reader: the problem, the constraint, the decision you made, and what actually happened.
Behance versus your own portfolio site
A Behance profile is discovery. An own site is control. Where each one earns its keep, and why the split is not obvious.
The portfolio that gets you hired, and the one that gets skipped
How portfolios are really reviewed: fast, sceptically, on a phone. What survives that reading, and what quietly loses you the job.