Professional Documents
Culture Documents
Coding
● No development should happen in the Production/Live branch directly.
● Sprint will be followed for each coding cycle .
● Code Simplicity: The simpler the code, the easier it is to test and change. Whenever you have a
new developer come on board, it takes them time to learn the new code, reducing that time by
having your codebases written simply.
Code Review
● Proper code review should be done before the testing deployments.
● make sure the components should be reusable. Also deprecated APIs and code should be
identified.
Deployments
● Before deploying the code, there should be a proper code review and the changes (in case if
required) confirmation from your lead.
● Commit should happen on a daily basis on the staging branch. No development should be left on
your local machine at the end of day.
Sharing Knowledge : The more sharing that is done, via code documentation, collaborative meetings,
sharing of new things learned or articles written, the less management.