Code reviews help to get information from the eagles view or the outsite perspective. It can help to find weaknesses in architecture, design or code and can help to improve the quality with the well-known four eyes principle.

Our mothers like to remind us in childhood not to run too fast in dangerous situations due to our leak of attention to our environment like car traffic, dangerous cliffs or slippery ground. They also like us to remind to pay attention to the current situation and not to dream the whole day, otherwise we could miss the important or interesting things in life ...

Also here we can apply the same principles to software development. From time to time, especially in turbulent and difficult times, we need to step back or lean back for some time to apply the three basic steps for right actions:

  1. Observe
  2. Understand
  3. Act

Within these three steps we have a close look to the current situation (oberservation) and analyse the situation in detail. Aftwards, we can judge whether or not our pre-assumptions are still valid, the environmental conditions are still the same and the specifications and needs are unchanged (understanding). Based on these judgements we can act accordingly to get the best out of the current situations.

This procedure is always needed in turbulent times if the possibility is given to loose control of the whole process or to run blindly into the wrong direction. During such times it is crucial (and the hardest thing to do) to apply the steps mentioned above to come back onto the safe path.

External code reviews can help to identify the weak points in your system due to the ability for a reviewer to ask questions without any pre-assumtations. Everything is questioned freely and openly and the answers given show very well the current situation. In-depth reviews help later on to identify potentials for better performance, usability or reliability. External professionals have an independent view on projects of others.

We can help you in doing code reviews for you. With asking questions we help you to judge your current situation and with looking into the architecture, the design and into the code itself, we help you to identify weak point of performance, stability and safety.