I think when Jeff Atwood says "portfolio" he means not just things you'd put on your resume, but source code and publicly available articles you've written, and for some reason a twitter account.
But not just "I developed that closed source project, over there." That's what everyone has on their resume.
-- Ninja Edit---
Actually I just looked at Jeff's other article, and apparently what he calls a "portfolio", is what I call a well written resume.
Where/when you worked should be just a company name and a date. That's it. It should be followed by a very brief description of what you did there.
So OP's resume would contain something like:
- Lumera (2002-2006):
I was solely responsible for version 1.0 of the software and led the team that did version 2.0.
How exactly is he going to put up an online portfolio, or a link to a website, when he works in embedded software/hardware. Not everything programming related is done for the web!
Besides, your link that you have provided means nothing since I can't see your source code... unless you are going for a job as a front end coder of course.
He has made tons of cash, built amazing stuff. Run and sold a start up and is currently running a small company. He has enough cash to retire, but he is one of the folks to whom retirement doesn't mean not working. He doesn't have a blog, his idea of social network is probably his linkedin profile, nothing more. And he doesn't harp and tweet about every single discovery he is making every two hours(which is pretty common today). He just works like crazy, gets work done, makes his money as silently as he can.
There are a lot of folks like these, but they are hidden, they keep to themselves. Make enough money doing what they like. And are generally at places they want to work at. You can't really interview such people. Because they choose you, you don't get to choose them.
So clearly common interviewing techniques are not for guys like these. And most of these guys don't work at big Web giants.