jblock

That said, it does abstract much of the crap that goes along with XMLHttpRequests and all the cross-browser idiosyncrasies that go along with it.

I'd say at this point it's a matter of personal preference and performance requirements.

I've found that on nights where I have trouble sleeping, taking 20 minutes and writing out every single thought in my skull (into a notebook; not onto a computer) pulls me out of the mental block and brain thunderstorm that is resisting calls to slumber. When it's out on paper, it becomes real. It doesn't sit and dwell as an empty, half-complete thought.

College is a place to gain knowledge from those that have more than you. If you see it as anything else (especially anything malicious) then you're looking at it from the wrong angle and coming in with the wrong attitude. A motivated person can gain a lot of insight and knowledge from even the shittiest of situations.

College classes are a completely valid way to learn things. If you think that you're entrepreneurial dreams will be fulfilled if you drop out, then go for it. Some people don't learn that way, and that's just as acceptable. There are problems with higher education, and some places more so than others. But don't be so vain as to denounce the entire institution of higher education from a single anecdotal data point.

This is impossible to use.

This doesn't take into account the fact that not all photos are stock photos, not all monitors are good at rendering fine serif fonts on dark backgrounds, some users need affordances for buttons and interactors, and that the fluid grid with no spacing whatsoever between content areas makes some information nearly impossible to scan.

We have to learn how to ride a bike and type on a computer. The user doesn't know how to do everything, nor do they have the intuitive reasoning to pick up and use something completely new and alien. While we should make them feel smart, there's room to teach them and make them feel enlightened with this new system. Contextually, a UI walkthrough may or may not be a good idea.

Have some common sense.

Odds are that a good amount of buyers either don't care or haven't noticed the problem. It's not kicking their customers in the nuts. They poorly structured the evaluation method to set a threshold for repair and are having to backtrack and fix an expensive quality control mistake.

They're not kicking me in the nuts. They're a company of humans that has to deal with a problem in a way that satisfies their suppliers, shareholders, and engineers. I've found greater success in approaching problems like this with rationality. With lots of noise, maybe the test will change (only 30 seconds on the grey screen will make a metric shit-ton of the units qualify for replacement).

Is corporate trying to sweep it under the rug? Maybe. But this is a costly repair for a part that is in incredibly high demand. It's not right and I'm frustrated about it, but I'm not surprised.

...and no one has mentioned the headline? :)

I get it. IE is better. Just don't insult designers/developers you're trying to impress by half-assing proper semantics.

There's a difference between mindless capture and capture with a purpose. Some people do it terribly (I've been to a few really nice restaurants, and have had the experience nearly ruined by my friends' attempts to take snapshots of the admittedly beautiful meals), but that shouldn't dissuade the idea of wanting to capture an important cultural experience. Hell, I've never been to Disneyworld, and you'd bet your ass that I'd want a picture with Mickey.

It wasn't enough to bullshit. It could only take you so far. You only did well if you could surgically read into what was written and explore it prosaically and pragmatically.

Disagree. That's outwardly more efficient, but it turns out that when we're tasked with sorting and arranging ourselves, we do this whole boarding a plane thing pretty efficiently (especially when we have a vague sense of our chances of finding a convenient spot for our bags or a good seat).

But seriously, hanging indents, a very minor textual hierarchy, your Masonry layout is messed up, etc.

It all looks very unprofessional. KISS is your friend unless you are a master of making these complex responsive sites. Fix your voice, too. This is your site. Don't write it like a biography if the site itself is an autobiography (unless you're really funny and clever about it, which you aren't).

The purpose of a site like this is to allow people to find out more about you. What you've done mashed your entire professional life into a really, really long document that only looks passable on mobile phones. Figure out what you want to say. Make it CLEAR. Use CONTRAST. Put those pictures on your flickr page and link to it.

Personal pet peeve: don't tell me how experienced you are at a certain language or technology with a percentage--show me some shit you made.

Sorry, but a Wiki is about content, not looks.

And I'd rather not see a bunch of "test" articles with one paragraph or so. Show me some dense, complex content, and maybe I'll grow interested (that and not having it 500 every 30 seconds).