sansguidon/bookmarks
1
0
Fork 0
Code Issues 16 Pull Requests 1 Packages Projects 1 Releases Activity

clean code tips by Victor Rentea

Browse Source
This commit is contained in:
Morgan 2017-11-06 11:06:20 +01:00 committed by GitHub
parent e2b99eb947
commit 64cab43ceb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
PRINCIPLES.md
View File

@ -68,6 +68,11 @@
* The Art Of Clean Code by [Victor Rentea](https://www.youtube.com/watch?v=J4OIo4T7I_E) * The Art Of Clean Code by [Victor Rentea](https://www.youtube.com/watch?v=J4OIo4T7I_E)
* Make it more readable even if it makes writing harder : We read 10x more times than we write * Make it more readable even if it makes writing harder : We read 10x more times than we write
* Boy scout rule : always check in code cleaner than you found it * Boy scout rule : always check in code cleaner than you found it
* Functions are verbs
* Boolean names should always answer yes/no
* Classes are nouns. Avoid meaningless names (OrderInfo, OrderData vs Order)
* Delete the interfaces : except for Remoting/API client jars and strategy pattern implementation.
* Make the name speak for itself
## personal thoughts ## 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. * [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.