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 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.