I am a cloud application architect with 10 years' experience in software development in several languages, including Perl, Java and C#. I'm an Irishman living in Calgary, Canada. GitHub on @cubikca.
Location
Calgary, Canada
Education
BSc. Computing and Info Systems, Athabasca University
I can see this working where developers are widely spread across multiple teams and for some reason you need someone on another team to review your code. I find that a daily build is an effective strategy, where a dedicated reviewer spends an hour or two each day reviewing the PRs from the previous day. This allows for a predictable schedule.
Admittedly, if something is escalated to senior management or executive, we'll have to promote the PR. But in this case we have executive/senior management support to ensure the PR is addressed immediately.
The idea of CR after the fact is interesting. I'm not sure how audit would feel about changes predating their review though.
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.
I can see this working where developers are widely spread across multiple teams and for some reason you need someone on another team to review your code. I find that a daily build is an effective strategy, where a dedicated reviewer spends an hour or two each day reviewing the PRs from the previous day. This allows for a predictable schedule.
Admittedly, if something is escalated to senior management or executive, we'll have to promote the PR. But in this case we have executive/senior management support to ensure the PR is addressed immediately.
The idea of CR after the fact is interesting. I'm not sure how audit would feel about changes predating their review though.