CODE RIGOR

The second one among "the coder tricks" (the prime one).


They say I am a pragmatic software guy. Do not be afraid of me, nothing about barbarity, ego or intollerance. Mastering code rigor today means to simplify code access to you and to your peers (company buddies). In few words mastering code rigor is the ability to not reinvent the software practice every day... Code rigor is undoubtly a good quality to own and nevertheless a good engineering doing!

Here, in this website, I offer some *pragmatic* examples you can browse and reuse like I always do (Please be aware that the list doesn't want to be complete and just refer to my personal take at everyday coding):

GENERAL PRACTICE

WRITE DOWN YOUR THOUGHTS
A coincise but good analysis *screwing out the prb* can help you in identifing constraints and to stick on the piece.

SIMPLICITY
When you write coincise code, doc and notes get mostly useless at readabiliy advantage.
Furthermore, sometimes, night time doesn't allow you to grasp anything else but simple stuff..

NOMENCLATURE CONVENTIONS (constants, variables, functions and other declarations)
Camel case or whatever, adopt them as soon as possible and stick on them, avoiding changes of mind.

DOCUMENTATION CONVENTIONS
Likewise, adopt them immediately and keep.

AGILE CODE
Use software practices like a standard project structure.
Make procedural code by functions, do not repeat code if it musts be reused.

SECURITY
Reach a good summary about the security of your code (eg. how your software parts can or can't be visible).
Don't be paranoid: avoid to make life frustating to your endusers.

INTERFACE (THE GUI!)

SIMPLICITY AGAIN
Do it simple for your enduser, like you want to be treated yourself..

YOU FORGOT THE TITLE
Time to market and ansiety take to forget about the most obvious stuff of this world! And, yes, it is about you too.

TEST, TEST AND REBUILD
Occasionally you can discover that you have no audience at all and for some good reasons: businesses often need a refresh like your software do.

PHP

NO PEAR EXTENSION
When you practice simplicity the complexity to manage php extensions doesn't make for you..

BE CLEAR
Expecially when you work with peers avoid (if it isn't impossible) to mix up server side code with html.
Well, PHP functions to write just client code are to avoid.

DO YOUR *SPEECH CHOISES*
PHP language is all but sleem, choose carefully commands and paradigms to keep or to avoid.