Firefox Relay est un outil semblable à DropMail, Yopmail, etc... ; ce sont des boîtes mails jetables.
La particularité de Firefox Relay est de pouvoir transmettre les messages à la boite mail principale.

A Rust framework used to build web Applications. Detailed in the blog post of sheshbabu

Well-explained ! It takes some times to read it, but some concepts are clear at the end 💡

Cool tips ! The other ones are useful too 😄

if you have Foo and FooBuilder, consider adding a builder method to Foo

that returns the Builder of course

J'ai pas compris les Workspaces 😅 Il y a le RFC correspondant sur Github qui explique bien la chose !

Mais on a :

• des commandes plus rapides avec l'utilisation d'un cache
• le moyen de déclarer que plusieurs modules dépendent d'une seule même version d'un module : les peerDependencies
• la logiqe d'installation des dépendances est un module @npmcli/arborist
• npx est intégré à npm via la commande `npm exec

La page de documentation indique comment résoudre le problème :

• il faut aller dans le dossier du programme Zotero (/opt/zotero ou /usr/lib/zotero à ma connaissance)
• puis aller dans extensions/zoteroOpenOfficeIntegration@zotero.org/install
• exécuter Zotero_OpenOffice_Integration.oxt

Voilà.... 🎉

Pep talk to use microservices 🤣

Wörter : lorsqu'il s'agit d'un nombre précis de mots, dénobrable
Worte : lorsque le pluriel est général, désigne un groupe abstrait de mots

Wörter bestehen aus Buchstaben, Worte aus Gedanken.

About impl Trait

Rule: If a type parameter only appears in one location, strongly reconsider if you actually need it.

The problem of centralized services : when they are down, everything is down

So there is four stages of quality for each name :

• Nonsense : For example, we might extract a method from a larger one and quickly rename it somethingWhatever() to get the refactor done and the tests passing.
• Accurate : We rename the nonsense method to what it actually does, such as processPayroll()
• Precise : Once we realise what the method really does, we might refine the accurate name and give it more precision, such as loopThroughEmployeesAndPayThem().
• Meaningful : At this point, we’ve revealed the complexity of the method, and can look to split it up into two methods: forEachEmployee() and perhaps a payWages() method on a separate interface.

I always use at least accurate names, because it helps me even during the development process. Something I tend to is to use meaningful names and thus creating a lot of functions 😅
I dislike the precise one as it looks as a function that need to be changed, because of doing to much things. At least, this reveals the complexity behind the name.