Jots is a collection of bits from inspiring pieces.

These days every Google product seems to assume that your internet connection is always on, that you’re close enough to the nearest Google server that your brain won’t notice the speed-of-light delay, and that you have practically unlimited bandwidth. These assumptions are barely true in Mountain View, let alone in most of the rest of the world.

Jot 115 : Jamey Sharp in How Not to Replace Email, from non-O(n) musings.
Jotted on the 19th of Feb 2018, at 11:15.

It’s a shame to see a ton of hard work go into static designs only to see all that thinking, detail, and nuance get washed away when it’s translated into code.

Jot 114 : Brad Frost in Your Sketch Library Is Not a Design System Redux, from Brad Frost’s Blog.
Jotted on the 18th of Feb 2018, at 17:40.

Once upon a time I opened a new tab in Firefox on my Android phone to find out that besides a list of my most visited pages to choose from, there also was a list of things “suggested by Pocket”. What the hell was Pocket, why was it suggesting me things and, more importantly, how the hell did it get into my Firefox?

Jotted on the 16th of Feb 2018, at 22:20.

What would you do, or how should the project be run to ensure that kind of failure?

Jot 112 : Taylor Smith in Premortem: Prevent Failures by Recognizing Patterns, from Taylor Smith’s Site.
Jotted on the 15th of Feb 2018, at 11:05.

To my fellow maintainers: stay harsh on code and don’t be afraid to say “No” or “Why?”; there really are more bad ideas than good ones […].

Jot 111 : Rusty Russell in MAINTAINERS: Remove rom Module & Paravirt Maintenance, from Kernel.org git Repositories.
Jotted on the 15th of Feb 2018, at 11:00.

[…] significant progress in the solutions of technical problems is frequently made not by a direct approach, but by first setting a goal of high challenge which offers a strong motivation for innovative work, which fires the imagination and spurs men to expend their best efforts, and which acts as a catalyst by including chains of other reactions.

Jot 110 : Dr. Ernst Stuhlinger in Why Explore Space?, from Letters of Note.
Jotted on the 13th of Feb 2018, at 23:15.

Rather than beginning a fruitless search for such divine proportions to serve a gross simplification of the world, we will instead focus on a more concrete history of how technology long has inspired designers to use geometric constraints to ease the burden of their work.

Jot 109 : Rune Madsen in A short history of geometric composition, from Programming Design Systems.
Jotted on the 13th of Feb 2018, at 10:55.

The more choices technology gives us in nearly every domain of our lives (information, events, places to go, friends, dating, jobs) — the more we assume that our phone is always the most empowering and useful menu to pick from. Is it?

Jotted on the 12th of Feb 2018, at 11:15.

The precision is introduced by the engineer, where it rightfully belongs. After all, our designs are completely useless until they are built—what exists in the users’ hands is the final design, and nothing less.

Jot 107 : Daniel Eden in The Burden of Precision, from Daniel Eden’s Site.
Jotted on the 29th of Jan 2018, at 11:05.

Herein lies the problem: our current tools encourage me to design the finished product first. They beg me to mess with rounded corners, colors, typefaces and stroke styles. But it’s only when I’m working within a strict design system that I ever need to declare those things.

Jot 106 : Robin Rendle in Tools for Thinking and Tools for Systems, from CSS-Tricks.
Jotted on the 29th of Jan 2018, at 11:00.

As a Designer becomes more Senior, they also become more realistic and business-minded, or so the idea goes. These “Senior Designers” understand that a company is a company, and that the money paying your salary has to come from somewhere.

Jot 105 : Joel Califa in Subverted Design , from Joel Califa’s Site.
Jotted on the 17th of Jan 2018, at 11:00.

[…] Google’s not going to be selling many ads next to search results that turn them up. So from a business point of view, it’s hard to make a case for Google indexing everything, no matter how old and how obscure.

Jot 104 : Tim Bray in Google Memory Loss, from Tim Bray’s Site.
Jotted on the 16th of Jan 2018, at 15:00.

It’s also worth recognizing how these decisions aren’t, in almost any case, unalloyed pushes for “the future of the web.” They reflect business priorities, just like any other technical prioritization.

Jot 103 : Chris Krycho in Chrome is Not the Standard, from Chris Krycho’s Site.
Jotted on the 12th of Jan 2018, at 11:00.

Machines are not intelligent, but they already excel at simulating intelligence. They are really good at making us believe that they understand, that they know us, that they comprehend, that they play chess.

