Software consultancy
Code review
Ship code that is reliable, that performs, and that matches the agreed requirements. The useful review is a second pair of eyes on a tree an internal team has been staring at for too long.
Three stages
Documentation and requirements. We look at whether the system documentation exists, and whether it is good enough to inform the audit.
Automated analysis. Tools give baseline metrics and a visual map of the solution. A language model can draft a finding. The review is still a person reading the code.
A detailed pass. Design patterns, object-oriented practice, internal quality rules, and unit tests — including misuse, not just 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.
Practice
A half-day a week has long been kept for professional development: new code, new languages, tools we might actually ship. Vendor certificates are useful. Years on several teams matter more.