Shared Team Values/Principles/Good Practices #71
josecelano
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
From the internal weekly meeting: https://github.com/orgs/nautilus-cyberneering/discussions/66#discussioncomment-7534160
Hi all (@da2ce7, @cgbosse, @mario-nt, @grmbyrn, @WarmBeer) for the next meeting I would like to add a topic for discussion. I would like to share my view on prioritising tasks and how I try to contribute.
How to prioritize
3.1 Reply to new issues
3.1 Reply comments
3.2 Review PRs
3.3 Merge PRs
4.1 Reply team members waiting for feedback, review, …
4.2 Help team members
6.1 Fix broken things
6.2 Implement small issues (those taking less than 1 day)
6.2.1 Update dependencies
6.2.2 …
6.3 Review and close stale issues
7.1 Deliver things before starting new ones. “Good code is worthless in Git” (the sentence is not mine).
In my daily routine, I always check that there is no higher-priority task.
How to develop (values/principles/good practices)
- Introduce changes progressively.
- They are easier to rollback
- They are easier to integrate (merge).
Resources
I think some companies are doing a great job explicitly defining their values/principles/practices, like for example, Audiense. See https://github.com/AudienseCo/engineering-principles.
Audiense Values
Lean (Software/Product) Development Resources:
Beta Was this translation helpful? Give feedback.
All reactions