Best Practices
Best Practice 1- Keep Reading Existing Software Source Code Best Practice 2 - Complete your documents before next step Best Practice 3 - Follow the defined standards, don't create it Best Practice 4 - Code should be written to be reviewed criticism about one or more of the following points; Bad coding Not following standard Not keeping performance in mind History, Indentation, Comments are not appropriate. Readability is poor Open files are not closed Allocated memory has not been released Too many global variables. Too much hard coding. Poor error handling. No modularity. Repeated code. Best Practice 5 - Testing to be followed like a religion Best Practice 6 - Keep your Code and Documents Safe Best Practice 7 - Keep your Tools & Techniques Handy the essential tools, which should be readily available with a software developer: A good text editor to write and edit the program. A nice debugger to debug the program. A memory detector in case yo...