3 ms·

To put it more bluntly, this resume is really just not very visually pleasing. I definitely wouldn't recommend drawing so much attention to your HTML/CSS skills

by jchendy 12y ago

To put it more bluntly, this resume is really just not very visually pleasing. I definitely wouldn't recommend drawing so much attention to your HTML/CSS skills unless they're really outstanding. And even then, going through Codepen is unnecessary because anybody who's going to be evaluating your front end code knows how to open the console and look at your code anyway.

gr3yh47 12y ago
isn't there a distinction to be made between design skills and coding ability though?
- chrisparsons 12y ago
  Yes, but the problem is you hit that no-mans-land between "I'm going to just format text in a readable way" and "I'm going to try to make this look nice", and missed both. If you're going to start styling it (and in resumes, once background color enters into the picture, that's styling it), you really need to clean it up and make it look nice. Otherwise, going for a simple resume that's just text is probably going to serve you better. I'd admittedly probably toss this resume as-is. (Also, what about a DL for your experience rather than header/list?)
- chc 12y ago
  To some degree, yes. When you're talking about CSS skills, the distinction is somewhat blurred, because getting things to look right is a big part of front-end programming. Creating things that look bad reads as sloppiness. When you're working for a client and faithfully implementing the client's designs, this is particularly unfair, but it's still the case even then. At any rate, the ability to make a rudimentary web page with HTML and CSS is not exactly impressive. I assume that's why jchendy said "… unless they're really impressive." Like, cool tech demos with HTML and CSS probably would help get you hired, but making a '90s-tastic resume is not even in the same neighborhood.