Redefining colour systems across design and code is easily the most complicated work I’ve done all year.
Notion is great because it does everything I need it to with just enough friction that I don’t actually want to do any of it.
Watching TV this week, someone on screen described themselves as a “nerd” for watching anime. My fiancée dismissed that claim, instead turning on me and insisting I am a “real” nerd because I like coding and have a mechanical keyboard…
An em dash is just three hyphens in a trenchcoat.
Backlog prioritisation is just managing the rate at which you burn social capital.
Absolute silence in libraries so a bunch of strangers can look for books? Unquestionable.
Keep it down in an open plan office so your coworkers can help keep your employer in business? Unheard of.
Carousels are the Lazy Susans of the web.
What if calendar meetings weren’t required to have durations or end times? If the only expectations people had were start times and agendas, would meetings be shorter or longer?
“View less” collapse buttons are my biggest UI pet peeve, especially when the user has just expanded the thing. If they don’t want to see it anymore, they’ll just scroll or navigate away. Nobody is cleaning up after themselves.
Sometimes I find myself using “accessibility” as an explanation for why something is important to do. I feel like “usability” would carry more weight.
“Make sure to include these attributes so it’s usable,” with an implicit “for everyone.”
Normalise replying to “LGTM” PR approvals with “damn right it does”
The Nine States of Design that “apply to all designs and all components”: Nothing, loading, none, one, some, too many, incorrect, correct, and done.
What’s more is this applies both within and adjacent to your team. Any bad apple within 1–2 degrees of collaboration can spoil the bunch. Gotta have an interest in maintaining high standards across the org.
I feel like many managers underestimate the impact of a bad hire. Not only do you get a jerk or under-performer or whatever, but they also eventually push away all of your lovely high-performers.
Two week sprints invite bad estimates, drifting team alignment and focus, and high work-in-progress. Just be careful of burdening yourself with too many meetings during one-week sprints. Experiment with (for example) weekly planning, async standups, fortnightly retrospectives.
Hot take? Two-week sprints are too long.
You can do anything in two weeks. It feels like forever. One week is better. You can see the free time on your calendar and plan more accurately.
A couple of thoughts:
Depth over breadth. Shipping quick features is fun but some satisfying problems take years to solve.
I’ve seen enough shit to know what I absolutely won’t put up with again, and switching companies always poses that risk.
Everyone I know who has hired product designers recently has despaired at the applicant pool. You either get marketing designers with no product experience or UX designers with no visual design skills. This helps explain why.
One cool thing about tennis is that crowds will support anyone who is playing well. Britain’s favourite Andy Murray got whomped at Wimbledon last week and the player who beat him was being cheered on the whole way, capped by a standing ovation.
“The decision to make a mess is never rational, is always based on laziness and unprofessionalism, and has no chance of paying of in the future. A mess is always a loss.”
“A mess is not a technical debt. A mess is just a mess. Technical debt decisions are made based on real project constraints. They are risky, but they can be beneficial.”