What are code reviews? Hopefully most of my readers whom are programmers are working in an environment where code reviews are part of the software development process. For those readers who have no idea what those are: code reviews are self-explainatory, it’s a process of reviewing changes (code) submitted by one member by other members working on the same project. Mind you - such reviews were not so popular just a few years back but benefits of including them in software development pipeline made them adapted widely anywhere from open source communities to business teams.

1. What’s CI CI stand for continous integration. The simplest way I could explain what it really is is with an example. Say, you remember when you started your first coding related job, or maybe the second. Hopefully the company/environment provided you with opportunity to review code throughout the team. If so you may have noticed that often it is not the solution itself that takes the most time but the actual codereviews, discussions and merging that is the problem.

Wait, what? Yeah, your goalkeeper. Surprised? If you are a developer there’s a great chance that you are underestimating the role of QA in development process. The less experience you have the more the chance is. But hey, that’s natural you know. You will grow to love them on your first major, ekhm, bug on production. Bugs on production never happen to me! Maybe, or perhaps you just ignore the pingpong you usually play with your QA tester.