3 ms·
Architects and engineers can usually show you what they've done in the past. Software developers can't if they don't have side projects. Artists have portfolio
by rootlocus 9y ago
Architects and engineers can usually show you what they've done in the past. Software developers can't if they don't have side projects.
Artists have portfolios. Why shouldn't software engineers?
- coldtea 9y agoBecause artists are usually sitting on their asses waiting for work, not already working 60 or 80 hours per week churning code.
- rootlocus 9y agoIf you're working 60 or 80 hours per week churning code, surely you have some code to show. </sarcasm> Really now, the fact that you can't showcase what you've done for your previous company is an implementation detail. Using a portfolio to judge a candidate is perfectly valid and works great with other industries. The reasons why you don't have one are your own concern. Like I said in other comments, interviewing is (for better or worse) a game / competition. You need to optimize for success.
- coldtea 9y ago>If you're working 60 or 80 hours per week churning code, surely you have some code to show. </sarcasm> Yeah, if you work for GNU or for countries were NDA is not a notion </sarcasm>.