Systems, Mistakes, and the Sea An Article by Robin Rendle www.robinrendle.com Every paper cut is felt The design systems between us
Thanks Doc An Article by Robin Rendle & Craig Mod www.robinrendle.com A couple of months back, Craig mentioned in a video that he has a doc filled to the brim with snippets of text—nice words, compliments, and thanks that had been sent his way for his work. Whenever someone says something nice he just copy/pastes it into that doc. It sounds silly at first and perhaps a little egotistical. Behold! I have a document that proves how great I am! But I started doing it just to see what it feels like and…hey…actually? It’s so great! When I’m feeling low (often) or whenever the world feels unstable (extremely often) it’s so very nice to return to a few kind words about my work. It reminds me just how much these words of praise mean, it reminds me that I ought to pass that favor along. Good Things happinessworkfriendship
An incoherent rant about design systems An Article by Robin Rendle www.robinrendle.com No matter how fancy your Figma file is or how beautiful and lovingly well organized that Storybook documentation is; the front-end is always your source of truth. You can hate it as much as you like—all those weird buttons, variables, inaccessible form inputs—but that right there is your design system. ...being honest about this is the first step to fixing it. uxcode
Care for the Text An Article by Robin Rendle css-tricks.com Whenever I’m stuck pondering the question: "How do I make this website better?" I know the answer is always this: Care for the text. Without great writing, a website is harder to read, extremely difficult to navigate, and impossible to remember. Without great writing, it’s hardly a website at all. But it’s tough to remember this day in and day out—especially when it’s not our job to care about the text—yet each and every <p> tag and <button> element is an opportunity for great writing. It’s a moment to inject some humor or add a considerate note that helps people. …These are the details that make a good website great. detailstypographycontent
Re: Pointing at things An Article by Robin Rendle www.robinrendle.com I think I’ve been darting around this question for a while now: ...I think we’ve all been taught to write in a style that forgets the reader entirely. My English degree taught me, incentivized me in fact, to write poorly with this sort of obfuscatory language, “nevertheless...”, “in this essay I will set out to...” etc. All that stuff is me pointing at me, pointing at a thing. But we should just get out of the way of the thing we’re pointing at! Pointing at things writing
Planning doesn't make for better software A Fragment by Robin Rendle www.robinrendle.com My own time in a Silicon Valley startup has proved this much to be true; planning doesn’t make for better software. In fact today our design systems team doesn’t have sprints, we don’t have tickets or a daily standup. Each day we come to work, figure out what’s the most important thing that we could be doing, and then we—gasp!—actually do it. Watching so many other teams slowly flail about whilst they plan for quarter 3.2 of subplan A, whilst our team produces more work in a week than they all do combined in a quarter has been shocking to me. After four years of working in a large startup, I know what I always assumed was true: you don’t need a plan to make a beautiful thing. You really don’t. In fact, there’s a point where overplanning can be a signal of inexperience and fear and bullshit. The scrum board and the sprints and the inane meetings each and every day are not how you build another Super Mario 64. Instead all you have to do is hire smart people, trust them to do their best work, and then get the hell out of their way. Why Software is Slow and Shitty planningsoftwareagile
Who the fuck is Guy Debord? An Article by Robin Rendle www.robinrendle.com Long, unwieldy sentencesImagining her PsychogeographySuch tortuous syntax writingsimplicity
Every Website is an Essay An Article by Robin Rendle css-tricks.com "Every website that’s made me oooo and aaahhh lately has been of a special kind; they’re written and designed like essays. There’s an argument, a playfulness in the way that they’re not so much selling me something as they are trying to convince me of the thing. They use words and type and color in a way that makes me sit up and listen. And I think that framing our work in this way lets us web designers explore exciting new possibilities. Instead of throwing a big carousel on the page and being done with it, thinking about making a website like an essay encourages us to focus on the tough questions. We need an introduction, we need to provide evidence for our statements, we need a conclusion, etc. This way we don’t have to get so caught up in the same old patterns that we’ve tried again and again in our work. And by treating web design like an essay, we can be weird with the design. We can establish a distinct voice and make it sound like an honest-to-goodness human being wrote it, too." writingwwwessays
Re: How would I improve RSS? An Article by Robin Rendle www.robinrendle.com I still believe in a Kindle/Analogue-esque device that, within it, contains an operating system that is half Patreon, half Substack, half Instapaper. I think of this as the Republic of Newsletters writ large—The OmniBlog—where writers can publish their work and folks can subscribe via RSS but with a Coil-esque payment system built in and preloaded onto a physical e-reader. Writers could blog away, connected to eachother, whilst readers could subscribe to their work and perhaps even fund larger pieces of writing... Shit, I just described Medium huh. How would I improve RSS? rssblogging
The Sense of Style A Book by Steven Pinker Classic styleThe assumption of equalityNominalizationThe curse of knowledgeStructural parallelism+2 More The Elements of Style writingcommunication
Classic style The guiding metaphor of classic style is seeing the world. The writer can see something that the reader has not yet noticed, and he orients the reader’s gaze so that she can see it for herself. The purpose of writing is presentation, and its motive is disinterested truth. It succeeds when it aligns language with the truth, the proof of success being clarity and simplicity. The truth can be known, and is not the same as the language that reveals it; prose is a window onto the world. truth
The assumption of equality Classic writing, with its assumption of equality between writer and reader, makes the reader feel like a genius. Bad writing makes the reader feel like a dunce. Long, unwieldy sentences respect
Nominalization The English language provides bad writers with a dangerous weapon called nominalization: making something into a noun. Instead of affirming an idea, you effect its affirmation; rather than postponing something, you implement a postponement. "Comprehension checks were used as exclusion criteria” would be better said as “we excluded people who failed to understand the instructions.” “There is not any anticipation there will be a cancellation” would be better as “I don’t anticipate that I will have to cancel.” Zombie sounds, unlike the verbs whose bodies they snatched, can shamble around without subjects. That is what they have in common with the passive constructions that also bog down these examples. language
The curse of knowledge The better you know something, the less you remember about how hard it was to learn. The curse of knowledge is the single best explanation I know of why good people write bad prose. It simply doesn’t occur to the writer that her readers don’t know what she knows - that they haven’t mastered the patois of her guild, can’t divine the missing steps that seem too obvious to mention, have no way to visualize a scene that to her is as clear as day. And so she doesn’t bother to explain the jargon, or spell out the logic, or supply the necessary detail. Such tortuous syntax knowledgeteachingux
Structural parallelism If the new phrase has the same structure as the preceding one, its words can be slotted into the waiting tree, and the reader will absorb it effortlessly. The pattern is called structural parallelism, and it is one of the oldest tricks in the book for elegant (and often stirring) prose. “He maketh me to lie down in green pastures; he leadeth me beside the still waters.” The principle of parallel construction
You live only once The logician would argue, You only live once should be rewritten as You live only once, with only next to the thing it qualifies, once. The logician would be unbearably pedantic, but there is a grain of good taste in the pedantry. Writing is often clearer and more elegant when a writer pushes an only or a not next to the thing that it quantifies. In 1962 John F. Kennedy declared, “We choose to go to the moon not because it is easy but because it is hard.” That sounds a lot classier than “We don’t choose to go to the moon because it is easy but because it is hard." grammar
Such tortuous syntax How does a writer manage to turn out such tortuous syntax? It happens when he shovels phrase after phrase onto the page in the order which each one occurs to him. The problem is that the order in which thoughts occur to the writer is different from the order in which they are easily discovered by a reader. It’s a syntactic version of the curse of knowledge. The writer can see the links among the concepts in his internal web of knowledge, and has forgotten that a reader needs to build an orderly tree to decipher them from his string of words. Who the fuck is Guy Debord?The curse of knowledgeChoose a suitable design and hold to it