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
Beyond Artboards An Essay by Chuánqí Sun medium.com The Pursuit of Lossless Design-Development Handoffs. Can't developers just see?We are the ones who paved the pathUntil we get there processinterfacesdesign
Can't developers just see? We designers love artboards. From rough UI sketches to high fidelity mockups, we see ourselves as visual artists expressing ideas on artboards that have a pre-defined width and height. To start a new project, we declare the size of the artboard in the first step. What about responsive design? Not a problem! We diligently design on three artboards — one for mobile, one for tablet, and one for desktop — with content elegantly adapting, scaling, reflowing, reordering, and reprioritizing. We proudly hand off the artboards to developers while patting ourselves on the back: this is how responsive design should be done. After weeks of arduous engineering, the product finally comes out. We find, to our great dismay, that some copy is hanging off the grid, the focal point of the hero image has been cropped out, the font sizes don’t even come close to the type ramp. What went wrong? Can’t the developers just see everything on all those artboards? Nope. Start drawing, then put the box around it
We are the ones who paved the path No matter how many screen sizes our artboards account for, some user’s browser will break loose from our prescription. With users resizing, rotating, and zooming the screen, new devices stretching, squashing, curving, and cutting (e.g. the speaker area in iPhone X) the screen, the sizes become infinite. Good luck making an artboard for each one of them. Artboards are a lossy format. Using artboards in a handoff is a lossy process. When we pitch a finite number of plans against an infinite number of situations. We inevitably get in-betweens. Once there are in-betweens, there are unknowns. Once there are unknowns there is guesswork. Once there is guesswork, there are surprises. Engineers take the path of least resistance. We are ones who paved the path. gridless.designChanging Our Development Mindset
Until we get there As a designer, learn writing HTML, or better still, semantic HTML. If coding up the entire design is too hard, try coding up one component at a time, and not worrying about CSS. The HTML alone will prove invaluable for developers to understand the content structure. In addition, you are forced to optimize the information architecture as you work out the code from content. If coding by yourself is out of the question, pair up with the engineer who will receive the design. Work closely with him or her to prototype the design, validate responsive behaviors, and obtain feedback on the feasibility. Don’t call it an iteration until the design has seen played with in code. As a manager for large enterprise, co-locate your designers and developers, encourage interdisciplinary learning, understand that each minute spent on coding before the handoff translates to ten minutes saved from changing and fixing issues after the handoff. As a stakeholder in the handoff meeting, give the designer a thumbs-up when he or she demos live code running in browsers in place of mockups on artboards. That’s a design champion you are looking at. html