Gifts of knowledge to humanity There are many commonalities we can admire in these endeavors: the dazzling leap of imagination, the broad scope of applicability, the founding of a new paradigm. But let’s focus here on their form of distribution. These are all things that are taught. To “use” them means to learn them, understand them, internalize them, perform them with one’s own hands. They are free to any open mind. In Hamming’s world, great achievements are gifts of knowledge to humanity. Bret Victor, The Art of Doing Science and Engineering: Learning to Learn knowledge
Hamming-greatness Hamming-greatness is tied, inseparably, with the conception of science and engineering as public service. This school of thought is not extinct today, but it is rare, and doing such work is not impossible, but fights a nearly overwhelming current. Bret Victor, The Art of Doing Science and Engineering: Learning to Learn
Up and Down the Ladder of Abstraction An Essay by Bret Victor worrydream.com The most powerful way to gain insight into a system is by moving between levels of abstraction. Many designers do this instinctively. But it's easy to get stuck on the ground, experiencing concrete systems with no higher-level view. It's also easy to get stuck in the clouds, working entirely with abstract equations or aggregate statistics. This interactive essay presents the ladder of abstraction, a technique for thinking explicitly about these levels, so a designer can move among them consciously and confidently. From a roving viewpoint abstractionunderstandinginteraction
The Ladder of Abstraction An Essay by Bret Victor worrydream.com Collaborative Information Architecture at Scale informationthinkingcommunicationabstraction
A Brief Rant An Essay by Bret Victor worrydream.com Like, just a post complaining that screens should be better designtechnologywwwinteractionbody
The Future of Programming A Talk by Bret Victor worrydream.com programmingcodetechnologyinteractionsoftware
A grossly obese set of requirements Who advocates in the requirements process for the product itself—its conceptual integrity, its efficiency, its economy, it’s robustness? Often, no one. As often, an architect or engineer who can offer only opinion based on taste and instinct, unbuttressed as yet by facts. For in a classical Waterfall Model product process, requirements are set before design is begun. The result, of course, is a grossly obese set of requirements, the union of many wish lists, assembled without constraints. Usually, the list is neither prioritized nor weighted. The social forces in the committee forbid the painful conflicts occasioned by even weighting, much less prioritizing. Frederick P. Brooks, Jr., The Design of Design Requirements proliferationA Plea for Lean Software features