OpenGrok review - why and how to use it in a large team
When working in large software companies, it is common that you end up working at some point for a large project with a business logic history that is never well documented. You find it hard to know what features are available in the existing project, which component triggers a specific behavior or if the system processes some specific information you need to learn more about. This is particularly frustrating in migration projects from an old platform to a new one, especial when the initial engineers are no longer with the company or have reduced their number. While this is not a very big issue for developers given the codebase is usually their documentation, it might be an issue for business analysts or other functions who do not have the habit to browse through the codebase using professional tools. Luckily nowadays there are a lot of source code web browsers, that offer the search capability in a web interface for references in the codebase. The source code...