Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 17:08:53 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 83

Update engineering handbook (#9729)

Browse source
This commit is contained in:
Luke Heath 2023-02-15 23:45:37 -06:00 committed by GitHub
parent 6a1a6f48c2
commit e822c7e1db
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 19 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

25
handbook/engineering/README.md
View file

@ -22,8 +22,7 @@
### Principles
- Support the [Maker Schedule](http://www.paulgraham.com/makersschedule.html) by keeping meetings to a minimum.
- Each individual must have a weekly sync 1:1 meeting with their manager. This is key to making sure each individual has a voice within the organization.
- Each team should have a fixed weekly sync check-in. This helps reinforce team bonds and alignment.
- Each individual must have a weekly or biweekly sync 1:1 meeting with their manager. This is key to making sure each individual has a voice within the organization.
- Favor async communication when possible. This is very important to make sure every stakeholder on a project can have a clear understanding of what’s happening or what was decided, without needing to attend every meeting (i.e., if a person is sick or on vacation or just life happened.)
- If an async conversation is not proving to be effective, never hesitate to hop on or schedule a call. Always document the decisions made in a ticket, document, or whatever makes sense for the conversation.
@ -88,31 +87,19 @@ For each attendee:
A chance for deeper, synchronous discussion on topics relevant to that group. Held weekly for 30 minutes - one hour.
e.g., “Interface Weekly” - “Platform Weekly” - “Agent Weekly”
e.g., “Frontend Weekly” - “Backend Weekly” - “Agent Weekly”
In some groups, this may be split into smaller discussions related to the different focuses of members within the group.
#### Participants
This would include members of each group.
This would include anyone who wishes to participate.
#### Sample Agenda (MDM)
- What’s good?
- Anything at risk for the release?
- Bug assignment
- Confirm response payload matches spec
- Discuss completion of Redux removal
### Standup
(Optional, varies by group) This is to provide status reports, discover blockers, and keep the group in sync.
If desired, each group can implement daily (or some other cadence) standups. Ultimately, it’s up to the Engineering Manager to make sure that the team is communicating appropriately to deliver results.
#### Participants
This would include any members of the group.
- Discuss common patterns and conventions in the codebase
### Engineering Leadership Weekly (Weekly ~ one hour)
@ -204,9 +191,9 @@ In either case, if the oncall engineer has the knowledge and confidence to revie
#### 3. Customer success meetings
The oncall engineer is asked to attend all the customer success meetings during the week.
The oncall engineer is encouraged to attend some of the customer success meetings during the week. Post a message to the #g-customer-experience Slack channel requesting invitations to upcoming meetings.
The engineer will receive calendar invitations for the appropriate meetings. This has a dual purpose of providing more context for how our customers use Fleet. Also, the engineer should actively participate and provide input where appropriate (if not sure, please ask your manager or organizer of the call).
This has a dual purpose of providing more context for how our customers use Fleet. The engineer should actively participate and provide input where appropriate (if not sure, please ask your manager or organizer of the call).
#### 4. Improve documentation