Comment perdre 30 min

:set backupcopy=yes

When you want to modify a file, you have two options, each with its benefits and drawbacks.

You can overwrite the file in place. This does not use any extra space, and conserves the hard links, permissions and any other attribute beyond the content of the existing file. The major drawback of doing this is that if anything happens while the file is being written (the application crashes, or the power goes out), you end up with a partially written file.
You can write the new version of the file to a new file with a different name, then move it into place. This uses more space and breaks hard links, and if you have write permissions on a file but not on the directory it contains, you can't do it at all. On the flip side, the old version of the file is atomically replaced by the new version, so at every point in time the file name points to a valid, complete version of the file.

http://vimdoc.sourceforge.net/htmldoc/options.html#%27backup%27

Big-O illustré en ruby

Je l'aime bien cet olivier, j'ai découvert son blog au tout début, j'étais en BTS donc 2009, j'ai commencé avec le bouquin la semaine de 4h et j'ai en lu une dizaine suggéré. J'aime bien alterner les lecture fiction et non fiction, ça change un peu et on apprends des choses même si c'est souvent du bon sens, on découvre d'autres manières de voir les choses

je découvre ce plugin vim qui a l'air juste magique pour interagir avec git

il faut que je me fasse au workflow "Branch updater"

aws community guide

Keepalive Notes

A keepalive packet generally has a TCP ACK configured with a sequence number set to one less than the current number used on the connection. Any machine receiving a nudge from such a packet will simply respond with the correct sequence number and, Frankenstein jokes aside, announce that it is indeed alive.

These types of packets are sometimes empty and generally have three associated parameters. The retry parameter will declare how many times to send a packet before coming to the conclusion that the other end of the connection has given up the ghost. The time setting is configured as the frequency of the checks, and finally the interval dictates the length of time between two sent packets if no response is received.

Inside the kernel, you can alter these settings by editing these values in the eye-watering pseudo-filesystem known and loved as /proc. One file, in this case, is /proc/sys/net/ipv4/tcp_keepalive_time, and you can edit it

man systemd.index