Draft: Document Engineering Culture Values in Handbook
Why is this change being made?
This MR is a Draft of Engineering Culture Values.
FAQ
Why do we need this new page?
Our engineering department grows and it might be important to foster a strong engineering culture, similarly to how we evolve our Company Culture. The values defined here are the same Values we documented on our GitLab Values page, but the new page clarifies them in the context of the software engineering practice.
Why can't we document this on GitLab Values page?
I imagine that if we merge this (or similar) content we may want to extend it with more concrete examples, patterns, heuristics that will become a guidance for us as our engineering department grows. The amount of content can grow quickly, and that this the main reason why I thought about separating these pages. Also, for the bigger part of the organization, the Engineering Culture Values would not be very meaningful, because other departments like Sales, Marketing, operate in a different context, and "triangulating abstractions" heuristic might not be very useful for them, hence documenting them on the main Company Values page might clutter the page with content that is irrelevant for most of the team members.
Recommenders
Author Checklist
-
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what -
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) -
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR