While "[l]ooking at a code portfolio for people who program is fundamentally no different from looking at past experience, at educational credentials, or at any

While "[l]ooking at a code portfolio for people who program is fundamentally no different from looking at past experience, at educational credentials, or at any of the other standard resume screening techniques..." may be true, I think that it sidesteps another important consideration: What does requiring a code portfolio signal to potential applicants about the employer? Does it signal that the employer will be inconsiderate of those who can't share their professional work, or those who don't have lots of spare time for side projects? Does it signal that an employer is more interested in the placement of curly-braces than the ability to communicate verbally? Does it signal that the employer is solely interested in getting tomorrow's work done, or do they balance increasing the value of their codebase with increasing the value of their employees?