INTRODUCTION
WALTER PLECKER WAS AN ASSHOLE.

In the 1920s, he was registrar of Virginia’s Bureau of Vital Sta-
tistics, the state government office that controlled birth, death,
marriage, and divorce records (http://bkaprt.com/eia/o0-01/). As
a frothing-at-the-mouth white supremacist, Plecker was terri-
fied of interracial marriage. Its very existence, he insisted, was
the result of poor categorization: white people were marrying
non-white people only because the government hadn’t labeled
them “correctly.”

Plecker decided that he could use bureaucracy to change this,
and he was right: all he had to do was relabel Virginia’s racial
categories, and racist laws took care of the rest. He reduced the
number of racial identity categories to just two, then altered and
enforced documentation to reflect his definitions.

This meant that a very small and specific group of people
were labeled white, and everyone who fell outside of Plecker’s
narrow view were not—and their lives changed accordingly.
The government saw them differently, identified them dif-
ferently, treated them differently. They no longer had access
to the same public spaces, the same schools, the same ser-
vices and safety nets afforded to white people. Marriages were
invalidated. Children were separated from parents. Virginians
lost agency over who they were—all because Walter Plecker
changed a label.

Changing a label is a design decision—one calculated, in this
case, to disenfranchise specific human beings.

Now, most of us don’t have Walter Plecker’s job. We are,
instead, designers, developers, copywriters, strategists. We
work on the web, and we may not think our work carries that
same weight.

I'm here to argue that it does. Whatever our role, we are
designers of information. Our choices alter the presentation
and flow of human knowledge. We control how people find,
understand, and use information in every facet of their lives.

‘We must be very, very careful.

How designing information can change the lives and the world

TL;DR; Use hsl isntead of RGB to create a gradient. This will avoid a grey zone. But using hsl is not available in CSS for now, so we can use a linear-gradient from a multiple of colors instead. Each color have to be similar to its neighbors... and it works !

and here the tool: https://www.joshwcomeau.com/gradient-generator/

Critiquer Rust sous prétexte que c’est un langage complexe conduit à passer à côté de ce qui fait sa force : il est pensé pour être expressif, ce qui signifie qu’il y a beaucoup de fonctionnalités, et dans la majorité des cas c’est ce que vous attendez d’un langage de programmation.

L'article est bien complet !

Mon avis: utiliser Go pour le code qui doit être déployé demain, Rust pour le code qui devra rester en production tel quel pour les 5 prochaines années
—Grzegorz Nosek

peut-on encore légitimement parler « d’une langue française » ou doit-on désormais parler de « plusieurs » langues françaises ?

Mais notre réponse scientifique est qu’il existe bien un corpus de règles générales fondamentales, une matrice de base sur laquelle viennent se greffer tous les usages Concernant les expressions figées, qui semblent a priori les plus variables

Display an item on scroll.

A tool similar to Shaarli: a bookmarks service that provide magic link (permalink), categories, etc...

Some are

Resting awareness

• Meditation
• Mindfulness
• Reflection
• Body scanning
• Visualization
• Note-taking
• Mindful programming

and related tips for casual cases !

Funny as it may sound, sleep is a really good technique to refresh our minds and bodies.

🤣

Fixed my issue on Arduino Genuino

1. I still don't know very much.
2. The hardest part of software is building the right thing.
3. The best software engineers think like designers.
4. The best code is no code, or code you don't have to maintain.
5. Software is a means to an end.
6. Sometimes you have to stop sharpening the saw, and just start cutting shit.
7. If you don’t have a good grasp of the universe of what’s possible, you can’t design a good system.
8. Every system eventually sicks, get over it.
9. Nobody asks "why" enough.
10. We should be far more focused on avoiding 0.1x programmers than finding 10x programmers.
11. One of the biggest differences between a senior engineer and a junior engineer is that they’ve formed opinions about the way things should be.
12. People don’t really want innovation.
13. Your data is the most important part of your system.
14. Look for technological sharks.
15. Don't mistake humility for ignorance.
16. Software engineers should write regularly.
17. Keep your processes as lean as possible.
18. Software engineers, like all humans, need to feel ownership.
19. Interviews are almost worthless for telling how good of a team member someone will be.
20. Always strive to build a smaller system.

A blog post as response to it ?

La qualité des appels audio passé avec le navigateur devrait être de meilleure qualité. En effet, la suppression du bruit, le contrôle automatique du gain et l’annulation de l’écho connaissent des améliorations significatives pour offrir une meilleure expérience.

+1

Le deepfake est bien réalisé, il faut oser prendre le président de la république dans une telle parodie.

Another one ! :D

(via https://nicolas-delsaux.hd.free.fr/Shaarli/?vtr8ew)

Utiliser les issues de ces deux plateformes pour avoir des cheatsheets :)

Download video from the web on mobile phone. It uses yt-dlp (formerly youtube-dl) 👍‍

2/3/22 ... U.S. formatted or E.U. formatted x)

Individuellement, ils sont plus au chômage, perçoivent plus d'allocations, c'est vrai. C'est le raccourci qui est souvent mis en avant pour dire qu'ils coûtent très cher à la France. Sauf que ce résultat individuel est compensé par une structure d'âge, avec des immigrés qui sont souvent dans la population active et qui donc cotisent beaucoup.