e. When researching this post, I discovered that Bongard problems were first popularized by a brief discussion in GEB—which I had entirely forgotten.2 It turns out that Hofstadter’s analysis develops some of the same themes as “How To Think”; I return to them in this post.3
Summary: To decide whether to visit a page, people take into account how much relevant information they are likely to find on that page relative to the effort involved in extracting that info.
Web superhero @dracos wrote up how he vastly improved the performance of the UK government Coronavirus data website. Spoiler alert: "The important thing is to have a resilient base layer of HTML and CSS, and then to enhance that with JavaScript."
“Problem-solving is always messy and most solutions are shaped by political agendas and resource constraints. The solutions that win out are not necessarily the best — they are generally those that are favored by the powerful or at least by the majority.”
A much-overlooked portion of design’s value is that poor design is very costly to an organization. Poor design can increase development costs through rework and waste.
Reflecting on the last couple months. Keep coming back to the wonderful experience of finishing a book with @searchlight5 and the rest of the @Amplitude_HQ teams. When vendor ebooks are a dime a dozen, I'm proud we put love and care into this (1/2)
Quantitatively evaluate a product or service’s user experience by using metrics to gauge its relative performance against a meaningful standard #UX #benchmarking #metrics
I see my term “data literacy isn’t binary” making the rounds. So great! We should be talking more about how it isn’t @lukestanke. I wrote about it for the data viz topic of the week On @DataVizSociety - join us on slack while we talk about this topic.