Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Sanding UI

blog.jim-nielsen.com

Post reply on HN
Print view View original

331–340 of 414 posts

Re: Sanding UI

#331

Post by beryilma »

noisy_boy wrote: post #201
crazygringo wrote: post #86

Earlier quoted context omitted.

What does agile have to do with anything? You think waterfall explicitly provided time to test out the UI and "sand" it? This is a process that generally requires a product manager to choose to prioritize, together with a capable UX engineer and/or designer. That prioritization can be inserted into any development methodology if you want it. Agile is irrelevant here.

Agile is relevant here because it has been adopted almost universally as a shovel to push more things on the programmer's back without much care to the quality of the changes being done. Sure, it is not to be blamed as per Agile manifesto but how many companies are adhering to the manifesto? It is how it is used, not what it was used for.

> Sure, it is not to be blamed as per Agile manifesto but how many companies are adhering to the manifesto?

Increasingly, I am also blaming the Agile Manifesto for causing the mess we are all in.

Given current business tendencies, the authors should have probably foreseen the future consequences of their wishy-washy manifesto declarations. I think "true Agile has never been implemented" should not absolve them from assuming some responsibility.

Re: Sanding UI

#333

Post by itronitron »

jagged-chisel wrote: post #210
aetherspawn wrote: post #83

This is so lost in Agile. Engineers should get the time to “sand” their products, but we just don’t. If QA doesn’t make a ticket for the space between, it’ll never get fixed. The customer probably notices this kind of a thing but it’s a miracle if the customer bothers to report it, and another miracle if it eventually turns into a ticket, and another miracle if someone prioritises it enough to spend time fixing it. […

I feel like this goes along with the recent Artisan Software discussion on HN. Companies don’t want Software Artisans.

Thanks, I think I just discovered my new job title :)

Re: Sanding UI

#335

Post by [deleted] »

aetherspawn wrote: post #83

This is so lost in Agile. Engineers should get the time to “sand” their products, but we just don’t. If QA doesn’t make a ticket for the space between, it’ll never get fixed. The customer probably notices this kind of a thing but it’s a miracle if the customer bothers to report it, and another miracle if it eventually turns into a ticket, and another miracle if someone prioritises it enough to spend time fixing it. […

[deleted]

Re: Sanding UI

#336

Post by bsoles »

invaliduser wrote: post #109

Anecdata, but I found the very same issue (the bermuda triangle gap between radioboxes, but also checkboxes, and their labels) in a project a few months ago. It seemed a pretty big deal to me, specially because I always clicked on the gap, and got frustrated and angry at this. So I reported it to the UX team managing the design system, and to the developers implementing the design system, and nobody really cared. Som…

Most software engineering has become the modern equivalent of assembly line workers, which brings about the concept of alienation from our work products, per Marx. It is all about productivity metrics and nobody actually cares about non-measured forms of quality and artisanship.

Re: Sanding UI

#337

Post by chrisweekly »

mattlondon wrote: post #167
geysersam wrote: post #127

Earlier quoted context omitted.

I like the IDE "defined here/used here" features but I wish the page would be faster. It can be quite painful to read code on GitHub. The code view is also broken and unusably slow in some mobile browsers (Firefox) when scrolling horizontally

This sort of problem (speed) is a much overlooked secondary functionality requirement IMO. You might get amazing UX mocks and wireframes and designs etc from the UX team, and the mockups from Figma or whatever may have user-tested really well, but if there is huge latency in the real implementation then that is a usability-killer IMO, regardless of how polished the UI is.

Agreed! Performance is the most important feature.

Re: Sanding UI

#338

Post by cezart »

ansgri wrote: post #307
rollcat wrote: post #235

Earlier quoted context omitted.

I really wish we had something resembling a "native" UI toolkit, but for the web. Just throw together a couple s or es with absolutely zero additional JS/CSS, but have it actually look & work moderately decent, the way SwiftUI does. CSS is too powerful, OOB HTML is too basic/ugly.

Bootstrap started as something like this, but it both evolved too quickly IMO, and for some reason a generic look on the web is considered bad (by who? marketing? designers? even users as they think lack of distinctive style means lack of developer skills?)

I still just throw in default bootstrap in a .container div when I need a fast prototype that looks decent.

Re: Sanding UI

#339

Post by chrisweekly »

pentagrama wrote: post #34

Is so important have people with that spark to see and fix those little UX issues, a good analogy used on UX design is papercuts for the user, not critical but it degrades user satisfaction. To the author I will add that that radio button is not following the convension of a dot for the selected state instead of a check. Users may think at first sight that multiple/no selection is possible.

Agreed. What "Papercuts" is on the negative side, "Juice"^1 (recently discussed here on HN) is to the positive.

1. https://garden.bradwoods.io/notes/design/juice

Re: Sanding UI

#340

Post by 0xedd »

ccakes wrote: post #91
xyst wrote: post #80

I wonder what’s the most polished or “sanded” UI out there? You would think FAANG would have a half decent UI and UX with the amount of money they have. But anybody that has used Amazon.com or AWS, GCP, or even Azure would beg to differ. Personally, off the top of my head. The most polished UI/UX has to be “mcmaster.com”. I can find anything I need in what seems like a couple minutes. Compare this to big box stores l…

imo GitHub has to be up there. I think some of the recent changes to search and making the code view more IDE-like are steps backward from a “polish” perspective, but still useful features

[dead]
Post reply on HN