The problem is pervasive, and speaking in noncommittal terms perpetuates passive acceptance. We can take action through our democratically elected representatives by re-opening mental health institutions and drug rehab centers. And we can enable law enforcement to lock up violent offenders with the assurance that the defendants will be given due process instead of being released without charges.
Has anybody tried software intelligence tools? Seeing the architectural components and control flow of the code seems like a quick way to document the codebase and figure out which “clusters” to study.
https://en.m.wikipedia.org/wiki/Software_intelligence
spread operator shorthand for passing component props.
Suppose: const now = moment()
Then, you can pass it down to a component like this:
<TimeInput {...{now}} />
Which is equivalent to
<TimeInput now={now} />
With many props, it becomes easier on the eyes and differentiates from passing event handlers e.g. <TimeInput {...{now}} myHandler={this.handleKeyPress} />
I was unsuccessful in finding articles that offered a counterpoint. I’m curious if anyone in the HN community has insight to share given the preponderance of studies arguing the opposite of this meta study’s conclusion.
I used SlateJS a year ago and couldn’t be more impressed. It struck a great balance with minimalist architecture while also providing the React building blocks I’d rather use than create myself.
That would require real effort instead of storytelling during work hours.
Whoch is harsh, but that’s the point. You are going to get far more insight from real customers than you are from one relatively homogenous sub-department’s imaginary beliefs about who your customers might be.
IMO the latter is pretty much the definition of one of David Graeber’s bullshit jobs.
There's nothing more valuable than watching customers actually use a product. Almost never will they do it the way you expect, and absolutely never will they want to do it the way that the designer intended. Nothing points out a painful, complicated, broken, confusing UI as quickly.
It may make sense, when you have 10 users, but then you can just skip profiling (and, by the way, profiling real users, at least in EU, is strictly limited from legal perspective - it just doesn't worth it). When there are thousands of users, real customer contacts may create unnecessary bias. There's no "average" real person, which means that serving the needs of one real person, you may hurt others too much. Personas are synthetic profiles for a reason: they cover the whole audience of the project or feature.
