Software consultancy

Code review

A team that has stared at the same tree for two years stops seeing it. A second pair of eyes finds what familiarity hides, and gives you code that is reliable, performs, and matches the requirements everyone agreed to.

Three stages

  1. Documentation and requirements come first. We look at whether the system documentation exists, and whether it is good enough to inform the audit.
  2. Automated analysis comes next. Tools give baseline metrics and a visual map of the solution, and a language model can draft a finding, but the review itself is still a person reading the code.
  3. Then the detailed pass: design patterns, object-oriented practice, internal quality rules, and unit tests, checked for misuse as well as for presence.

Languages

Code audit work is offered in Visual Basic.NET and C#. Where the stack is one we do not live in every day, we work with technology partners we appoint. All of our own code is reviewed the same way.

Practice

A half-day a week has long been kept for professional development: new code, new languages, and tools we might actually ship. Vendor certificates are useful, and years on several teams matter more.