From c411e0a9e25dc18737d925e247a920a6d84ebc36 Mon Sep 17 00:00:00 2001 From: Morgan Date: Sat, 4 Nov 2017 10:19:57 +0100 Subject: [PATCH] Adam Chester principle about doing it well --- PRINCIPLES.md | 1 + 1 file changed, 1 insertion(+) diff --git a/PRINCIPLES.md b/PRINCIPLES.md index bec81a7..d405bc1 100644 --- a/PRINCIPLES.md +++ b/PRINCIPLES.md @@ -63,6 +63,7 @@ * Keep your code absolutely simple. Keep looking at your functions and figure out how you simplify further - [John Romero](https://twitter.com/CodeWisdom/status/926568192729894912) * Fix it immediately, but plan for the future fix. Document the fix. Automate the solution. [Adam Bertram](https://www.pluralsight.com/blog/it-ops/troubleshooting-tips) * Finding errors in your past decisions and ideas means you’re progressing. - [Greg Kogan](https://www.gkogan.co/blog/progression/) +* You can’t go fast when everyone is spending their time fighting with the poor decisions of yesterday - [Adam Chester](https://twitter.com/adamchester/status/925479016798109696) ## personal thoughts * [MorganGeek](https://twitter.com/MorganGeek/statuses/420907517934178304) - Problem solving / Productivity : Good programmers write code after they found the solution. Un bon programmeur ne commence à coder qu'après avoir trouvé une solution.