Good writing. However, I don't consider pull requests a good code review flow for development teams (they are great for the open-source community though). Way too much friction. There are better in-IDE options like CodeStream (disclaimer: I work there), just to name one.
Thanks! :) I think well organized merge reviews are working for both open and closed communities. For example, I was working for multiple companies from 10 to 200 people, using github, gitlabs and bitbucket with their similar core review flows.
It was working without any overhead.
However, I can see the value in tools like CodeStream, if they are properly integrated in workflows. Problem with new tools is that architects and stakeholders tend to just "slap them on existing infrastructure" without taking extra effort to integrate it properly and make transition process good.
In short, my take on that paying for new tool is the easiest part, making proper use of it is what requires skill, will and something else that was rimming with will, skill, but I forgot what it was.. :D
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Good writing. However, I don't consider pull requests a good code review flow for development teams (they are great for the open-source community though). Way too much friction. There are better in-IDE options like CodeStream (disclaimer: I work there), just to name one.
Thanks! :) I think well organized merge reviews are working for both open and closed communities. For example, I was working for multiple companies from 10 to 200 people, using github, gitlabs and bitbucket with their similar core review flows.
It was working without any overhead.
However, I can see the value in tools like CodeStream, if they are properly integrated in workflows. Problem with new tools is that architects and stakeholders tend to just "slap them on existing infrastructure" without taking extra effort to integrate it properly and make transition process good.
In short, my take on that paying for new tool is the easiest part, making proper use of it is what requires skill, will and something else that was rimming with will, skill, but I forgot what it was.. :D