Hi all,
While Browsing through Microsoft Dynamics Community i Found C/AL Coding Guidelines under Design Pattern.
Let's Make Use of the Same Guidelines and share it with all your colleagues to follow standard and to Keep the code as clean as you can.
This is what i feel About Coding -
-- Yes everyone who is a technical can write so many codes but before writing do think.
-- Writing a FindFirst and FindSet make hell lot of difference when i look it in terms of Performance.
-- We Teach our New NAV Consultants how to write Code, we never teach them how to Write an Optimize Code.
-- I Still remember when i started my career i was eager to write code as soon as i heard a requirement, but after nearly five years i think before writing a piece of code.
Humble Request -
-- Do Follow Best Practice while writing a Piece of Code.
-- Try to Impart the Optimize Code Practice to your Peers & Juniors.
Why We Need To Do This -
-- If the Code is optimized the performance will be good.
-- The Dependency of the Developer will be less as the code will be readable.
-- During a Partner Change via Customer we keep on getting codes written by someone else, if that is optimized it make life easier.
Below are the Links to Download the C/AL Coding Guidelines -
1. Source - Microsoft Dynamics NAV Community
2. Dennis Pardaan Blog - (unofficial) PDF of the guidelines
3. Download From Sky Drive - Unofficial PDF & Official (From Microsoft). ** BOTH
4. Official PDF - From Microsoft.
Let's Read, Understand and Share the Coding Guidelines and Make NAV Code Optimize & easy to Read.
Regards,
Saurav Dhyani
saurav-nav.blogspot.com
While Browsing through Microsoft Dynamics Community i Found C/AL Coding Guidelines under Design Pattern.
Let's Make Use of the Same Guidelines and share it with all your colleagues to follow standard and to Keep the code as clean as you can.
"A Good Written Code is Always Easy to Read by anyone and that is the first step for a good Performance too. "
-- Yes everyone who is a technical can write so many codes but before writing do think.
-- Writing a FindFirst and FindSet make hell lot of difference when i look it in terms of Performance.
-- We Teach our New NAV Consultants how to write Code, we never teach them how to Write an Optimize Code.
-- I Still remember when i started my career i was eager to write code as soon as i heard a requirement, but after nearly five years i think before writing a piece of code.
Humble Request -
-- Do Follow Best Practice while writing a Piece of Code.
-- Try to Impart the Optimize Code Practice to your Peers & Juniors.
Why We Need To Do This -
-- If the Code is optimized the performance will be good.
-- The Dependency of the Developer will be less as the code will be readable.
-- During a Partner Change via Customer we keep on getting codes written by someone else, if that is optimized it make life easier.
Below are the Links to Download the C/AL Coding Guidelines -
1. Source - Microsoft Dynamics NAV Community
2. Dennis Pardaan Blog - (unofficial) PDF of the guidelines
3. Download From Sky Drive - Unofficial PDF & Official (From Microsoft). ** BOTH
4. Official PDF - From Microsoft.
Let's Read, Understand and Share the Coding Guidelines and Make NAV Code Optimize & easy to Read.
Regards,
Saurav Dhyani
saurav-nav.blogspot.com
Comments
Post a Comment