We offer a code-review service aimed at program code written in C. Although code review is often specified in company quality procedures, it often does not play its intended role. Amongst the reasons for this are:
- It is usually done too late in the coding cycle, after the code has been tested and is nominally finished. At this stage, so much has been invested that changes as a result of a critical code review are unwise;
- It is often done half-heartedly, just as a box-ticking exercise;
- There are no agreed standards against which the code is reviewed, even though there is probably a company coding standard kicking around somewhere;
- There is no agreed coding style, each programmer having different, sometimes bizarre, preferences;
- Critical comments can be taken personally, causing friction within a team.
In our opinion, code should be reviewed during the design process before significant testing is performed. Reviews should be conducted independently of the project team. If the quality department does not have the resources to execute this function it can be outsourced - to us, for example.
To discuss how we can help you, please contact us. For an example of our code, please browse through the string library and UDP hole punching client/server