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 Fidelity Curve An Article by Ryan Singer m.signalvnoise.com How do we choose which level of fidelity is appropriate for a project? I think about it like this: The purpose of making sketches and mockups before coding is to gain confidence in what we plan to do. I’m trying to remove risk from the decision to build something by somehow “previewing” it in a cheaper form. There’s a trade-off here. The higher the fidelity of the mockup, the more confidence it gives me. But the longer it takes to create that mockup, the more time I’ve wasted on an intermediate step before building the real thing. I like to look at that trade-off economically. Each method reduces risk by letting me preview the outcome at lower fidelity, at the cost of time spent on it. The cost/benefit of each type of mockup is going to vary depending on the fidelity of the simulation and the work involved in building the real thing. Four levels of fidelityTime to build versus confidence gained prototypesinterfaces
Four levels of fidelity Suppose we have four levels of fidelity… Rough sketch (on paper or an iPad) Static mock-up (eg. Photoshop or Sketch) Interactive mock-up (eg. Framer, InVision) Working code prototype (HTML/CSS, iOS views) Depending on the feature you’re working on, these levels of fidelity take different amounts of time to create. If you plot them in terms of time to build versus confidence gained, you could imagine something like a per-feature fidelity curve.
Time to build versus confidence gained Show image 0 Show image 1 Show image 2 Take a simple CRUD web UI, where you’re just navigating between screens. It doesn’t take much more time to build the real version than it does to mock it when the design is simple. If you were to build out an interactive mock first, you would end up spending twice as much time in total without gaining much out of it. Contrast that with a complicated Javascript interaction. Or a native iOS feature that requires programmer time to build out. If it takes substantially more time to build the real code version, then it may be smart to do an interactive mockup first.