Developer's Best Practices (Code should be written to be reviewed…
Developer's Best Practices
Keep reading existing software source code
Attributes of Software Codes
check the code you had written
Complete your documents before next step
answer the following
Where is the Requirement Specification ?
Where is the Impact Analysis Document ?
Where is the Design Document ?
Have you documented all the assumption, limitations properly ?
Did you get sign off on all the documents from all the stakeholders?
Tips and tricks
Special function, commands and instructions
Maintain Required Documents
Follow the Defined Standards, don't create it
Search for coding standards of different programming languages
File Naming Convention
Function Module Naming Convention
Variable Naming Convention
History, Indentation, Comments
Readability and guidelines
List of do's and don't
Code should be written to be reviewed
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
Always have a testing
Bugs are your enemies, so you have killed one
Now your software is having one bug less
mistakes are good as long as they are not repeating
What you learn today, prepares you tomorrow
Keep your code and documents safe
Proper Source Code Version Control System
Never share your password
Keep your Tools and Techniques handy
good text editor
a memory detector
putty to connect to a remote machine
WinSCP or FileZilla to FTP files
Integrated Development Environment (IDE)
Always keep adding techniques
Leave the ego behind, Be eager to Learn
Ask from colleagues
understand the support of others
Keep yourself updated with latest tools and technologies
Technical forum over the internet
Technical magazine on various IT subjects
Technical bulletin boards
Conferences, Training and workshops
Latest version of old tools and packages, languages, etc.