html {
  max-width: 70ch;
  padding: 3em 1em;
  margin: auto;
  line-height: 1.75;
  font-size: 1.25em;
}

and 100 more bytes:

h1,h2,h3,h4,h5,h6 {
  margin: 3em 0 1em;
}

p,ul,ol {
  margin-bottom: 2em;
  color: #1d1d1d;
  font-family: sans-serif;
}

Testomony and feedback after 100 posts written.

Here the tips I find relevant for myself:

*Write about the topic, even if it has been covered elsewhere. Your perspectives, experiences, and understanding are the unique bit. People want to read your work.

• Learn to identify the difference between constructive criticism and unproductive harassment. It’ll help you focus on what matters and not waste time and energy.
• Get comfortable getting rejected. While the sting never really goes away, you do grow a thicker skin.
• Read your writing out loud to yourself before publishing it.
• Read it out loud again.

How to hide desktop icons on ubuntu (on 21.04):

sudo apt install gnome-shell-extension-prefs
gnome-shell-extension-prefs

Deactivate Desktop Icons NG (DING)

Older methods does not seems to work (gnome tweak tools, etc...).

How to disappear from Google searches:
<meta name="googlebot" content="noindex">

Your docs belong in the code repository
Your docs is not extracted from code
Your docs features examples
You document every API call you provide
Your docs is easily accessible and browsed
Your docs should be easy to contribute to

and the example of curl.

That way in a moment of full-disk crisis I can simply delete it and buy myself some critical time to debug and fix the problem. 8GB is a significant amount of space, but storage is cheap enough these days that hoarding that much space is basically unnoticeable... until I really need it.

Only one same job at a time ?

My solution to deal with this is to bind an IPv6 localhost ::1 socket to a given port. Only one process can do this, and thus it’s a very effective mutex. No lock files to cause havoc, no dealing with the dark and buggy corners of advisory file locking.

For shell scripts, simply replace the #!/bin/sh with #!/somewhere/bin/lock 2048 where 2048 is the port number you will use to enforce the lock (greater than 1024 if you do not want to deal with the hassles of privileged ports).

31 tips after 10,000 hours of programming.

Takeaways:

• It is possible to list a directory with 8 million files in it.
• strace is your friend
• Don't be afraid to compile code and modify it (hell, simple C compiles so fast it could be interpreted)
• There is no good reason to have 8 million files in a directory :-), but this was a good learning experience (and possibly a good interview question).

The last point is the most important :D

$'$HOME' expands escape sequences like \n or \'

• Shallow cloning avec GIT_DEPTH=1
• Cache
• Artefacts
• Retry
• Évitez les déploiements depuis les forks
• Sécurité - Lockez vos versions pour rendre vos builds reproductibles
• Sécurité - Services intégrés

Amend a commit message by ID. A simple script.

Si le montant des billets à échanger sont inférieurs à 800€, LaPoste les échange gratuitement.

Les bureaux de postes effectuant ce service sont détaillé dans un fichier .xls. Ils sont peu nombreux malheureusement, mais c'est déjà ça.
Les pièces à fournir sont aussi détaillée.

opt-out FĹoC Header... but how do you know that the reference on Google search will not depend on this too ?

Thanks for sharing all the configurations !

Using <wbr> where it can break. It is useful for URLs.

Yes 👍

Trouvé sur le net:
« Quand vous prenez un TGV et que vous voulez utiliser le wifi
=> ouvrez la page de connexion
=> Demander l'aide du bot
=> Dites que vous avez un billet étranger
=> Voila, vous avez accès sans donner votre idenfication. Vous pouvez lancer votre vpn »

I really enjoy the explanation on how to use pushd and popd to navigate between directories.
After pushd, it is possible de navigate through cd ~n with n the index of the path in the stack.

cd - to return to the previous path :)