I will provide a thorough review of your codebase and point out all areas it could be improved in. That includes already present bugs, but extends to all sources of potential bugs or inefficiencies, both algorithmic and in language specific implementation details.

I will evaluate the overall architecture and provide comments and concrete suggestions for how to improve it.

When encountering bad practices, I will not only tell you they are bad, but explain why, detail what problems they cause in the long run and what should be done instead.

As code is not only meant for compilers, interpreters and other programs to process, but for humans - who might have to extend and maintain it - to read, the contents of my review will also never be purely technical. Style matters. Good style fosters elegant, correct and efficient code. Bad style facilitates errors. I want to ensure your code expresses your intent as clearly as possible, which is why I take special care to mention everything that might inhibit such clarity.

In our interactive sessions, you can walk me through your thought process and we can identify flaws in your reasoning or issues you might have overlooked.