The Nintendo way of adapting technology is not to look for the state of the art but to utilize mature technology that can be mass-produced cheaply.
This is the reason a Nintendo console never has the fastest chips or the beefiest specs of its generation; instead, its remixes components in an interesting and generative way. Think of the Gameboy’s monochrome screen, the Wii’s motion controller, the Switch’s smartphone form.
[Gunpei Yokoi] is talking about reliability and predictability, in performance and supply alike. He wants the components to be boring, so their application can be daring.
This visualization takes the current New York Times Best Sellers list for combined print and e-book fiction and scales each title according to the demand for its e-book edition at a collection of U.S. public libraries, selected for their size and geographic diversity.
This is a kind of manifesto about the difference between liking something on the internet and loving something on the internet.
It’s also an experiment in a new format: a “tap essay,” presenting its argument tap by tap, making its case with typography, color, and a few surprises.
The mandate from above is clear, just get it done! Avoid everything that's in the way: all advice, all expertise, all discovery efforts that detract from hitting the Date™!
What these organizations don't realize is that all software change can be modeled as three components: Value, Filler and Chaos. Chaos destroys Value and Filler is just functionality that nobody wants. When date pressure is applied to software projects, the work needed to remove Chaos is subtly placed on the chopping block. Work like error handling, clear logging, chaos & load testing and other quality work is quietly deferred in favor of hitting the Date™.