Stick like hell When the Wizard of Menlo Park called invention 10 percent inspiration and 90 percent perspiration, he was speaking not only about the creative act of inventing but also about the whole inventive process needed to bring more than intellectual success. Edison warned against discouragement during the perspiration phase in the following way, reminding us that we get things to work by the successive removal of bugs: Genius? Nothing! Sticking to it is the genius! Any other bright-minded fellow can accomplish just as much of he will stick like hell and remember nothing that's any good works by itself. You've got to make the damn thing work!...I failed my way to success. Thomas Edison, The Evolution of Useful Things inventionsuccess
More easily asked than definitively answered Some design questions are more easily asked than definitively answered. Inventors are seldom at a loss for problems, and so they must choose which ones they will work on. Henry Petroski, The Evolution of Useful Things inventionquestionschoice
We feel it in our fingers In System A, there is no architect separate from the contractor. We are builders, simply. As builders, we have a direct feeling about construction. We feel it in our fingers, so it is down to earth. One result of this down-to-earth quality is that everything is somewhat experimental. We make experiments all the time. Sometimes we place a piece of wood this way. Another time, we may like to try it that way. Any time something new comes up in the design of a building, we are very likely to try and invent the best way of building it. This is not a great big invention. Just a simple invention, the way we might invent a way of tying a piece of string, to hold a broken toy together. It is just practical. Christopher Alexander, The Battle for the Life and Beauty of the Earth In Defence of Intuition inventioncreativityproblems
History tends to be charitable History tends to be charitable. It gives credit for understanding what something means when we first do it. But there is a wise saying, “Almost everyone who opens up a new field does not really understand it the way the followers do.” The reason this happens so often is the creators have to fight through so many dark difficulties, and wade through so much misunderstanding and confusion, they cannot see the light as others can, now the door is open and the path made easy. Richard Hamming, The Art of Doing Science and Engineering: Learning to Learn invention
The word invents itself Posits certain neologisms as arising from their own cultural necessity—his words, I believe. Yes, he said. When the kind of experience that you're getting a man-sized taste of becomes possible, the word invents itself. David Foster Wallace, The Pale King wordsmeaningnoveltyinvention
The Evolution of Useful Things A Book by Henry Petroski Here, then, is the central idea: the form of made things is always subject to change in response to their real or perceived shortcomings, their failures to function properly. This principle governs all invention, innovation, ingenuity. Spike and sponShaped and reshapedForm follows failureTheir wrongness is somehow more immediateA small corner of the world of things+23 More The evolution of devices formfunctioninventionprogressfailure
Stepping stones in possibility space An Article by Gordon Brander subconscious.substack.com If we try to cross this lake by following only the stepping stones that lead toward our objective, we’ll soon get stuck. But what if we let go of our objectives? What if we focused on trying to find new stepping stones instead? This is novelty search. Instead of looking for something specific, you look for something new. Novelty search isn’t just random, it’s chance plus memory. Together, these ingredients do something interesting. ...Stepping stones are also combinatorial. Each new stepping stone we discover expands our potential to find even more stepping stones. Collecting stepping stones is a luck maximization algorithm. By collecting and combining stepping stones, we might arrive at our destination by accident, or somewhere more interesting! chanceknowledgeprogressnoveltyevolutioninvention
Ideas behind their time An Article by Tim Harford www.ft.com These days I am more interested in the reverse case [of Da Vinci's helicopter]: ideas that could have worked many centuries before they actually appeared. The economist Alex Tabarrok calls these “ideas behind their time” Curious minds want to know why these ideas appeared so late — and whether there might be anything that would prevent delays in future. One explanation is that the ideas aren’t as simple as they appear. The bicycle is not as straightforward an invention as it seems. To move from ox-hauled cart to human-powered bicycle requires smooth-rolling wheel bearings, which in turn need precisely engineered bearing balls. Modern steel ball bearings were not patented until the late 1700s, and demand from the 19th-century bicycle industry helped to improve their design. Materials and how to employ them inventionideas
Who Becomes an Inventor in America? The Importance of Exposure to Innovation A Research Paper www.nber.org We directly establish the importance of environment by showing that exposure to innovation during childhood has significant causal effects on children's propensities to invent. Children whose families move to a high-innovation area when they are young are more likely to become inventors. These exposure effects are technology-class and gender specific. Upstream, Downstream inventioninnovationchildhood
Age of Invention A Series by Anton Howes antonhowes.substack.com I’m a historian of innovation. I write mostly about the causes of Britain’s Industrial Revolution, focusing on the lives of the individual innovators who made it happen. I’m interested in everything from the exploits of sixteenth-century alchemists to the schemes of Victorian engineers. My research explores why they became innovators, and the institutions they created to promote innovation even further. Upstream, Downstream inventioninnovationhistoryindustry
The small web is beautiful An Essay by Ben Hoyt benhoyt.com I believe that small websites are compelling aesthetically, but are also important to help us resist selling our souls to large tech companies. In this essay I present a vision for the “small web” as well as the small software and architectures that power it. Why aim small?Features and complexitySolving the problem of software bloatRaw size isn't enough Rediscovering the Small Web wwwmicrosites
Why aim small? Why aim small in this era of fast computers with plenty of RAM? A number of reasons, but the ones that are most important to me are: Fewer moving parts. It’s easier to create more robust systems and to fix things when they do go wrong. Small software is faster. Fewer bits to download and clog your computer’s memory. Reduced power consumption. This is important on a “save the planet” scale, but also on the very local scale of increasing the battery life of your phone and laptop. The light, frugal aesthetic. That’s personal, I know, but as you’ll see, I’m not alone. performancesystemsconservation
Features and complexity Niklaus Wirth of Pascal fame wrote a famous paper in 1995 called A Plea for Lean Software. His take is that “a primary cause for the complexity is that software vendors uncritically adopt almost any feature that users want”, and “when a system’s power is measured by the number of its features, quantity becomes more important than quality”. A Plea for Lean SoftwareSpeed is a featureRequirements proliferation featurescomplexity
Solving the problem of software bloat But instead of just complaining, how do we actually solve this problem? Concretely, I think we need to start doing the following: Care about size: this sounds obvious, but things only change when people think they’re important. Measure: both your executable’s size, and your program’s memory usage. You may want to measure over time, and make it a blocking issue if the measurements grow more than x% in a release. Or you could hold a memory-reduction sprint every so often. Language: choose a language that has a chance. Remove: cut down your feature set. Aim for a small number of high-quality features. My car can’t fly or float, and that’s okay – it drives well. Say no to new features: unless they really fit your philosophy, or add more than they cost over the lifetime of your project. Dependencies: understand the size and complexity of each dependency you pull in. Use only built-in libraries if you can.
Raw size isn't enough A few months ago there was a sequence of posts to Hacker News about various “clubs” you could post your small website on: the 1MB Club, 512KB Club, 250KB Club, and even the 10KB Club. I think those are a fun indicator of renewed interested in minimalism, but I will say that raw size isn’t enough – a 2KB site with no real content isn’t much good, and a page with 512KB of very slow JavaScript is worse than a snappy site with 4MB of well-chosen images. ...[Instead, it's about] an “ethos of small”. It’s caring about the users of your site: that your pages download fast, are easy to read, have interesting content, and don’t load scads of JavaScript for Google or Facebook’s trackers. minimalismcontentsize