Had this happened:
A developer make a new feature, but not working, since last year, total code change is 100+files and 10k lines.
Until recently, with help of another developer, get it to work.
Now the code review is huge to include all changes.
Seems there is a common sense that unfinished incomplete change shouldn't be sent for code review. So how to deal with this situation?
The answer here is fairly simple: don't get yourself into this situation in the first place. I don't care that it's an "independent module", you should still have split it up into chunks which were individually reviewable in the first place. Obviously I don't know what domain this is, but you're still going to have something like data access bits, business logic bits, UI bits and some utility code as well. Write each individual chunk separately and get it reviewed separately.
