Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Mikah’s ideas

  1. Highest priority

    1. All code should be in a repository

    2. Repositories should have at least 2 branches at all times (master/dev)

    3. Code should be meaningfully documented (ideally in confluence) and linked in the README

    4. If an intern/temporary employee is the main developer the above is especially critical

  2. High priority

    1. Resources should be hosted in azure

    2. Languages should be well known by other people on the team

    3. Limit proprietary solutions (data bricks etc)

    4. Separate resources into logical groups (don’t put API, web app, db on one VM)

  3. Medium priority

    1. Use git flow (feature branches)

    2. Have master and dev be protected branches

    3. Enforce meaningful code review

    4. Detailed notes on each PR explaining what’s going on

    5. No mega PRs (10+ files changed etc) unless absolutely needed

    6. Issue tracking via github issues or jira

  4. Low priority

    1. Have tests

    2. Have CI/CD

  • No labels