Jot 102 : iA in Who Serves Whom?, from iA’s Site.
Jotted on the 5th of Jan 2018, at 11:15.

This is bonkers, isn’t it? Google is creating data out of data.

Jot 101 : Justin O’Beirne in Google Maps’s Moat, from Justin O’Beirne’s Site.
Jotted on the 20th of Dec 2017, at 11:15.

For me and for Tony, this clip is extremely reassuring. If Miyazaki — the world’s greatest living animator — can admit defeat after trying his best, then it’s okay for everyone else. If he can let go, then so can we.

Jot 100 : Taylor Ramos, Tony Zhou in Postmortem: Every Frame a Painting, from Medium.
Jotted on the 19th of Dec 2017, at 10:50.

If you know you have a meeting in an hour, do you start your deepest, most complex problem solving work? I’d venture to guess most people don’t. I certainly don’t.

Jot 99 : Dan Kim in It’s time for recurring meetings to end, from Signal v. Noise.
Jotted on the 16th of Dec 2017, at 15:15.

Notice how these colors do not seem ‘natural’ per se, but are chosen to convey the taste of the product.

Jot 98 : Rune Madsen in Color schemes, from Programming Design Systems.
Jotted on the 30th of Nov 2017, at 19:10.

[…] Debt is acquired by building for the short-term. Design debt is made up of an overabundance of non-reusable and inconsistent styles and conventions, and the interest is the impossible task of maintaining them.

Jot 97 : Marco Suarez in Introducing design systems, from DesignBetter.Co.
Jotted on the 30th of Nov 2017, at 11:00.

I wish I had more comforting words for you, but all I can say is that most things worth doing are a struggle.

Jotted on the 9th of Nov 2017, at 10:35.

Fail fast. Iterate quickly. Prototype. Prototype. Prototype. And cut. Cut scope until it hurts.

Jotted on the 1st of Nov 2017, at 11:15.

Failure is a good thing if you plan for it. Failure can teach you lessons that no success will ever teach you […]

Jot 94 : Sarah Woodrow in 7 Truths About Indie Game Development, from Gamasutra.
Jotted on the 31st of Oct 2017, at 11:45.

If you’re describing what a function does and you have to use the word “and,” that function is probably too complex. What a function does should be simple enough to explain with only a descriptive function name and descriptive arguments.

Jot 93 : Brandon Gregory in Coding with Clarity, from A List Apart.
Jotted on the 27th of Oct 2017, at 12:20.

Tell everyone you’re working on this project to make sure that there isn’t anything you overlooked.

Jot 92 : Robin Rendle in 5 Tips for Starting a Front-End Refactor, from CSS-Tricks.
Jotted on the 20th of Oct 2017, at 12:40.

Values aren’t what’s printed on the wall or in the employee handbook, but the interactions that happen every day. The values stem from the top, are reinforced by each employee, and determine how the company works.

Jot 91 : Julie Zhuo in Signs It’s Time to Move On, from The Looking Glass.
Jotted on the 17th of Oct 2017, at 12:40.

Solutions based on this knowledge can help you to give users what they need, rather than what they say they want.

Jot 90 : Ruth Stalker-Firth in Inside Your Users’ Minds: The Cultural Probe, from A List Apart.
Jotted on the 10th of Oct 2017, at 17:05.

[…] software patents are actually preventing the adoption of new technology, rather than encouraging it.

Jot 89 : Simson L. Garfinkel, Mitchell Kapor, Richard M. Stallman in Why Patents Are Bad for Software, from Issues in Science and Technology, Fall 1991.
Jotted on the 9th of Oct 2017, at 12:10.

Your job is not to stop your mentee from making any mistakes; it’s to stop them from making the same mistakes over and over.

Jot 88 : Brandon Gregory in Be a Mentor, from A List Apart.
Jotted on the 8th of Oct 2017, at 22:35.

[…] it’s confusing because I don’t think pictorially, I’ve done it grammatically […]

Jot 87 : Christopher Nolan in 18-Minute Analysis By Christopher Nolan On Story & Construction Of Memento, from YouTube, The Lord Louis Show.
Jotted on the 5th of Oct 2017, at 22:25.

A difficult client who demonstrates trust issues right from the beginning of the business relationship and shows an inability to compromise might be more trouble than they are worth.

Jotted on the 5th of Oct 2017, at 13:00.

Yes, I have regrets, but as soon as you start rewriting your past you realize how your failures and mistakes are what define you.

Jot 85 : Cory Taylor in Questions for Me About Dying, from The New Yorker.
Jotted on the 29th of Sep 2017, at 00:30.

