Hacker News Reader

> Yes, for pure coders, this is a terrible resume. It looks like she is using the right side of the brain for something left-sided.

Urgh... I really hate to go into rant mode because I know what you're trying to say isn't really relevant to this. However, as an incredibly right-brained person who is a good programmer (or so I like to think :-) and has absolutely zero design skill, I'm always a bit annoyed by this. The whole "right-brained people are creative artists, left-brained people are engineers and scientists" is a 3 or 4 decade old view of how the brain works. Yes, the left brain tends to be a bit more textual while the right brain tends to be more visual, but that doesn't mean that right-brained skills aren't useful to coders or that left-brained people don't have design skills. And even if it did, people can still tap into the other side of their brain.

Ok, that's my rant for the day. :-)

:) rant appreciated. I actually harbor the same suspicions, but for the sake of general understanding it was the best way I could frame the issue.

> I would definitely spend some more time to look into the applicant.

So would I.

> Yes, I would never hire her for algorithm optimization, but if she was building a website that doesn't innovate technologically but rather creates social, cultural, aesthetic or other value (which the majority of startups do) - I would take a second look.

She'd also probably be good at doing design / front-end parts of a website while communicating with back-end developers (who might be doing algorithm optimisation).

I expect she'd be good at talking to designers from a coders point of view too.

This applicant I suppose. What about the next 50? I'd grow REALLY tired of trying to parse through all of it.

Isn't that true for just about anything (at first) original and novel?

but even as a designer she has failed to demonstrate good design sense. All she has demonstrated is that she's good at copying the en vogue style.

Agreed. But that's still better than many.

There must be thousands of jobs that want just that.

>but even as a designer she has failed to demonstrate good design sense

Can somebody explain what's wrong with this design?

It's flashy and harder to understand than more boring presentations?

I understand why it might not be a great resume, but what about the design. The Previous Work tree diagram is sort of neat, in text form the info that it conveys might be even harder to understand.

It's a bad design because it does a bad job framing the contents. It doesn't solve a problem, instead it creates several. It took me several times longer to figure out her resume than it does for a standard one, not to mention that I still came away not knowing several things that I would need to know.

As it stands, all I can say about her is that she has decent mastery of Photoshop but no understanding of good design.

tptacek did an excellent job of explaining it for you already. It sounds a bit like you are thinking of design as "making things pretty", and it's not. It's about communication.

The message this resume is communicating is that the author also feels that design is just about ornamentation, and the only way it could be more obvious is if the diagram were in the shape of a giant duck. I have to assume she doesn't actually believe that, not least since she hasn't asked for us to psychoanalyse her and it's really, really unfair to try to do so based on this completely decontextualised link. But even so, the design seems unsuccessful to me because it's communicating the wrong message.

Design is about communication, but it does not exclude ornamentation. Design can be ornamental (if the purpose of the resume is to highlight some design skill), however it should not reduce the readability of data as this one does. Having just read "The visual display of quantitative information" I have this to say to the designer of the resume: remove non-data ink. Increase data density and readability. Especially readability.

>Its easy to see if she has Ruby skills, for instance - but its hard to see the overall picture of what skills she has without spending a lot of time on it.

One can take her resume idea even further and create a CV in an interactive form, so it could meet everyones needs.

The issue of thinking in pictures versus words has always interested me. Wiki says[1] 30% of us are explicitly picture thinkers, 25% think in words and the rest combine both methods. Most entrepreneurs (not sure about the ones dealing with start-ups) tend to drift towards the right, because it's usually easier to generalize your idea by visualizing it, rather than coming to a logical conclusion by using words only. Which, I think, would be slower in this case. So, how come are most (if not all?) of the current cv-websites featuring only long walls of text?

[1] = http://en.wikipedia.org/wiki/Picture_thinking

Because all of what you said about how we think has nothing to do with the informational density of the two formats. Words trump pictures for complex ideas.

But isn't "maker of beautiful things" what designer/developers are really aspiring to? And in light of that, isn't recognizing the division just as silly as drawing a venn diagram with yourself in the middle?

I'd suspect anyone who calls themselves a designer/developer is probably good at other things to, like writing, designing meaningful infographics, and playing the resume game with subtlety.