ReviewNinja
Code Review
Hound
Hound comments on style violations in GitHub pull requests, allowing you and your team to better review and maintain a clean codebase.
Code review guidelines - CodeProject
Code review is systematic examination (often known as peer review) of computer source code. It is in...
The risks of feature branches and pre-merge code review - The Pug Automatic
Our team has been doing only spontaneous code review for a good while – on commits in the master bra...
Code Review - The Ultimate Guide
1 What is code review and why is it important? We all know how nice it is when we're dealing with cl...
An Intro to CSS Testing with SonarQube | CSS-Tricks
The following is a guest post by David Racodon. David contributes to this open source code quality t...
Sass Guidelines
My name is Hugo Giraudel, I am a 23 year-old French front-end developer, based in Berlin (Germany) s...
CSS performance revisited: selectors, bloat and expensive styles - Ben Frain
444Days 444 days since this post was last revised. Specific details are likely out of date. What is ...
Improving Smashing Magazine's Performance: A Case Study
Practical insights and lessons learned from performance challenges on Smashing Magazine. The result:...
Day in the life of an ALM Developer: Suspend work, fix a bug, and conduct a code review
Visual Studio 2015 A powerful one-click way to switch your working context from one thread of work t...
GitHub Code Reviews
Our Crew explains its Development Workflow. In part 2 we talk about the steps necessary to get your ...
92bondstreet/code-review-front-end
code-review-front-end - Code Review Checklist for Front-End Developers