1. Never blame users and introduce change on every issue

   There are no bad users—only bad user experience.

2. Report issues no matter what

   Even simple reporting can be a significant contribution.

3. Have trust in automated tools

   Takeaway: People make mistakes. Prefer automatic tools. Let the robots do the work!

Yes and these are reasons to do it

Quicknotes :

Five 9s : 99.999% uptime [where are they now ?, AN]
Avoid loss of capabilities

Robustness is declining
Productivity is declining [not sure about that..., AN]
The argument that software is advancing is obviously false

Techonology, by itself, will degrade
We must simplify by itself, at every level:

• the hardware
• the OS
• the libraries
• the application code
• the communication systems (e.g. internet)
• how we compile
• how we debug
• how we distribute
• how people interface with software

Surviving as a developper : removing complexity is the right short-term play, even if it doesn't seem so.

Le même x)

La plupart des gens qui se sont posés la question sont d’accord sur ce point : il faut entre 600 et 1000 heures de pratique pour devenir développeur “opérationnel”

Mais oui, totalement !

Oui !

About Svelte, React and WebComponents, . Somethings to remember

Youhou, some comic strips about developer's lifes

Cet article m'a fait tellement de bien. Moi qui défendait Python, mon premier langage de programmation et maintenant Rust.

Avec la référence pour comprendre ce qui exprimé par « rube-goldberg »

Lorsque aucune maintenance n'est prévue, un badge a apposer sur la documentation du projet : No Maintenance Intended