Skip to content

Instantly share code, notes, and snippets.

@mmyoji

mmyoji/dev-team-should-be.md

Last active June 17, 2022 01:42
Show Gist options
  • Save mmyoji/f70eb897831535e1cef35b8b32397ac7 to your computer and use it in GitHub Desktop.
Save mmyoji/f70eb897831535e1cef35b8b32397ac7 to your computer and use it in GitHub Desktop.
Download ZIP
Dev team should be
Raw
dev-team-should-be.md
  • Using GitHub, GitLab or similar de facto git hosting/collaborating services
  • Many public chat messages, a few private ones
  • Preferring remote/asynchronous communication to synchronous one
  • Well-tested and -documented applications
  • No routine meetings: discuss whenever necessary
  • Higher priority for code review with respecting team mates' motivation
  • Make code/projects public as mush as possible rather than trying hard to write "tech blog"
  • CI/CD
  • linter/formatter: not discuss code styles or preferences during code review

Git specific

  • Well-written commit messages: why you do this? what is another option you discard?
  • Single commit should pass CI
  • Delete stale/merged branches
  • Commit messages have consistent tense (present or past)
  • rebase base branch before code review
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment