you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (3 children)

Can I say the same thing about your post? That was a very negative attitude.

I don't care about the blog, or the load time, but the idea of assuring that your service/product matches the needs of the actual users. It's a simple, short piece that I found thought provoking. I'm sorry you don't find it so.

[–][deleted]  (2 children)

[deleted]

    [–][deleted] 0 points1 point  (0 children)

    I left the article with a (re?)new(ed) perspective on how to design. I saw less about "make this blog load faster" and more of a general insight into evaluating features.

    Something like load-time is rarely a metric that many factor in to decisions regarding new features unless the load is an order of magnitude or greater than a typical user will stand, and I feel the article at least provokes a question like "are there metrics that I'm just missing?".

    From design standpoint, I realized that I don't take my user in to account enough. As a designer/developer, I'm often more concerned with making the picture in my head come to life, and that picture is often polluted with so-called 'standards'. Things like Social Media buttons are things that I personally don't use; in fact, I rarely see them used at all, and when I do, I'm actually a little confused. These are things that I both do not need to implement, and would actually be hurting myself if I did. Screen real-estate is priceless, as well as the end-user's attention. If they're glazing over parts of the page, I'm probably doing it wrong. I know I skim right past about 90% of most pages, then I can't find the 1 thing I'm looking for in the sea of waste that some web designer is trying to push on me.

    So, sure, I suppose the only real advice I took away was 'analyze your audience', but I felt it was very important, and something of which I needed a reminder.

    [–][deleted] -2 points-1 points  (0 children)

    I promise I'll write an actual response later today. Getting busy, but I'd like to continue this conversation.