|
|
|
|
|
|
by 21asdffdsa12
1 day ago
|
|
|
If they put effort into the code- they will put effort into guiding the reviewer through it. Like : Here is the ticket, this was the goal.
I set out by beginning here- but encountered problems x y z
I then refactored to accomplish.
Finally.. You just dont drop a blob from orbit. Ironically, ai could generate that quite well from existing documentation (ticket, tasks and prompts) + https://marketplace.visualstudio.com/items?itemName=vsls-con.... |
|
|
Not sure how you are working but we have this novelty idea where people have daily meetings like 15 mins each day to update each other which tasks they are busy with.
We also have refinement meetings where people are involved in clarification for each task so they are not surprised by requirements.
So we do planning meetings every two weeks. Each ticket is tied to the code in commit.
So by code review time anyone doing CR has all of the information in few clicks and some of it already in their head.