Writing, Briefly An Article by Paul Graham www.paulgraham.com As for how to write well, here's the short version: Write a bad version 1 as fast as you can; rewrite it over and over; if you can't get started, tell someone what you plan to write about, then write down what you said; expect 80% of the ideas in an essay to happen after you start writing it; start writing when you think of the first sentence; write about stuff you like; learn to recognize the approach of an ending, and when one appears, grab it. v0.crapThe situation talks back writing
Writing and Speaking An Essay by Paul Graham paulgraham.com Being a really good speaker is not merely orthogonal to having good ideas, but in many ways pushes you in the opposite direction...there's a tradeoff between smoothness and ideas. All the time you spend practicing a talk, you could instead spend making it better. writingspeechcommunicationpractice
Write Simply An Essay by Paul Graham www.paulgraham.com I try to write using ordinary words and simple sentences. That kind of writing is easier to read, and the easier something is to read, the more deeply readers will engage with it. The less energy they expend on your prose, the more they'll have left for your ideas. Several Short Sentences About Writing writing
The Age of the Essay An Essay by Paul Graham www.paulgraham.com EssayerExpressing ideas helps to form themFlow interesting (The Meander) Follow the brushThe Anxiety of Sequence writing
Early work An Essay by Paul Graham www.paulgraham.com Imagine if we could turn off the fear of making something lame. Imagine how much more we'd do. The right way to deal with new ideasFocus on the rate of change creativityskillideas
What doesn't seem like work? An Essay by Paul Graham paulgraham.com The stranger your tastes seem to other people, the stronger evidence they probably are of what you should do. So I bet it would help a lot of people to ask themselves about this explicitly. What seems like work to other people that doesn't seem like work to you? workinterestlife
The Top Idea in Your Mind An Essay by Paul Graham paulgraham.com I think most people have one top idea in their mind at any given time. That's the idea their thoughts will drift toward when they're allowed to drift freely. And this idea will thus tend to get all the benefit of that type of thinking, while others are starved of it. Which means it's a disaster to let the wrong idea become the top one in your mind. ideas
Cities and Ambition An Essay by Paul Graham paulgraham.com Boston says you should be smarterFlorence and MilanA city speaks to you mostly by accidentCity messages citiesambition
Taste for Makers An Essay by Paul Graham paulgraham.com If there is such a thing as beauty, we need to be able to recognize it. We need good taste to make good things. Instead of treating beauty as an airy abstraction, to be either blathered about or avoided depending on how one feels about airy abstractions, let's try considering it as a practical question: how do you make good stuff? You feel this when you start to design thingsGood design is simpleGood design is timelessGood design is often slightly funnyGood design is hard, but looks easy+3 More Beauty in flight beautytastedesign
Good and bad procrastination An Essay by Paul Graham paulgraham.com The absent-minded professorYou can't look a big problem too directly in the eye
The still life effect A Fragment by Paul Graham paulgraham.com If you're going to spend years working on something, you'd think it might be wise to spend at least a couple days considering different ideas, instead of going with the first that comes into your head. You'd think. But people don't. In fact, this is a constant problem when you're painting still lifes. You plonk down a bunch of stuff on a table, and maybe spend five or ten minutes rearranging it to look interesting. But you're so impatient to get started painting that ten minutes of rearranging feels very long. So you start painting. Three days later, having spent twenty hours staring at it, you're kicking yourself for having set up such an awkward and boring composition, but by then it's too late. ideasart
How to do what you love An Essay by Paul Graham paulgraham.com To do something well you have to like itWow, that's pretty coolPrestige is just fossilized inspirationAlways produce worklife
Hackers and Painters An Essay by Paul Graham www.paulgraham.com A great painting has to be better than it has to be
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