• peer review
    Best Practices,  Life of A Developer

    Do not let User Tell what is wrong about your Application

    It is a good practice to review your code and not wait for the user to complain.¬† Other developers get too much comfortable when testing the software as they think that users make great testers and will eventually tell if something is wrong. This lead to oversight of a crippling bug that affects the business.   Code Reviews Code reviews are extremely important in ensuring the quality of codes delivered. Conduct code reviews as if you are checking the implementation of the code not just abiding some sort of standards like variable naming and layouts. Code reviews keep error rates low.   How do you review codes? You can do…

  • Collective code ownership
    Best Practices,  Life of A Developer

    Benefits of Practicing Collective Code Ownership

    Collective code ownership, in simple terms, is sharing code and design responsibility among the team members. A sole developer who is working on a piece of a module in a nontrivial project should consider letting other team members look into their code and do necessary refactoring. It is a practice in extreme programming which helps¬†deliver high-quality software and respond to the customer changing needs. In a workplace with “strong code ownership”, developer tend to not let other developers add functionality, change the approach or refactor as they will be held responsible if something went wrong. In collective code ownership, any developer has the change to modify and refactor the code…