I agree it's not always necessary to have a portfolio, I've still not built one and it's never been a problem in interviews. I've thought of it as a 'nice to have' though, so I'm curious to know how it counted against some of the candidates you interviewed?
Ah I see, yea that makes sense. I've come across a few portfolio sites where it felt more like an opportunity to try out new tech or ideas, rather than what's appropriate for the portfolio.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I agree it's not always necessary to have a portfolio, I've still not built one and it's never been a problem in interviews. I've thought of it as a 'nice to have' though, so I'm curious to know how it counted against some of the candidates you interviewed?
Over-engineering, JS errors, failing to work on some browsers, excessive bloat, inappropriate choice of technology... etc.
Ah I see, yea that makes sense. I've come across a few portfolio sites where it felt more like an opportunity to try out new tech or ideas, rather than what's appropriate for the portfolio.