How it works
The process is simple. We start with a briefing to establish a common understanding of the objective, to determine the environment and context affecting the scenario, and to estimate the probability of substantial input.
We prefer to work on cases that involve the following technologies because low-level issues are what we're passionate about:
aarch64
assembly
c++
c
java
linux
posix
unix
win32
windows
x86_64
In case you're still unsure about the kind of scenarios we're working on, read an actual review report or contact us
If both of us are ready to commit, we agree on a timebox for the review effort (4 hours initially). If desired, a non-disclosure agreement (NDA) can be used to protect intellectual property and internal data. Access to the scenario with the least possible privileges must be provided.
The actual spot code review is done by processing and reviewing the provided input and code and building/testing modified versions (if required). A feedback loop is used to communicate progress, preliminary suggestions and to request further information.
The code review leads to a detailed report that outlines the scenario, analysis, and detailed recommendations to meet the initially presented objectives.
As part of a report review, we jointly decide if we're done or another timebox is required.