Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

8
  • 4
    Appears or is? A quick measurement of the source files will confirm or deny your suspicions. After measuring just bring up the measurement numbers at the code review and suggest a refactoring to bring down the complexity numbers. Commented Dec 15, 2016 at 16:51
  • 4
    related: How can I tactfully suggest improvements to others' badly designed code during review? Commented Dec 15, 2016 at 17:06
  • 6
    Possible duplicate of What do you do when code review is just too hard? Commented Dec 15, 2016 at 18:49
  • 5
    Please define "too complicated". Is the code too complicated because it uses well known design patterns that are simply unfamiliar to your team, or because it fails to use patterns well known to your team? The precise reasons for judging the code "too complicated" are essential to creating a correct assessment of how to go forward. A statement as simple as "too complicated" on a knowledge area as deep and complicated as code review suggests a witch hunt of the developer to me. Commented Dec 16, 2016 at 20:18
  • 7
    @PieterGeerkens Or, perhaps, is it too complicated because it's solving a complicated problem? Commented Dec 16, 2016 at 22:07