6 ms·
Our teams efforts have shifted toward reviewing plans as a team. Before code hits a humans eyes it's went through a few independant review passes from our revi
by bnchrch 4mo ago
Our teams efforts have shifted toward reviewing plans as a team.
Before code hits a humans eyes it's went through a few independant review passes from our review agents.
If it's low complexity / blast radius it gets auto merged.
If it's high complexity / blast radius it gets flagged for human review.
And funny enough our team has agreed even our human review layer has the best results if we have an agent create supplementary descriptions of the code and potential issues that we read and apply human judgement.
Reason being is that it can be very pendantic. Both in a good and bad way. Either flagging things that are non-concerns, or catching things my lazy human eye wouldnt have caught. e.g. A docstring mis-describing the actual shape of an object.
- maxalbarello 4mo agointeresting! how do you review each other's plans? do you just copy-paste them into chat or something else?