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 you are using dynamic memory allocation.
  • Putty to connect to a remote machine.
  • WinSCP or FileZilla to ftp files on a remote machine.
  • IDE ( Integrated Development Environment) for rapid development.
Best Practice 8 -Leave the ego behind, Be eager to learn

Bu blogdaki popüler yayınlar

SDLC - Software Development Life Cycle

Resim
SDLC -  Software Development Life Cycle  is a process used by the software industry to design, develop and test high quality softwares. 1- Requirement Analysis 2- Defining Requirements To clearly define and document the product requirements SRS (Software Requirement Specification)   document which consists of all the product requirements to be designed and developed during the project life cycle. 3-   Designing the Product Architecture One design approach for the product architecture is proposed and documented in a DDS - Design Document Specification . DDS is reviewed by all the important stakeholders and based on various parameters as risk assessment, product robustness, design modularity, budget and time constraints, the best design approach is selected for the product. DDS defines all the architectural modules of the product along with its communication and data flow representation with the external and third party modules. 4- Developing the ...
Devamı

@SerializedName and @Expose annotations

The  @SerializedName  annotation is needed for Gson to map the JSON keys with our fields. In keeping with Java's camelCase naming convention for class member properties, it is not recommended to use underscores to separate words in a variable.  @SerializedName  helps translate between the two. @SerializedName ( "quota_remaining" ) @Expose private Integer quotaRemaining; In the example above, we are telling Gson that our JSON key  quota_remaining  should be mapped to the Java field  quotaRemaining .  If both of these values were the same, i.e. if our JSON key was  quotaRemaining  just like the Java field, then there would be no need for the  @SerializedName  annotation on the field because Gson would map them automatically. The  @Expose  annotation indicates that this member should be exposed for JSON serialization or deserialization. 
Devamı