From 9f50b76eba5df46d4a2fe342ef51c455f783990b Mon Sep 17 00:00:00 2001 From: Morgan Date: Mon, 15 Feb 2021 08:29:52 +0100 Subject: [PATCH] Slow programming tips --- PRINCIPLES.md | 1 + 1 file changed, 1 insertion(+) diff --git a/PRINCIPLES.md b/PRINCIPLES.md index 3d85811..ec6fb96 100644 --- a/PRINCIPLES.md +++ b/PRINCIPLES.md @@ -278,6 +278,7 @@ See also [Calm programming / Slow programming](sections/programming.md#calm-prog * Comment. * More so than all other tools (issue tracker, code management system, etc.) comments in code have the greatest chance of still being around and easily searchable if they haven't been deleted. **See also** [Ref : The case for comments in code](https://notes.eatonphil.com/the-case-for-comments-in-code.html) * Code can’t self-document if it isn’t there. If you decide to not write some code and don’t leave a comment explaining why, there will be nothing left to explain what you were thinking! Add comments that explain why the code is doing what it is doing, or is structured the way that it is structured. **See also** [Ref : How to write readable code](https://jeremymikkola.com/posts/2021_02_02_how_to_write_readable_code.html) +* When you're done with your commit and push, just double check what you have just done. Sometimes issues or possible improvements appear obvious only when the work is already pushed. Next time, slow down and double check before pushing ;-) ## Slow programming Healthy tips / helpers * Disconnect & Focus. Value your time, use it to focus. Put lot of non-meeting blocks in your agenda.