Une liste d’articles qui ne prennent pas trop de rides. J’aime beaucoup ce qu’a fait Anselm Hannemann alors voici un espace que je vais mettre à jour au gré de mes lectures. Ça me permettra aussi de lier des références mises en cache dans le futur. L’ordre n’est pas significatif.
Bonne lecture !
User experience design has led us to use a certain vocabulary: Instead of seeing human beings with goals and attitudes, we see users. We use words like subscribers, subs, visitors, spenders, whales or even just “traffic” or “installs” to refer to them. We assign a role to them. UX design dehumanizes people.
Humans, not Users (cache)
In UX, empathy enables us to understand not only our users’ immediate frustrations, but also their hopes, fears, abilities, limitations, reasoning, and goals. It allows us to dig deep into our understanding of the user and create solutions that will not only solve a need, but effectively improve our users’ lives by removing unnecessary pain or friction. Instead of just designing an accessible website, practicing empathy is using a screen reader, blindfolded, in order to complete a task on your own website.
Sympathy vs. Empathy in UX (cache)
You want your customers to be talking to you. You want them sharing ideas and experiences with you. Instead of a no-reply, set it to your support email address. Make sure someone will see any replies that a customer sends. Sure, you’re going to get lots of auto-responders. That’s why your email app has filter and rules you can set up.
No Reply Addresses (cache)
In everyday language, the word “ethics” is used as a synonym for morals. And in everyday discussions that is just fine. Morals sounds old fashioned, conservative, unscientific. We say “ethics” even though, strictly speaking, we mean morals. When it comes to discussing the “ethics” or the morality of our industry, we need to understand our basic moral beliefs.
“Ethics” and Ethics (cache)
This is, by the way, the dirty secret of the machine learning movement: almost everything produced by ML could have been produced, more cheaply, using a very dumb heuristic you coded up by hand, because mostly the ML is trained by feeding it examples of what humans did while following a very dumb heuristic. There’s no magic here.
Forget privacy: you’re terrible at targeting anyway (cache)
Les personnes chargées de créer des formulaires, des bases de données ou des ontologies ignorent souvent la façon dont les noms changent d’un pays à l’autre. Elles conçoivent leurs formulaires et leurs bases de données sans se rendre compte de l’effort demandé pour un utilisateur étranger. Cet article vous présentera d’abord les différents styles utilisés pour un nom de personne, puis détaillera quelques incidences possibles pour les gérer au mieux sur le Web.
Noms de personnes à travers le monde (cache)
Voir aussi (cache).
Communities prior to the advent of coinage didn’t seek to settle their trades on the spot, at least not within those communities. They relied on much more egalitarian long-running concepts of reciprocity. Forms much closer to the communist slogans of “from each according to his ability, to each according to his needs” than the quid pro quo paradigm we all take for granted in today’s market-based societies.
Open source beyond the market (cache)
Search is a deceptively complex field, where competence is hard-won through training, practice, and experience. The list stands at a total of 105 falsehoods. I couldn’t mash up the ole 99-problems meme with this to cull 6 unworthy items, because they are all worthy.
Falsehoods Programmers Believe About Search (cache)
There really is very little reason to leave your static assets on anyone else’s infrastructure. The perceived benefits are often a myth, and even if they weren’t, the trade-offs simply aren’t worth it. Loading assets from multiple origins is demonstrably slower. Take ten minutes over the next few days to audit your projects, and fetch any off-site static assets under your own control.
Self-Host Your Static Assets (cache)
The Projector Test is my favorite “gut check” manual UI test, and I encourage you to use it early, often, and especially when ironing out final visual specs. It doesn’t substitute for testing out a functional version of your site in a variety of environments — browsers, form factors, screen resolutions, operating systems, screen orientations, screen readers, etc. — but it’s a good place to start. Embrace your conference room’s projector and challenge yourself to make your designs look stellar on even the fuzziest, most washed-out of screens.
Projectors don’t lie. (cache)
You know what’s better than perceived performance? Actual performance. Avoid techniques that merely provide a mirage of speed.
Instead, declutter and optimise the foundations of your design system which will result in less weight, less complexity, less distraction, less hassle and ultimately, less bull shit.
Designing for actual performance (cache)
Ultimately, in email, less is more.
This can be a tough pill for marketers to swallow (myself included) because we’re naturally driven to be creative. But data repeatedly shows plain-text email wins, so it’s up to us to decide whether or not we want to make the switch.
Plain Text vs. HTML Emails: Which Is Better? (cache)
You want to avoid branching for this work if at all possible, based on previous painful experiences of merging long-lived branches in the past. Instead, you decide that the entire team will continue to work on trunk, but the developers working on the Spline Reticulation improvements will use a Feature Toggle to prevent their work from impacting the rest of the team or destabilizing the codebase.
Feature Toggles (aka Feature Flags) (cache)
Always measure and store time in UTC. If you need to record where the time was taken, store that separately. Do not store the local time + timezone information!
“Eppur si muove!” – Dealing with Timezones in Python (cache)
This script doesn’t actually do any of the steps of the procedure. That’s why it’s called a do-nothing script. It feeds the user a step at a time and waits for them to complete each step manually.
At first glance, it might not be obvious that this script provides value. Maybe it looks like all we’ve done is make the instructions harder to read. But the value of a do-nothing script is immense
Do-nothing scripting: the key to gradual automation (cache)
When I started as a professional UX designer, I was shocked how many times my clients would hand me the initial wireframes (or the living, breathing, in-browser MVP) and there’d be completely obvious UX mistakes all over them. I’m not talking about things you need hours of research and A/B testing to discover. I’m talking, like, dead simple mistakes.
4 Rules for Intuitive UX (cache)
So, if I was designing a new form, I’d want to know how to avoid the common issues. And to use my time to solve newer and perhaps more difficult problems.
Seriously, who wants to spend time solving something that’s already been solved?
Form design: from zero to hero all in one blog post (cache)
Vous voulez que votre mot de passe résiste à un voisin malveillant prêt à mettre plus de 10 € sur la table ? Prévoyez au moins 10 caractères.
Et là, seconde magie : Si vous mettez 10 caractères on se moque de savoir si vous y avez mis des chiffres ou symboles. La longueur a bien plus d’importance que l’éventail de caractères utilisé.
Développeurs, vous devriez avoir honte (cache)
Say you’re trying to test whether people like pizza. If you serve them burnt pizza, you’re not getting feedback on whether they like pizza. You only know that they don’t like burnt pizza. Similarly, when you’re only relying on the MVP, the fastest and cheapest functional prototype, you risk not actually testing your product, but rather a poor or flawed version of it.
Don’t Serve Burnt Pizza (And Other Lessons in Building Minimum Lovable Products) (cache)
Est-ce qu’il y aurait des publications de cet espace que vous mettriez dans une telle liste ? Je fais ma propre liste en pied de page et je serais curieux de savoir si elle diffère de la vôtre :-).