In philosophy, a razor is a principle that allows one to eliminate unlikely explanations for a phenomenon.

- Occam's razor: Simpler explanations are more likely to be correct; avoid unnecessary or improbable assumptions.
- Hanlon's razor: Never attribute to malice that which can be adequately explained by stupidity.
- Hume's guillotine: What ought to be cannot be deduced from what is.
- Hitchens' razor: "What can be asserted without evidence can be dismissed without evidence."
- Newton's flaming laser sword: If something cannot be settled by experiment or observation, then it is not worthy of debate.
- Sagan standard: Extraordinary claims require extraordinary evidence.

'BUY' ALMOST ALWAYS BEATS 'BUILD' : If you can avoid building something, you should. Code is the most expensive way to solve a problem that isn’t addressing a core area of your business.

MAKE DEPLOYS EASY : Deploying should be a frequent and unexciting activity. Engineers should be able to deploy with minimal manual steps and it should be easy to see if the deploy is successful. (...) It’s not a coincidence that two of the four key metrics that the book focuses on are directly related to this (Deploy Frequency, Change Lead Time). Shipping is your company’s heartbeat.

TRUST THE PEOPLE CLOSEST TO THE KNIVES : The people who work with a system are the ones who understand it best. (...) They should, therefore, be the primary stakeholders responsible for prioritizing technical work.

BORING TECHNOLOGY IS GREAT : (...) you want a wide area of expertise for routine operations and when shit goes sideways (...). Very few organizations have the bandwidth to debug unique problems. (...) Using boring technology means you can lean on a large community of users. Shit on it all you want, but there are very few PHP issues that someone else hasn’t already encountered.

Is there enough computing power in a USB-C charger to take you to the Moon and back ?

The "Let it crash" principle reminds me of the Unix's "Rule of Repair" (https://homepage.cs.uri.edu/~thenry/resources/unix_art/ch01s06.html) : "When you must fail, fail noisily and as soon as possible."

The Incas lacked the use of wheeled vehicles. They lacked animals to ride and draft animals that could pull wagons and plows... [They] lacked the knowledge of iron and steel... Above all, they lacked a system of writing... Despite these supposed handicaps, the Incas were still able to construct one of the greatest imperial states in human history.

Plein de bons conseils, malheureusement souvent mis en pratique :-/

L'ensemble de l'article est aussi vrai que drôle.
Mention spéciale à cette phrase qui a un petit goût de "j'ai-déjà-vu-ça-quelque-part" :

Dans le désordre tu peux obliger tout le monde à travailler minimum 60 H par semaine. Quand les gens n’auront plus de vie personnelle, c’est avec plaisir non dissimulé qu’ils vont chier à l’intérieur de ton projet.

La vérité dans tout ça, c'est que les gens ne savent pas ce qu'ils veulent jusqu'à ce qu'on leur propose.

L'unique façon de vérifier que son idée est bonne, c'est vendre.

Les gens arrêtent de mentir quand on leur demande de l'argent.

Pour ça, la stratégie consiste à créer du contenu tout en donnant la possibilité d'acheter notre produit.

Il existe un terme populaire dans le monde des startups qui résume bien cette stratégie : "Fake it until make it".