From 82348ddc7caec627516040fd8136df1eaadd0217 Mon Sep 17 00:00:00 2001 From: Brad Treloar Date: Sat, 30 Aug 2025 23:50:21 +0930 Subject: [PATCH] Add engineering process notes --- docs/programming/general/working-on-a-team.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/programming/general/working-on-a-team.md b/docs/programming/general/working-on-a-team.md index d1d6716..b9ae5e6 100644 --- a/docs/programming/general/working-on-a-team.md +++ b/docs/programming/general/working-on-a-team.md @@ -9,3 +9,14 @@ are both. Good documentation (comments, readmes, pull-requests) makes everyone's job easier. + +If you don't trust a dev's knowledge or decision-making then put guardrails on +their work. Give detailed instructions about how the feature should work in the +ticket, and check their work against these requirements when reviewing their +work. + +A team is only as good as its processes. Engineering processes such as code +style rules, code review, version control, testing, release planning etc. all +provide quality control. Without these controls, devs will perform at the level +they find personally acceptable, which may be below the standard the team needs +to succeed.