Difference between revisions of "CodingStyles"
From Lost In Wonderlands
(Created page with "= Coding Styles= ''by paul.plaquette, Senior Software Engineer, Trilda Open Source'' '''NeXT Steps''' ''here everything has yet to be done !'' ''coming soon'' : '''''Ev...") |
(→Coding Styles) |
||
| Line 1: | Line 1: | ||
= Coding Styles= | = Coding Styles= | ||
| − | ''by paul.plaquette, | + | ''by paul.plaquette, Experimented R&D Software Engineer, Trilda Open Source'' |
'''NeXT Steps''' | '''NeXT Steps''' | ||
Revision as of 14:12, 1 April 2017
Coding Styles
by paul.plaquette, Experimented R&D Software Engineer, Trilda Open Source
NeXT Steps
here everything has yet to be done !
coming soon :
Everything You Always Wanted to Know About Re-factoring... (But Were Afraid to Ask)
Re-factoring is the process of redesigning software architecture and source code in which anti-patterns were identified using Design Patterns
See also
- DesignPatterns
- AntiPatterns
- Refactoring
- CleanCode
- SecureCode
- UML
- SOLID
- Packages Principle
- KISS
- DRY
- GRASP
- YAGNI
Preferred Coding Styles
Remember
- a function name should be descriptive and short
- a function should not have more than 3 parameters in argument list , or should use the memento design pattern
- a function is supposed to do only one thing.
- a function should not be very indented
- a function should be short: only a few lines of code
- a function code should be self descriptive (not comments needed)
in C
in C++
in CSS
in HTML
in Java
in JavaScript
in Objective C
in PHP
in Python
Coding styles
in C
- https://www.kernel.org/doc/Documentation/CodingStyle
- http://www.gnu.org/prep/standards/standards.html
in Python
