Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
This tag is for questions about the practice of code review and code walkthroughs. For reviews of existing, working code, please see http://codereview.stackexchange.com
3
votes
How can I tactfully suggest improvements to others' badly designed code during review?
Code reviews aren't always aimed at making improvements.
A review near the end of a project as seems to be the case here is just so that everyone knows where to start looking when bugs come in (or fo …
4
votes
What quality level in the commit history can/should I expect/enforce?
It is generally easiest to avoid editing the history - It can be done even in a team environment, but it requires a lot of work for little benefit and introduces a risk of data loss.
You will have s …