With the previous team I used to work with, we used to work on the same project at the time. Or at least we used to use the same platform/programming languages. Code review was almost daily routine and established procedure. However, when I joined my new team as a senior developer, there was no code review followed at all. One of things I was asked to introduce to the team, is code review. The problem is, my current team works on different projects, mostly using different platforms and different programming languages. For example, these couple of weeks I'm writing in PL/SQL and doing some ORACLE APEX development. Another team member is developing a mobile App using some hybrid App platform (jQuery, JavaScript, CSS ... etc). A third one is setting up IVR/OVMS system that barely has any code written except for some basic MySQL DB. We rotate usually in future projects, so everybody will get to understand the platforms. But we do not work on the same platform at the same time.I understand this way of distributing work is not really the best (It might be for this company, but I do not think I have the privilege to discuss this, at least not just yet). The problem is, When I assign code review to a team member in a language that he has not touched for couple of weeks (maybe months), it is very hard to comment or make any useful understanding of it. When I spent my whole day writing in Javascript, and at the end of the day I'm asked to review some complex logic in PL/SQL, it is really not an easy task.So my question: Is there any methods followed in similar cases? How can I facilitate the process and make the best use of code review given the team work load?
How to encourage code review with team members working on different projects and platforms
code reviews