August 8, 2018 at 9:18 am
In our environment, historically, we have been "One-Person Shops" where everyone builds their own application front ends and databases. Over the last 6-12 months, we have been growing having collaborations between Application Developers, Database Developers, and DBAs doing code reviews.
Currently, we have App and DB developers create the product, User Acceptance Testing, submit code for DBA code review. Once the code is reviewed, any final changes are made and testing is done again.
Is this standard workflow and best practices? Or can someone recommend a better workflow as it seems cumbersome to have code reviews after user acceptance.
How does your business handle application deployments?
August 8, 2018 at 1:21 pm
rjjh78 - Wednesday, August 8, 2018 9:18 AMIn our environment, historically, we have been "One-Person Shops" where everyone builds their own application front ends and databases. Over the last 6-12 months, we have been growing having collaborations between Application Developers, Database Developers, and DBAs doing code reviews.Currently, we have App and DB developers create the product, User Acceptance Testing, submit code for DBA code review. Once the code is reviewed, any final changes are made and testing is done again.
Is this standard workflow and best practices? Or can someone recommend a better workflow as it seems cumbersome to have code reviews after user acceptance.
How does your business handle application deployments?
You are definitely going in the right direction. The flow can depend on the number of environments. In general, I've usually seen it where the code review is done before it moves out of development. And then changes from the code review are worked on in development. So it sits there until it passes code review and then goes up to the next level, environment.
Sue
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply