You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
When I worked on flash mem (2001), I read the literature on how it worked. At the time, the exact physical mechanism by which some things happened wasn't understood. There were theories, but multiple theories were consistent with what was observed. But we can make flash reliable!
And to the extent that it's not reliable, we can describe when we expect it to be unreliable and what the odds are. Someone might argue that this is equivalent to "understanding", but that's your point, I think -- the talk is so vague it can mean whatever you want.
He has this idea that composing simple components is the way to make robust systems and that abstractions over complexity are worthless.Sounds reasonable, but we manage to build reliable chips even though the underlying physical mechanics we abstract over are tremendously complexpic.twitter.com/ESbBbYQKgB
The big productivity boosts have been abstractions that hide but don't eliminate underlying complexity. Gate-level design instead of transistor-level design, RTL instead of schematic capture, synthesis instead of doing raw circuit design, etc.
Later, he says you should just use data structures because they're "simple". Imagining the same idea in EE: no gates, only do layout because it's simpler. Metal, poly, and n/p-wells are "simple", why complicate things with gates? We're EEs, it's all physical layout in the end.pic.twitter.com/uEiZ1CY7Zk
As for software, why have data structures? Memory is actually very simple. There are not a tremendous number of variations in the essential nature of memory. There are locations that contain addresses. There are locations that contain values. There are not a lot of other concep
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
