I disagree with the article and the notion that asking for a portfolio is about passion. I guess it does add insight for that, but really only shows basic profi

I disagree with the article and the notion that asking for a portfolio is about passion. I guess it does add insight for that, but really only shows basic proficiency. I wouldn't hire an artist, writer or designer without seeing a portfolio of their work so why would I hire a software developer? I too have been on both sides of the hiring discussion. Because anyone can write anything on there resume, there are only two way to know if someone can code. They can write some code of they can show some code they have written. As both an interviewer and interviewer I would rather work with real world problems and discuss real world solutions. So the choice seems to be between stupid whiteboard processes or portfolios. I suspect there is a reason writers and painters don't have auditions and perhaps that same logic maps onto programming.