After reading that, do you still want to include open source work in your project? Will it derail your purpose and goal?

Jot 84 : Phillip Ikuvbogie in Considering Open Source Licenses, from A List Apart.
Jotted on the 27th of Sep 2017, at 11:50.

What has changed in the last generation is that companies today view more and more of the labor it takes to produce their goods and services as akin to staplers: something to be procured at the time and place needed for the lowest price possible.

Jotted on the 21st of Sep 2017, at 12:10.

When an organization tries to maximize inputs, rather than outputs, the result is a whole series of bad judgments.

Jot 82 : Itamar Turner-Trauring in Join Our Startup, We’ll Cut Your Pay by 40%!, from Code Without Rules.
Jotted on the 19th of Sep 2017, at 12:10.

Exhaustion isn’t cured over a weekend (or even a long weekend). It requires a recalibration of priorities, tasks, life goals and even life purpose.

Jot 81 : Patrick Johnson in What Is Burnout?, from Patrick Johnson’s Site.
Jotted on the 13th of Sep 2017, at 00:55.

[…] it is important to distinguish between ‘state’ and ‘act.’ The state of something in UX is fundamentally static, like a design comp. The act of something in UX is fundamentally temporal, and motion based.

Jot 80 : Issara Willenskomer in Creating Usability with Motion: The UX in Motion Manifesto, from “Medium”.
Jotted on the 12th of Sep 2017, at 11:45.

[…] there are three levels of consistency: individual, collective, and institutional.

Jot 79 : Jens Oliver Meiert in How to Write Better Code: The 3 Levels of Code Consistency, from “CSS-Tricks”.
Jotted on the 8th of Sep 2017, at 12:15.

If a project calls for SVG and a designer has been tasked with creating illustrations and providing design assets for development, then the designer is no longer handing over a static file, but a snippet of code […].

Jot 78 : Geoff Graham in When Design Becomes Part of the Code Workflow, from “CSS-Tricks”.
Jotted on the 8th of Sep 2017, at 12:10.

Being a senior developer doesn’t mean you have to know everything, it means you can help find out anything.

Jot 77 : Chris Coyier in So You Want To Be a Senior Developer?, from “CSS-Tricks”.
Jotted on the 8th of Sep 2017, at 12:00.

Effective retrospectives require a commitment to maintain an open mind and open communication with your team, as well as a willingness to be vulnerable.

Jotted on the 6th of Sep 2017, at 12:00.

[…] we primarily use animation in three ways—to indicate a state change, to add an emphasis, or to reveal extra information

Jot 75 : Alla Kholmatova in Integrating Animation into a Design System, from “A List Apart”.
Jotted on the 22nd of Aug 2017, at 11:45.

A common pitfall is to define your goals in terms of your existing metrics—“well, our goal is to increase traffic to our site.” Yes, everyone wants to do that, but how will user-experience improvements help?

Jot 74 : Kerry Rodden in How to Choose the Right UX Metrics for Your Product, from “GV Library”.
Jotted on the 1st of Aug 2017, at 12:30.

Trust keeps a relationship going, but you need the knowledge of possible future repeat interactions before trust can evolve.

Jot 73 : Nick Case in The Evolution of Trust, from “The Evolution of Trust”.
Jotted on the 1st of Aug 2017, at 12:00.

When you’ve been set up to fail, your primary goal is to demonstrate that the inevitable failure was not your fault.

Jot 72 : Itamar Turner-Trauring in The Bad Reasons You’re Forced to Work Long Hours, from “Code Without Rules”.
Jotted on the 9th of Jul 2017, at 20:25.

Focusing on coding inflates the importance of finding the “right” method to solve a problem rather than the importance of understanding the problem.

Jot 71 : Basel Farag in Please Don’t Learn to Code, from “TechCrunch”.
Jotted on the 3rd of Jul 2017, at 18:10.

What advice does anyone have for me?

Jot 70 : Claire Lew in Unlock Honest Feedback with This One Word, from “Signal v. Noise”.
Jotted on the 16th of Jun 2017, at 12:30.

I tend to finish a presentation with some questions of my own. I ask whether they feel the project will achieve its desired goals, meet the needs of users and fulfil organisational objectives.

Jot 69 : Paul Boag in Convincing Clients: How To Get Sign Off When It Matters, from “Smashing Magazine”.
Jotted on the 14th of Jun 2017, at 11:50.

Audrey, you’re missing a really important step. I think you need to just listen to them.

Jotted on the 7th of Jun 2017, at 17:20.