Viewing profile — martinvanaken

Hi Sheff, I'm Martin, co-founder of PullReview. I'm interested in understanding why the SaaS is not a good solution for you. Is it because you are not using GitHub (or any other on…

+1 to that one. Code Review should be Peer Review - it is not about a Senior reviewing a Junior it is about a developer reviewing the work of another one. The junior's questions ma…

Thanks, nice list, summarize a good part of the best practices in a short form. Will quote.

Hi, author here. I agree this may not be easy - but something can always be done. I've been in several situation. As a team leader facing junior developers, I did simply set-up rul…

Great list (especially "off the top of your head"). Thanks a lot for sharing. Several of those can actually be implemented in an automated tool (styles, short variables, spacing, u…

I agree with you, and this is the reason why having small features and reviews for all of them helps. Groking a colleague's code is much simple if it is a small piece, and when you…

Its the whole point for me: even if I prefer managers that I can convince, I just call that "development". Replace: "feature is done but need to be tested or reviewed" by "feature …

Hi, OP here. Interesting list. I think I would approve most of your points, but never worked (or created) such a "proper" environments in my various teams. Could you share the kind…

This one should be recorded on http://www.codingconfessional.com/

Hi, I think both are actually useful. The CI is supposed to run the tests (even if I like to run some myself when reviewing), but I agree that starting the application is a part of…