I believe the problem is the PR itself is too large and trying to do too many things. For example it might be trying to solve one problem, but along the way, some formatting changes happen, new comments which are missing but could be useful are added and other objectives.
When PRs are made as small as possible and not lumps of many things they become far easier to understand and theres less chatter and questions.
With the example of that message could be improved that should be a new and different PR.
I would suggest that the task be broken up into multiple parts that can be completed independently.
realizing there are a few usecases:
- Clients adding comments, change requests, etc
- Testing team adding comments, documenting defects, etc
- dev team needing specific repro steps (video), or screenshot of what exactly is being reffered to
Really nice thing about the usecases is it heavily heavily saves time in all three sides: client, tester, dev.
- Client side, as I realize something needs to change i can make a little note in the ui so i can come back and discuss further with a BA.
- Tester side, its great because it auto screenshots the selected component, also it lets me screen-record so i can repro an issue and automatically attach it to this.
- On the dev side, its absolutely amazing because I need context, if there is no images/videos and a half-assed description i cant do anything with it, much worse my agent cant do anything with it, this tool is kinda killing 3 birds with one stone
this is a universal communication problem i think a lot of companies face, which is the classic telephone game problem-
there is a line of people, first person in the line whispers a message to the one behind, and eventually by the time we get to the last person, the message is completely different from what the first person started with
this, if we look at what the client wants for their product, that information traveling to a BA, then a PM, then the dev team, you can already tell information is lost along the way, and the bigger the company the worse it gets, especially remote/offshore teams, and i think with tools like this, that gap gets smaller and smaller
I believe the problem is the PR itself is too large and trying to do too many things. For example it might be trying to solve one problem, but along the way, some formatting changes happen, new comments which are missing but could be useful are added and other objectives.
When PRs are made as small as possible and not lumps of many things they become far easier to understand and theres less chatter and questions.
With the example of that message could be improved that should be a new and different PR.
I would suggest that the task be broken up into multiple parts that can be completed independently.
I built a comment tool!
realizing there are a few usecases: - Clients adding comments, change requests, etc - Testing team adding comments, documenting defects, etc - dev team needing specific repro steps (video), or screenshot of what exactly is being reffered to
Really nice thing about the usecases is it heavily heavily saves time in all three sides: client, tester, dev.
- Client side, as I realize something needs to change i can make a little note in the ui so i can come back and discuss further with a BA.
- Tester side, its great because it auto screenshots the selected component, also it lets me screen-record so i can repro an issue and automatically attach it to this.
- On the dev side, its absolutely amazing because I need context, if there is no images/videos and a half-assed description i cant do anything with it, much worse my agent cant do anything with it, this tool is kinda killing 3 birds with one stone
this is a universal communication problem i think a lot of companies face, which is the classic telephone game problem-
there is a line of people, first person in the line whispers a message to the one behind, and eventually by the time we get to the last person, the message is completely different from what the first person started with
this, if we look at what the client wants for their product, that information traveling to a BA, then a PM, then the dev team, you can already tell information is lost along the way, and the bigger the company the worse it gets, especially remote/offshore teams, and i think with tools like this, that gap gets smaller and smaller