Services

I read your codebase and look for what makes changes slow and risky: concepts without a name, decisions spread across the system, responsibilities in the wrong layer, and gaps in the tests.

What you get

A written report with findings ordered by what they cost you, next steps with code examples, and answers to follow-up questions by email.

A good fit when

A system has become hard to change, your team took over code it did not write, or a larger extension is coming up.

I review your team’s pull requests on GitHub or GitLab, with the same eye for structure, naming and tests, so problems are caught before they are merged.

What you get

Review comments directly on the pull request within an agreed number of business days.

A good fit when

Your team wants a second reviewer with architecture experience, or you want to raise the bar for new code while the legacy is being cleaned up.

You send a design document, architecture decision records or a repository. I check boundaries, responsibilities, integration with foreign systems and whether the testing strategy carries the design.

What you get

Written feedback with risks, alternatives and short decision records for the important trade-offs.

A good fit when

You are starting a new product, splitting a monolith, or connecting systems you do not control.

One technical question or decision, with the context that matters. I think it through and write down what I would do and why.

What you get

A written answer within a few business days, including the assumptions it depends on.

A good fit when

You lead a team without a technical peer, or a decision is too important to make alone.