--- title: How We Review // nipafx | daily.dev description: A detailed look at how a 15-20 person Java development team implemented a code review process. Key elements include a monthly rotating 'code buddy' system for... canonical: https://daily.dev/posts/how-we-review-nipafx-gncw3kt0d twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: How We Review // nipafx | daily.dev og:description: A detailed look at how a 15-20 person Java development team implemented a code review process. Key elements include a monthly rotating 'code buddy' system for... og:url: https://daily.dev/posts/how-we-review-nipafx-gncw3kt0d og:image: https://api.daily.dev/og/posts/GNCw3Kt0D.png og:image:alt: How We Review // nipafx og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # How We Review // nipafx **[nipafx \(Nicolai Parlog\)](https://daily.dev/sources/nipafx)** · 7 min read · 0 upvotes · 0 comments ## Summary A detailed look at how a 15-20 person Java development team implemented a code review process. Key elements include a monthly rotating 'code buddy' system for peer review assignments, a backlog management strategy for unavailable reviewers, and use of Atlassian Crucible as the review tool. The post covers Crucible's limitations (no custom fields, no open discussion tracking) and the workarounds adopted, such as misusing the 'defect' marker to track unresolved comments. The full review workflow is outlined step by step, from creating a review in Crucible through to closing it once all defects are resolved. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Similar posts on daily.dev - [Reviewing large changes with Jujutsu](https://daily.dev/posts/reviewing-large-changes-with-jujutsu-ocxv3pmjs) · Lobsters · 2 upvotes · 1 comments --- Tags: [#java](https://daily.dev/tags/java), [#code-review](https://daily.dev/tags/code-review) [View this post on daily.dev](https://daily.dev/posts/how-we-review-nipafx-gncw3kt0d) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"How We Review // nipafx","url":"https://daily.dev/posts/how-we-review-nipafx-gncw3kt0d","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/how-we-review-nipafx-gncw3kt0d"},"datePublished":"2026-03-16T08:13:51.035Z","dateModified":"2026-03-16T08:26:06.394Z","description":"A detailed look at how a 15-20 person Java development team implemented a code review process. Key elements include a monthly rotating 'code buddy' system for...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/802757805a011a13a0f39f277248f48c?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/802757805a011a13a0f39f277248f48c?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"nipafx (Nicolai Parlog)","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"nipafx (Nicolai Parlog)","logo":"https://media.daily.dev/image/upload/s--H_Echo_u--/f_auto,q_auto/v1773648772/logos/nipafx?_a=BAMAMiiu0","url":"https://daily.dev/sources/nipafx"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/how-we-review-nipafx-gncw3kt0d","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"java,code-review","timeRequired":"PT7M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"nipafx (Nicolai Parlog)","item":"https://daily.dev/sources/nipafx"},{"@type":"ListItem","position":3,"name":"How We Review // nipafx"}]} ```