There goes my boss again calling me police or asking me to issue summons this year if the codes is not of good quality.
Two years ago, I helped to ‘quality-check’ nearly everyone’s codes and came up with some documentation of coding standards to follow. However, this time is different. There are many more developers working on the same large-scale project and it is getting difficult to distinguish whose work it belongs to and the style of developers may need to be kept in check to follow the company’s coding standards. I have to dig out the old codings standard and review it and improve it for everyone to follow.
Quality Code / Coding standards need to be kept in check because it will grow messier and out of control. Some codes may be duplicated and the number of files are growing exceptionally larger for the big project. I think it may also breed some hidden errors. Well, let’s not talk about Unit Testing and Eliminating Errors yet. Some authors think it’s good to re-write the codes to make it short yet work the same way as before? I will also recommend putting author, date of creation, modification details so that we can keep track of the changes with one another instead of asking “WHO DID THE FILE?” OR “WHO CHANGED THE FILE?”
Perhaps you could look at this http://coldfusion.sys-con.com/read/41972.htm to understand why coding standards is very important in the development and maintanence of codes.
Url: http://coldfusion.sys-con.com/read/41869.htm
Url: http://www.informit.com/articles/printerfriendly.aspx?p=24131
Url: http://www.tutorialized.com/view/tutorial/Writing-Maintainable-Code/7166
Url: http://www.adobe.com/devnet/coldfusion/articles/cfc_practices.html
Url: http://coldfusion.sys-con.com/read/41971.htm
Ha, I never think of this. Spotting the worst practices for coldfusion… Good idea to read this up and see how to spot mine and the team… Wish me best!
Url: http://coldfusion.sys-con.com/read/41871.htm
