The remainder is NOT a modulo.

[...] the difference being that the modulo operator result would take the sign of the divisor, not the dividend.

The Law of Triviality, illustrated. https://en.wikipedia.org/wiki/Law_of_triviality

In the third chapter, "High Finance, or the Point of Vanishing Interest", Parkinson writes about a fictional finance committee meeting with a three-item agenda:[1] The first is the signing of a £10 million (£221.3 million in 2016 money) contract to build a reactor, the second a proposal to build a £350 (equivalent to £7,744 in 2016) bicycle shed for the clerical staff, and the third proposes £21 (equivalent to £465 in 2016) a year to supply refreshments for the Joint Welfare Committee.

The £10 million number is too big and too technical, and it passes in two and a half minutes. One committee member proposes a completely different plan, which nobody is willing to accept as planning is advanced, and another who understands the topic has concerns, but does not feel that he can explain his concerns to the others on the committee.

The bicycle shed is a subject understood by the board, and the amount within their life experience, so committee member Mr Softleigh says that an aluminium roof is too expensive and they should use asbestos. Mr Holdfast wants galvanised iron. Mr Daring questions the need for the shed at all. Holdfast disagrees. Parkinson then writes: "The debate is fairly launched. A sum of £350 is well within everybody's comprehension. Everyone can visualise a bicycle shed. Discussion goes on, therefore, for forty-five minutes, with the possible result of saving some £50. Members at length sit back with a feeling of accomplishment."

Parkinson then described the third agenda item, writing: "There may be members of the committee who might fail to distinguish between asbestos and galvanised iron, but every man there knows about coffee – what it is, how it should be made, where it should be bought – and whether indeed it should be bought at all. This item on the agenda will occupy the members for an hour and a quarter, and they will end by asking the secretary to procure further information, leaving the matter to be decided at the next meeting."[5]

Given all the time and effort collectively spent debugging by the software industry, it makes sense to explore the notion of formalizing the practice.

The paper illustrating some concepts from the people who created the object-oriented paradigm. A great read according to Avdi Grimm.

good read

Another interesting framework built on top of Vue.js

Un bouquin en ligne sur Git
– via sebsauvage

Probably another book I should take on

A sarcastic Git man page generator, because you don't even know git

Tailwind is different from frameworks like Bootstrap, Foundation, or Bulma in that it's not a UI kit.

to watch later

A lot of different noises, very interesting. I only knew about white noise.

Just a very lengthy but thorough article on home insurance

Reference for ES2015, keep it open at all time when learning JS

Interesting post about enforcing unique usernames on a website and what examples could lead to some social engineering fails.

To read later, but seems complete. I also want to adapt the back-end to use Ruby on Rails instead of Laravel.

Help people fix it themselves. Help people help you. Turn contributors into co-maintainers. Most importantly, don’t let those notifications build up and stress you out.

Do all this as a precaution before you get stressed and burnt out.

title says it all

very detailed article about Netflix and their content distribution system

You can't fully understand databases, NoSQL stores, key value stores, replication, paxos, hadoop, version control, or almost any software system without understanding logs