Via BBC Future: Dyslexie is a typeface by Christian Boer that helps dyslexics read better with asymmetrical letter forms, bold capitals, and increased length of “the up and down sticks” — ascenders and descenders — to allow differentiation and therefore better legibility.
Research conducted at the University of Twente has shown that dyslexic readers make fewer mistakes when reading text in Boer’s font, while eye tracking experiments conducted at France’s University of Lille also have shown that the gaze of dyslexics’ children flows more easily across a page of text using the font than other more traditional fonts.
Interesting move from Starbucks in an era of more and more commerce being done eletronically and at a distance. The goal? To become an “experiential destination” and compete with Amazon by only being offered — via a human connection — in stores.
CEO Kevin Johnson says, “To survive, merchants need to create unique and immersive in-store experiences.” Though I tend to prefer local coffee merchants, I still end up at Starbucks for the consistency and convenience.
Does that include drive-through? What about mobile orders where you just swing in without speaking to anyone? In both cases you’d still experience the smells and sights, and possibly interact with a human. Which is a good thing — human connections build trust, trust builds brand loyalty.
Photo note: I’ve recently started asking for a “real” mug at my local store, to see how it feels.
Technical update from my colleague Alister for how WordPress.com uses automated tests for build confidence, now running for on GitHub pull requests instead of after deployment to production. The tests and webhook “bridge” infrastructure are open source just like the Calypso source code itself.
At WordPress.com we strive to provide a consistent and reliable user experience as we merge and release hundreds of code changes each week.
We run automated unit and component tests for our Calypso user interface on every commit against every pull request (PR).
We also have 32 automated end-to-end (e2e) test scenarios that, until recently, we would only automatically run across our platform after merging and deploying to production. While these e2e scenarios have found regressions fairly quickly after deploying (the 32 scenarios execute in parallel in just 10 minutes), they don’t prevent us from merging and releasing regressions to our customer experience.
Introducing our Canaries
Earlier this year we decided to identify three of our 32 automated end-to-end test scenarios that would act as our “canaries”: a minimal subset of automated tests to quickly tell us if our most important flows are broken. These tests execute after a pull…