Continuous Integration

The continuous integration setup should be used to create a pair programming buddy or a code review buddy. Something that can give you blameless feedback while also allowing you to ask for as much help as you need without feeling self conscious about using other peoples time. This applies from jr developers all the way up. It also provides a better experience for others who are going to review your code as well. I believe changing the way people view ci from some time waste that stops me from releasing and always slows us down. To how do I create the idea blameless code review partner. Well they would be happy to catch simple mistakes quickly and point them out with causes or solutions. They could help me clean and format my work so that I new it looked good. They could help me understand the reach and impact of my changes. They might also help me learn from other similar things people have already done. All of these things could be provided by your ci without having to worry about your reviewer having a bad day, poorly wording a suggestion, being frustrated with the frequency of changes or anything else like that. Just a useful blameless system that makes it fast and easy for you to get the feedback you need to improve and grow in a good direction. This is not to say human code reviews aren’t also very important but a human should add value by doing what human’s do best providing higher level insights and encouragement when needed. Not digging through every change and trying to figure out all the possible problems because this also creates a more hostile environment for conversations. Making it harder to convey improvements or suggestions when the goal seems to be to find flaws. Ideally a person would want to check if the test cases and other verification systems were updated appropriately to see the changes and that the changes were done to produce the outcome of the task.