Here are three practices that I found to be of a great help in my day-to-day work as software development manager.
Inspection is your friend
It’s crucial to know how your code source health is.
Complex code tend to have a high maintenance cost and makes entry cost higher for a newcomer. Failing to apply best practices and recommendations can result in various bugs. A poor test coverage makes future development very likely to introduce regressions.
Static and dynamic analysis are you best friends to give you accurate indicators about your code health. They also help you take appropriate actions to cure the spotted deficiencies.
If you don’t have this yet in place, all it takes is these simple steps:
1. Start by setting up a continuous code analysis process for your source code
2. Define a quality profile and break the build whenever the quality gateway is violated
3. Every time an issue is fixed, adjust the quality gate accordingly
Static and dynamic code analysis can help you track the source code health but when it comes to technical design they are rather limited.
When software development manager drifts away from the code because of other duties that require his attention, code review can be a good help.
By reviewing the changes regularly the software development manager can stay up to date with the design changes and can intervene at an early stage if needed. How to do it? By a continuous automated code review generation process:
1. Automatically create a code review for each new change
2. Keep the pace, perform the review regularly
Get your hands dirty
Quite often the software development manager doesn’t have room anymore for coding. Unfortunately this can make him unaware of the coding conditions, pain-points and other important factors. If the team fail to give him a comprehensive feedback this can result in negative outcomes.
My suggestion, make room to code. Besides giving you an accurate idea of the work conditions of your team, you’ll enjoy performing what initially made you want this job.