--- title: How To REALLY Do Code Reviews | daily.dev description: Code reviews exist on a spectrum from extremely strict (Linux kernel style) to laissez-faire, and the right approach depends on multiple variables: the... canonical: https://daily.dev/posts/how-to-really-do-code-reviews-ghl6kzqxt twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: How To REALLY Do Code Reviews | daily.dev og:description: Code reviews exist on a spectrum from extremely strict (Linux kernel style) to laissez-faire, and the right approach depends on multiple variables: the... og:url: https://daily.dev/posts/how-to-really-do-code-reviews-ghl6kzqxt og:image: https://api.daily.dev/og/posts/ghl6KzqXt.png og:image:alt: How To REALLY Do Code Reviews 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 To REALLY Do Code Reviews **[Marco Codes](https://daily.dev/sources/marco-codes)** · 23 min read · 0 upvotes · 0 comments ## Summary Code reviews exist on a spectrum from extremely strict (Linux kernel style) to laissez-faire, and the right approach depends on multiple variables: the experience levels of reviewer and reviewee, ego management, project type (open source vs. commercial), team location, and available time. Using a real GitHub pull request for a Google Photos clone as an example, three approaches to code review are demonstrated: high-level nudging comments for senior developers, detailed specific feedback for junior contributors, and outright rejection with explanation for personal projects. The core takeaway is that there is no single correct way to do code reviews — context determines everything. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Similar posts on daily.dev - [Lessons Learned From Code Review Remarks](https://daily.dev/posts/lessons-learned-from-code-review-remarks-vsgqh5vpk) · Software Testing Magazine · 0 upvotes · 0 comments - [Mistakes I see engineers making in their code reviews](https://daily.dev/posts/mistakes-i-see-engineers-making-in-their-code-reviews-uvlezwfro) · Lobsters · 2 upvotes · 0 comments --- Tags: [#java](https://daily.dev/tags/java), [#leadership](https://daily.dev/tags/leadership), [#code-review](https://daily.dev/tags/code-review) [View this post on daily.dev](https://daily.dev/posts/how-to-really-do-code-reviews-ghl6kzqxt) ```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 To REALLY Do Code Reviews","url":"https://daily.dev/posts/how-to-really-do-code-reviews-ghl6kzqxt","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/how-to-really-do-code-reviews-ghl6kzqxt"},"datePublished":"2026-03-16T08:08:49.626Z","dateModified":"2026-03-16T08:09:48.798Z","description":"Code reviews exist on a spectrum from extremely strict (Linux kernel style) to laissez-faire, and the right approach depends on multiple variables: the...","image":"https://i.ytimg.com/vi/DYamyCSDtew/sddefault.jpg","thumbnailUrl":"https://i.ytimg.com/vi/DYamyCSDtew/sddefault.jpg","isAccessibleForFree":true,"articleSection":"Marco Codes","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":"Marco Codes","logo":"https://media.daily.dev/image/upload/s--MFM0XEYf--/f_auto,q_auto/v1773596415/logos/marco-codes?_a=BAMAMiiu0","url":"https://daily.dev/sources/marco-codes"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/how-to-really-do-code-reviews-ghl6kzqxt","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"java,leadership,code-review","timeRequired":"PT23M","video":{"@type":"VideoObject","name":"How To REALLY Do Code Reviews","description":"Code reviews exist on a spectrum from extremely strict (Linux kernel style) to laissez-faire, and the right approach depends on multiple variables: the...","thumbnailUrl":"https://i.ytimg.com/vi/DYamyCSDtew/sddefault.jpg","uploadDate":"2026-03-16T08:08:49.626Z","duration":"PT23M","url":"https://api.daily.dev/r/ghl6KzqXt","embedUrl":"https://www.youtube.com/embed/DYamyCSDtew"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Marco Codes","item":"https://daily.dev/sources/marco-codes"},{"@type":"ListItem","position":3,"name":"How To REALLY Do Code Reviews"}]} ```