4 ms·
If you're a (junior) front-end developer, then use the website to show off your skills. In other words make it responsive, accessible, use js libraries _when it
by laurentl 8y ago
If you're a (junior) front-end developer, then use the website to show off your skills. In other words make it responsive, accessible, use js libraries _when it makes sense to do so_, maybe some visual bling (background effects, scroll snap, a nice design). Https obviously, clean css, small page size, must load quickly.
The reason I'm recommending this: I recently looked for a junior web developer, in the zero-to-little experience range (combined work & school curriculum). I received more than 50 CVs, all stating that they were fluent in HTML/CSS/js.
Less than 10 of these had personal web page links. I looked at all of these web pages, and they were a big factor in who got an interview. Off the top of my head, I don't think we interviewed a single person who didn't have a personal resume/portfolio webpage, because we already had a pool of candidates who demonstrated that they had an actual practical experience of building a web site.
- kqr 8y agoAll the things you mention are boxes I intend to tick. But I'm not really interested in junior web dev roles; I'm more of an algorithms kind of a person. The reason for making a good web page is more to indicate that I am as much of an allrounder as I say, that I attention to details, and that I care about communication.
- laurentl 8y agoI agree that it’s (mostly ?) about signaling. I mentioned the junior web dev profiles because it happened a few weeks ago and because this is precisely a situation (lots of candidates, little to no priors to judge on, similar profiles / education) in which signaling plays an important role. A personal website is interesting in that there are many dimensions on which you can show your attention to details, from design to hosting.