Austin Kleon
Write the books you want to read
The art of finding what you didn’t know you were looking for
An Article by Austin KleonIn the terrific documentary about his work, The Secret Life of Lance Letscher, the collage artist points out that he doesn’t want his file boxes of source material organized too much, that he specifically avoids organizing them, so that he can find unexpected things when he starts searching. “He depends upon that chaos of stuff, of things lying around.”
/
There are several paragraphs in Murch’s book about the importance of fighting against the touted “features” of digital tools, such as speed. “The real issue with speed,” he says, “Is not just how fast can you go, but where are you going so fast? It doesn’t help to arrive quickly if you wind up in the wrong place.”
/
If I was simply able to execute a full-text search on my notebooks, and pull up exactly what I was looking for, that’s all I’d find: exactly what I was looking for. And the real art is in finding what I didn’t know I was looking for.
The tools matter and the tools don't matter - Austin Kleon
An Article by Austin KleonThough you might not think it from the comic, I’m actually sympathetic to questions about tools and process, as I myself am a kind of process junky. I love hearing about how other writers work.
I’m also not someone who dismisses questions about tools with the line “the tools don’t matter.” In fact, I think tools matter so much that if you don’t talk about them correctly you can do some damage.
...What I love about John Gardner and Lynda Barry is that they believe that the tools you use do matter, but the point, for them, is finding the proper tools that get you to a certain way of working in which you can get your conscious, mechanical mind out of the way so that your dreaming can go on, undeterred.
You have to find the right tools to help your voice sing.
Input as collage
An Article by Austin KleonYour output depends on your input, but a lot of your input is random: you’re interested in lots of different things, and those things, occasionally, will talk to each other in your work.
Lately I’ve been thinking about being more intentional with input. Thinking about input as collage. Taking the principle of juxtaposition (1+1=3) and using that to guide your input: what weird, seemingly disparate things can you feed your brain that will come out later in a new mix?
The input collage can be subject or genre based and even better if it’s multi-media.
...There’s a balance here between feeding your brain intentionally and then backing off and letting your brain do the subconscious work of mixing your inputs together.
If a book can be summarized, is it worth reading?
An Article by Austin KleonIt is my opinion that if a book’s contents can be adequately “summed up,” so that you really don’t miss anything by reading the summary, it is not actually a book worth reading. (Of course, there’s no way to tell whether a summary is adequate or not unless you have also read the book.) Also, I suspect that the harder you find it to summarize a book you have read, the more valuable it might be.
Ignorant, but curious
An Article by Austin KleonThe method is perhaps best summarized by Mike Monteiro: “The secret to being good at anything is to approach it like a curious idiot, rather than a know-it-all genius.”
The “curious idiot” approach can serve you well if you can quiet your ego long enough to perform it.
A curious idiot is unafraid to ask stupid questions. Every stupid question you ask takes a teeny, tiny act of courage. Sometimes you have to muster the will to push the words out of your lips.
The most important thing you do
An Article by Austin KleonFor the writer, your career will be the result of whatever piece you’re working on right now, and the piece you’re working on right now will be the result of whatever sentence you’re working on right now.
Finding nourishment vs. identifying poison
An Article by Austin Kleon & Olivia LaingA useful analogy for what [Sedgwick] calls ‘reparative reading’ is to be fundamentally more invested in finding nourishment than identifying poison. This doesn’t mean being naive or undeceived, unaware of crisis or undamaged by oppression. What it does mean is being driven to find or invent something new and sustaining out of inimical environments.
I would like to adopt that line as a mission statement: “To be fundamentally more invested in finding nourishment rather than identify poison.”
Because you can identify all the poison you want, but if you don’t find nourishment, you’ll starve to death.
Poison sniffers
An Article by Austin KleonChristopher Johnson says “prescriptivists” or “Cute Curmudgeons” — people who are interested in only policing usage and grammar rules — are “linguistic poison sniffers.” They turn language into “a source of potential embarrassment rather than pleasure.”
Johnson sees his job as getting people to love and appreciate language by being curious about and paying attention to “what makes language delicious.”
This reminded of Olivia Laing’s distinction between identifying poison and finding nourishment.
Everywhere you look these days, there are lots of poison sniffers, but very few cooking a delicious meal…
Almanacs and cyclical time
An Article by Austin KleonI am fascinated by the Farmer’s Almanac, and the “Planting by the Moon” guide in particular, which has advice such as: “Root crops that can be planted now will yield well.” “Good days for killing weeds.” “Good days for transplanting.” “Barren days. Do no planting.”
I think it’d be funny to make up an almanac for writers and artists, one that emphasized the never-ending, repetitive work of the craft.
Don't get me wrong
An Article by Austin KleonNo phrase makes me want to stop reading more. “Don’t get me wrong” is usually a tell — a kind of backpedaling that sets off an internal alarm and suggests I’m a) reading a hyperbolic argument (which, admittedly, describes the majority of online writing these days) or b) that the writer is just lazy. Either way, when I see “don’t get me wrong,” I start to suspect I’m reading a piece of writing that might not be worth my time.
If you find yourself using “don’t get me wrong,” I have a suggestion: Delete the phrase and rewrite what came before it so I don’t get you wrong.
Pointing at things
An Article by Austin KleonThe story goes that the painter Al Held said, “Conceptual art is just pointing at things,” so John Baldessari decided to take him literally, and commissioned a bunch of amateur painters to paint realistic paintings of hands pointing at things.
As I wrote in Steal Like An Artist,
“Step 1: Wonder at something.
Step 2: Invite others to wonder with you.”Point at things, say, “whoa,” and elaborate.
Beyond Artboards
The Pursuit of Lossless Design-Development Handoffs.
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.
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.
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.