7 ms·

Author here, thank you for the feedback. I'm a little bit confused by your comments, though. Can you point out a particular page and some specific improvements

Author here, thank you for the feedback. I'm a little bit confused by your comments, though. Can you point out a particular page and some specific improvements you think would help? I admit that I'm not a great UX designer, I would appreciate help in refining my approach.

reaperducer 8y ago
While I agree that the line-height could use a little work, don't take any criticisms from the HN crowd to heart. It often seems like half the people here are only happy on original DEC VT-100 terminals, and the other half are only happy if they can transform the web into an Xbox game. And if all else fails, remind yourself that Craigslist, fleaBay, and PayPal didn't become billion dollar companies by throwing around a bunch of gradients, animated GIFs, or whatever the latest craze is.
- smt88 8y ago
  My criticism was specific: the site is confusing to use. It's hard to find what I want. I gave reasons for this. Generalizing about the HN community has nothing to do with what I said. If you specifically think that most text and links should be the same, that buttons and non-buttons should be undistinguished rectangles, and that margins should bump up against the sides of the browser, then please say so and explain why you think these things are better for usability.
  - reaperducer 8y ago
    Calm down. I was addressing the author, not you. If I wanted to be critical of what you wrote, I would have replied to your comment. I didn't. Decaf.
    - smt88 8y ago
      Commenting without the presumptive and condescending "calm down" and "decaf" would make your point just as effectively without making you come across as petty and/or unable to argue unemotionally.
      - deleted 8y ago
        [deleted]
      - hitekker 8y ago
        Don't worry about it, dude. The GP made a childish and pathetic attempt at bullying, because you dared to question his straw man. Just ignore the trolls.
