From 7f1c52a5ddfc83c2b54eccfc8f45afb71b662900 Mon Sep 17 00:00:00 2001 From: Lex Berezhny Date: Tue, 31 Jul 2018 12:34:12 -0400 Subject: [PATCH] Updated Zen of LBRY Development (markdown) --- Zen-of-LBRY-Development.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Zen-of-LBRY-Development.md b/Zen-of-LBRY-Development.md index 1a28ba0..d579917 100644 --- a/Zen-of-LBRY-Development.md +++ b/Zen-of-LBRY-Development.md @@ -5,7 +5,7 @@ 1. Avoid loops in unit tests. 1. Learn and use many of the `unittest` assert methods. 1. Use function name to document what the function does. -1. Split large functions into smaller ones and use function name to document what the function does. +1. Split large functions into smaller ones and see previous rule. 1. Don't write redundant comments or doc strings. 1. Do write comments or doc strings to include references to specifications or other resources. 1. Prefer writing clear code instead of clear comments to explain unclear code, clearly.