The art of not constructing It would be well if engineering were less generally thought of, and even defined, as the art of constructing. In a certain important sense it is rather the art of not constructing: or, to define it rudely, but not inaptly, it is the art of doing well with one dollar that which any bungler can do with two. Arthur M. Wellington, The Economic Theory of the Location of Railways Economy of material and labor simplicityengineering
The amount of work not done Simplicity—the art of maximizing the amount of work not done—is essential. Manifesto for Agile Software Development -2000 Lines Of Code simplicity
Economy of material and labor Whatever the comparative merits of [various bed framing methods], what is clear from Aristotle's Mechanica is that economy of material, and labor, was as much an issue in ancient times as it is now. Henry Petroski, The Evolution of Useful Things The requirements of economyThe art of not constructing simplicity
To be truly simple Why do we assume that simple is good? Because with physical products, we have to feel we can dominate them. As you bring order to complexity, you find a way to make the product defer to you. Simplicity isn't just a visual style. It's not just minimalism or the absence of clutter. It involves digging through the depth of the complexity. To be truly simple, you have to go really deep. For example, to have no screws on something you can end up having a product that is so convoluted and so complex. The better way is to go deeper with the simplicity, to understand everything about it and how it's manufactured. You have to deeply understand the essence of a product in order to be able to get rid of the parts that are not essential. Jonathan Ive, Steve Jobs Less, but betterTool-being simplicity
Omit needless words When a sentence is made stronger, it usually becomes shorter. Vigorous writing is concise. A sentence should contain no unnecessary words, a paragraph no unnecessary sentences, for the same reason that a drawing should have no unnecessary lines and a machine no unnecessary parts. This requires not that the writer make all sentence short, or avoid all detail and treat subjects only in outline, but that every word tell. William Strunk Jr. & E.B. White, The Elements of Style Less, but better brevitysimplicityminimalism
Good design is simple Good design is simple. You hear this from math to painting. In math it means that a shorter proof tends to be a better one. Where axioms are concerned, especially, less is more. It means much the same thing in programming. For architects and designers it means that beauty should depend on a few carefully chosen structural elements rather than a profusion of superficial ornament. Similarly, in painting, a still life of a few carefully observed and solidly modeled objects will tend to be more interesting than a stretch of flashy but mindlessly repetitive painting of, say, a lace collar. In writing it means: say what you mean and say it briefly. When you're forced to be simple, you're forced to face the real problem. When you can't deliver ornament, you have to deliver substance. Paul Graham, Taste for Makers simplicity
Conversations, not commandments Good software comes from a vision, combined with conversations not commandments. In a craft-focused environment, care for efficiency, simplicity, and details really do matter. I didn’t leave my last job just because I wanted to make something new. I left because I wanted to make it in a way I could be proud of. Pirijan Ketheswaran, Why Software is Slow and Shitty pketh.org detailscraftsimplicityefficiency
Perfection It seems that perfection is attained not when there is nothing more to add, but when there is nothing more to take away. Antoine de Saint-Exupéry, Wind, Sand and Stars perfectiondesignsimplicitymaking
August short No. 2: Glass An Article by Riccardo Mori morrick.me Glass looks and feels perfectly tailored to my photo sharing needs and expectations. For me it’s even better than pre-Facebook Instagram in the sense that it pushes me to select and share what I think are good photos (same as it happens with Flickr), rather than making me obsess with getting ‘the Instagram shot’ at all costs every day or multiple times in a day. It doesn’t cheapen photography like Instagram has done for years. That’s why I hope Glass’s founders/developers will resist feature creep. Resist user objections like: I don’t think Glass is offering that much for the subscription price they’re asking. There are a lot of people who will gladly pay for having a cleaner, simpler, focused experience. featuressimplicityproductsphotography
The return of fancy tools An Article by Tom MacWright macwright.com Technology is seeing a little return to complexity. Dreamweaver gave way to hand-coding websites, which is now leading into Webflow, which is a lot like Dreamweaver. Evernote give way to minimal Markdown notes, which are now becoming Notion, Coda, or Craft. Visual Studio was “disrupted” by Sublime Text and TextMate, which are now getting replaced by Visual Studio Code. JIRA was replaced by GitHub issues, which is getting outmoded by Linear. The pendulum swings back and forth, which isn’t a bad thing complexitysimplicitytoolssoftwaretechnologynotetaking
In Praise of Small Menus An Article by Rachel Sugar www.grubstreet.com The best way to experience a restaurant, I have always felt, is by eating exactly what it wants to feed you. I do not want choices. I want the best thing. A restaurant might have five or ten best things, but it cannot have 45. There are many infuriating things about the world, but one of the more fixable is the sensation of acute regret from having ordered wrong. Why are there possibly wrong orders? Recently, I was at a fancy restaurant with great pastas and bad pizzas. So cut the pizzas! A kitchen that focuses on its strengths turns out consistently excellent things, even if that results in fewer total things. fooduxchoicesimplicity
Don't Rush to Simplicity An Article by Shawn Wang www.swyx.io You've probably heard this story before: A businessman finds a fisherman, who is living an idyllic, peaceful life by the sea. He laughs and tells the fisherman how to get rich instead. The fisherman asks him what he will do after he gets rich. He replies that he would retire to an idyllic, peaceful life by the sea. There's supposed to be a deep life lesson in there, but it's always felt insincere to me. To me it is better to have reached the heights of a career, or suffered an epic defeat, even if I do end up in the same place as everyone else in the end. To me simplicity is made more beautiful when understood through a long personal struggle with complexity. When I can dance with it, having turned a mighty nemesis into an old friend, and teach others to do the same. Better to have loved and lost, than never to have loved at all. On the other side of complexityMountains are mountains zensimplicity
On the other side of complexity A Quote "I would not give a fig for the simplicity this side of complexity, but I would give my life for the simplicity on the other side of complexity." — Oliver Wendell Holmes Jr. Don't Rush to Simplicity simplicitycomplexity
Who the fuck is Guy Debord? An Article by Robin Rendle www.robinrendle.com Long, unwieldy sentencesImagining her PsychogeographySuch tortuous syntax writingsimplicity
Product vs. Feature Teams An Article by Marty Cagan svpg.com This article is certain to upset many people. Empowered product teamsViability, usablity, feasibilityWhat went wrong? featuressoftwareagile
Empowered product teams When I wrote about the virtues of empowered product teams, I was referring to what I’ll continue to call here as product teams. Specifically, they are cross-functional (product, design and engineering); they are focused on and measured by outcomes (rather than output); and they are empowered to figure out the best way to solve the problems they’ve been asked to solve.
Viability, usablity, feasibility In an empowered product team, the product manager is explicitly responsible for ensuring value and viability; the designer is responsible for ensuring usability; and the tech lead is responsible for ensuring feasibility. The team does this by truly collaborating in an intense, give and take, in order to discover a solution that work for all of us. However, in a feature team, you still (hopefully) have a designer to ensure usability, and you have engineers to ensure feasibility, but, and this is critical to understand: the value and business viability are the responsibility of the stakeholder or executive that requested the feature on the roadmap. What went wrong? teamwork
What went wrong? If something ships from one of the companies I advise, and it is virtually unusable because of poor design (which as we all know occasionally does happen), you can bet I go directly to the designer and ask how this happened? It is absolutely on the designer to ensure this does not happen, so something went wrong. Similarly, if the product ships and performance is terrible you can bet I go directly to the tech lead with the same question. And most frequently of all, if something ships and the analytics show that it’s either not being bought or not being used, or it turns out that it violates some business constraint like compliance or privacy, you can bet I go right to the product manager with that question. Viability, usablity, feasibility