smt88 8y ago
It's absolutely fine to be a not-great UX designer. I'm also not a great UX designer. The way you wrote and posted this article, there was an implication to me (and I'm guessing to others) that you think this design philosophy is better than what most other people are doing. The article would benefit from some qualifications, e.g.: "I'm still teaching myself UX and aesthetic design," for example. As it is, it comes across as a strong argument from someone who thinks he's an expert (and thinks other people's design decisions are wrong). In terms of resources, you could take a full-semester class just about typography. Designing UIs is really hard and requires a ton of research. I've spent hundreds of hours over the last 10+ years just reading books and articles, and I still consider myself an amateur. My strong recommendation is to pay someone who is great at UX and understands how to accommodate people with physical disabilities. Even people who are just 40+ years old (and not disabled in any way) are getting significantly less light coming through their retinas, and it's possible to choose fonts and colors that are difficult for them. You can find someone who could revamp your stylesheet in a couple of days, and it shouldn't cost you more than $1k-$2k with the right person on Upwork. You seem to be great at a lot of other things, so why not find someone who has equal depth at UX design? As a generalist myself, I often rely on specialists because it's truly impossible to be great at a large number of fields. If you want to take a DIY, some good initial resources are: - https://alistapart.com https://alistapart.com (note that its design is very functional and minimal, but still uses fonts, colors, and whitespace in a helpful way) - https://www.smashingmagazine.com/category/ux-design/ https://www.smashingmagazine.com/category/ux-design/ - https://designmodo.com/design/ux-design/ https://designmodo.com/design/ux-design/
- Sir_Cmpwn 8y ago
  >The way you wrote and posted this article, there was an implication to me (and I'm guessing to others) that you think this design philosophy is better than what most other people are doing. The article would benefit from some qualifications, e.g.: "I'm still teaching myself UX and aesthetic design," for example. As it is, it comes across as a strong argument from someone who thinks he's an expert (and thinks other people's design decisions are wrong). I thought I covered this pretty well in the conclusion: "I’m not a particularly skilled UI designer, so keeping it simple like this also helps to make a reasonably nice UI attainable for an engineer-oriented developer like me." Outside of that, thank you very much for the resources.
jakelazaroff 8y ago
Some things that stand out to me: - In the header, it looks like you're using the same text style for the inactive navigation links as the helper text ("Logged in as"). - Icons should be used to help clarify things, but most of the icons seem to be just arrows pointing right on links. You can probably omit them! - In the source tree, I had no idea I could click on the file names until I hovered over them by chance. Blue text alongside black text is a very strong signal that the blue text is a link and the black text is not. (Also note that in the file path at the top, the ancestor directories are blue and clickable while the current directory is black and not). Here is where an icon would be useful: to disambiguate between directories and files. - Not a visual UX issue, but an accessibility one: for whatever reason, keyboard navigation doesn't work for me in Firefox. In general, just try to have consistent styles for things, and consistently different styles for different things. Links should look like links, not unclickable text. It's okay if you take a bit of artistic license in specific places (like the main navigation) but things should at least be internally consistent within that place.
- Sir_Cmpwn 8y ago
  Thanks for the feedback! >Icons should be used to help clarify things, but most of the icons seem to be just arrows pointing right on links. You can probably omit them! I discussed my opinion on icons in the article, and I stand by it in this case. > the source tree, I had no idea I could click on the file names until I hovered over them by chance. Blue text alongside black text is a very strong signal that the blue text is a link and the black text is not. (Also note that in the file path at the top, the ancestor directories are blue and clickable while the current directory is black and not). Here is where an icon would be useful: to disambiguate between directories and files. Good point. I don't want to add an icon, but I should make filenames underlined or something like that. >for whatever reason, keyboard navigation doesn't work for me in Firefox. That's bizarre, it works fine for me. Can anyone else reproduce this?
  - jakelazaroff 8y ago
    Re: icons, sorry if I was unclear — I'm not suggesting you add more icons, and I think your opinion in the article is good! I'm saying that it's not obvious to me what the right arrow means specifically, and (IMO) it's common enough that it adds visual clutter. For example, in the tree summary, "browse" and "log" have the right arrow, but the repo URL under "read-only" doesn't, and it's not clear why.
hyperpape 8y ago
I'm not a designer, but: On the file page, the links at the top (git, builds, todo, etc) have a hover effect, the links to ~sircmpwn and git.sr.ht do as well. The links to summary, tree, log, refs and contributors do not. From context, it's easy to guess that they're links, but they should share a hover effect with one of the other links.

reaperducer 8y ago

While I agree that the line-height could use a little work, don't take any criticisms from the HN crowd to heart. It often seems like half the people here are only happy on original DEC VT-100 terminals, and the other half are only happy if they can transform the web into an Xbox game. And if all else fails, remind yourself that Craigslist, fleaBay, and PayPal didn't become billion dollar companies by throwing around a bunch of gradients, animated GIFs, or whatever the latest craze is.

smt88 8y ago
My criticism was specific: the site is confusing to use. It's hard to find what I want. I gave reasons for this. Generalizing about the HN community has nothing to do with what I said. If you specifically think that most text and links should be the same, that buttons and non-buttons should be undistinguished rectangles, and that margins should bump up against the sides of the browser, then please say so and explain why you think these things are better for usability.
- reaperducer 8y ago
  Calm down. I was addressing the author, not you. If I wanted to be critical of what you wrote, I would have replied to your comment. I didn't. Decaf.
  - smt88 8y ago
    Commenting without the presumptive and condescending "calm down" and "decaf" would make your point just as effectively without making you come across as petty and/or unable to argue unemotionally.
    - deleted 8y ago
      [deleted]
    - hitekker 8y ago
      Don't worry about it, dude. The GP made a childish and pathetic attempt at bullying, because you dared to question his straw man. Just ignore the trolls.

smt88 8y ago

It's absolutely fine to be a not-great UX designer. I'm also not a great UX designer. The way you wrote and posted this article, there was an implication to me (and I'm guessing to others) that you think this design philosophy is better than what most other people are doing. The article would benefit from some qualifications, e.g.: "I'm still teaching myself UX and aesthetic design," for example. As it is, it comes across as a strong argument from someone who thinks he's an expert (and thinks other people's design decisions are wrong). In terms of resources, you could take a full-semester class just about typography. Designing UIs is really hard and requires a ton of research. I've spent hundreds of hours over the last 10+ years just reading books and articles, and I still consider myself an amateur. My strong recommendation is to pay someone who is great at UX and understands how to accommodate people with physical disabilities. Even people who are just 40+ years old (and not disabled in any way) are getting significantly less light coming through their retinas, and it's possible to choose fonts and colors that are difficult for them. You can find someone who could revamp your stylesheet in a couple of days, and it shouldn't cost you more than $1k-$2k with the right person on Upwork. You seem to be great at a lot of other things, so why not find someone who has equal depth at UX design? As a generalist myself, I often rely on specialists because it's truly impossible to be great at a large number of fields. If you want to take a DIY, some good initial resources are: - https://alistapart.com https://alistapart.com (note that its design is very functional and minimal, but still uses fonts, colors, and whitespace in a helpful way) - https://www.smashingmagazine.com/category/ux-design/ https://www.smashingmagazine.com/category/ux-design/ - https://designmodo.com/design/ux-design/ https://designmodo.com/design/ux-design/

Sir_Cmpwn 8y ago
>The way you wrote and posted this article, there was an implication to me (and I'm guessing to others) that you think this design philosophy is better than what most other people are doing. The article would benefit from some qualifications, e.g.: "I'm still teaching myself UX and aesthetic design," for example. As it is, it comes across as a strong argument from someone who thinks he's an expert (and thinks other people's design decisions are wrong). I thought I covered this pretty well in the conclusion: "I’m not a particularly skilled UI designer, so keeping it simple like this also helps to make a reasonably nice UI attainable for an engineer-oriented developer like me." Outside of that, thank you very much for the resources.

jakelazaroff 8y ago

Some things that stand out to me: - In the header, it looks like you're using the same text style for the inactive navigation links as the helper text ("Logged in as"). - Icons should be used to help clarify things, but most of the icons seem to be just arrows pointing right on links. You can probably omit them! - In the source tree, I had no idea I could click on the file names until I hovered over them by chance. Blue text alongside black text is a very strong signal that the blue text is a link and the black text is not. (Also note that in the file path at the top, the ancestor directories are blue and clickable while the current directory is black and not). Here is where an icon would be useful: to disambiguate between directories and files. - Not a visual UX issue, but an accessibility one: for whatever reason, keyboard navigation doesn't work for me in Firefox. In general, just try to have consistent styles for things, and consistently different styles for different things. Links should look like links, not unclickable text. It's okay if you take a bit of artistic license in specific places (like the main navigation) but things should at least be internally consistent within that place.

Sir_Cmpwn 8y ago
Thanks for the feedback! >Icons should be used to help clarify things, but most of the icons seem to be just arrows pointing right on links. You can probably omit them! I discussed my opinion on icons in the article, and I stand by it in this case. > the source tree, I had no idea I could click on the file names until I hovered over them by chance. Blue text alongside black text is a very strong signal that the blue text is a link and the black text is not. (Also note that in the file path at the top, the ancestor directories are blue and clickable while the current directory is black and not). Here is where an icon would be useful: to disambiguate between directories and files. Good point. I don't want to add an icon, but I should make filenames underlined or something like that. >for whatever reason, keyboard navigation doesn't work for me in Firefox. That's bizarre, it works fine for me. Can anyone else reproduce this?
- jakelazaroff 8y ago
  Re: icons, sorry if I was unclear — I'm not suggesting you add more icons, and I think your opinion in the article is good! I'm saying that it's not obvious to me what the right arrow means specifically, and (IMO) it's common enough that it adds visual clutter. For example, in the tree summary, "browse" and "log" have the right arrow, but the repo URL under "read-only" doesn't, and it's not clear why.

hyperpape 8y ago

I'm not a designer, but: On the file page, the links at the top (git, builds, todo, etc) have a hover effect, the links to ~sircmpwn and git.sr.ht do as well. The links to summary, tree, log, refs and contributors do not. From context, it's easy to guess that they're links, but they should share a hover effect with one of the other links.