Great article. I think you’re right - show the end result to grab their attention, but provide the process so they can understand how you got there.

You might also want to check what someone on the other side of the fence thinks. Since I’m a developer, I can suggest a great blog post from a guy who hires developers. I’ve been following Joel Spolsky’s blog Joel on Software for at least 15 years and it’s always insightful. His post on interviewing hits on your point “people hire people, not portfolios” precisely. I often tell people that “I can teach anyone to code, but I can’t teach them to ‘people’” [an exaggeration, of course] http://www.joelonsoftware.com/articles/GuerrillaInterviewing3.html