update principles

This commit is contained in:
Morgan 2021-01-24 12:23:52 +01:00 committed by GitHub
parent b87b3e0b55
commit f33e074839
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -254,3 +254,4 @@ See also [Calm programming / Slow programming](README.md#calm-programming--slow-
* It also means that when building systems, you should not assume that operators will do things correctly. Expect failure from people. Try to think about tools you can give them to undo their mistakes, because they will happen sooner or later. Have some dread. Be understanding. Know things won't be perfect. [source](https://ferd.ca/lessons-learned-while-working-on-large-scale-server-software.html) * It also means that when building systems, you should not assume that operators will do things correctly. Expect failure from people. Try to think about tools you can give them to undo their mistakes, because they will happen sooner or later. Have some dread. Be understanding. Know things won't be perfect. [source](https://ferd.ca/lessons-learned-while-working-on-large-scale-server-software.html)
* Study your tools, see how you work, understand how you can improve it. Don't rush. Before you run, you have to learn to walk. * Study your tools, see how you work, understand how you can improve it. Don't rush. Before you run, you have to learn to walk.
* Wait before jumping on every opportunity/request/problem. Dont touch it / dont act too soon * Wait before jumping on every opportunity/request/problem. Dont touch it / dont act too soon
* Use right tools for the job (email != todo list, PR and commits != code documentation, Jenkins != long term storage for releases/versions/build info/state of quality of your code)