# code reviews Code review is the process of having someone other than the code's author examine a code change to validate its design and implementation and help maintain code quality. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The Case for Hiring Junior Engineers 🌱 DevFeed: [The Case for Hiring Junior Engineers 🌱]() Original publisher: [Read original article]() Author: Luca Rossi Published: 2026-08-12T07:19:52Z Content type: opinion Language: en Sources: [Refactoring]() Topics: [Artificial Intelligence](), [systems](), [code reviews]() Tags: [2026](), [ai](), [code-reviews](), [hiring](), [junior](), [systems]() ### AI overview This opinion argues that companies are making a practical business mistake by freezing junior engineering hiring because of AI. It acknowledges that junior engineers now face earlier demands such as code review, critical thinking, and systems thinking, while arguing that these challenges do not eliminate the value of hiring them. ### Source excerpt Let's flip the narrative that you only need seniors now. ## The growing code review workload and emerging AI-assisted approaches DevFeed: [The growing code review workload and emerging AI-assisted approaches]() Original publisher: [Read original article]() Author: Ivan Klaric Published: 2026-07-23T16:55:29Z Content type: article Language: en Sources: [The Pragmatic Engineer]() Topics: [code reviews](), [ai code review](), [Software Engineering](), [Testing](), [Formal methods](), [GitHub]() Tags: [ai](), [ai-code-review](), [code-review](), [formal-methods](), [software](), [testing]() ### AI overview The article examines the growing code review workload as AI-generated code increases. It surveys dedicated AI review tools, review features in coding platforms, in-house systems, and verification approaches such as testing and formal methods, while noting that few solutions are proven. ### Source excerpt Top of mind for engineering leaders: what to do about the growing code review load, and how devs are starting to review code less thoroughly than before? Many questions, but few proven solutions. ## Agentic code workflows with Nick Tune DevFeed: [Agentic code workflows with Nick Tune]() Original publisher: [Read original article]() Author: Dr Milan Milanović Published: 2026-03-26T16:01:37Z Content type: article Language: en Sources: [Tech World With Milan Newsletter]() Topics: [agentic-coding](), [ai-coding](), [Claude Code](), [Code quality](), [code reviews](), [Test-driven development](), [Testing](), [Command-line interface](), [Domain-driven design (DDD)](), [migration](), [Requirements](), [Continuous Delivery (CD)]() Tags: [agentic](), [agentic-coding](), [agents](), [ai-coding](), [ai-tools](), [best-practices](), [claude-code](), [cli](), [code-quality](), [code-reviews](), [continuous-delivery](), [domain-driven-design](), [migration](), [requirements]() ### AI overview An interview with Nick Tune about advanced agentic coding workflows. It covers planning requirements, modeling development as a tested state machine, implementing features with Claude Code and guardrails, enforcing architecture rules deterministically, reviewing pull requests, applying TDD, and using custom tooling. ### Source excerpt Most engineers who talk about AI productivity talk in abstractions. ## AI Can Accelerate Experienced Engineers but Should Not Replace Junior Developers' Learning Process DevFeed: [AI Can Accelerate Experienced Engineers but Should Not Replace Junior Developers' Learning Process]() Original publisher: [Read original article]() Author: Mike Yerou Published: 2026-02-05T09:59:43Z Content type: opinion Language: en Sources: [Rock and Null]() Topics: [Artificial Intelligence](), [coding](), [code reviews]() Tags: [ai](), [ai-tools](), [artificial-intelligence](), [code-reviews](), [coding](), [productivity](), [software-engineering](), [thoughts]() ### AI overview The article argues that AI tools can help experienced engineers work faster but may allow junior engineers to bypass the struggle, debugging, code reviews, and design discussions that build deep understanding. It recommends intentional training and allowing juniors to develop intuition before relying heavily on AI. ### Source excerpt Junior engineers can get instant answers and working code, but risk skipping the hard-earned understanding that comes from struggle. AI is a powerful multiplier for experienced engineers, but without intentional training, it can quietly erode how the next generation is built. ## How to give outstanding code reviews (if you have to) DevFeed: [How to give outstanding code reviews (if you have to)]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2024-07-20T05:00:00Z Content type: tutorial Language: en Sources: [Tobias Mende]() Topics: [code reviews](), [Programming](), [pull-requests]() Tags: [asynchronous](), [code](), [code-reviews](), [collaboration](), [developer-experience-developer-productivity-quality-software-development-software-testing-engin](), [how-to](), [knowledge-sharing](), [programming](), [software]() ### AI overview This article explains the author's approach to code reviews. It favors pair or team programming for immediate feedback, while presenting asynchronous code reviews as a fallback when pairing is not possible. It discusses slower feedback, less effective written communication, reduced knowledge sharing, and weaker collaboration as drawbacks of asynchronous reviews. ### Source excerpt How to give outstanding code reviews (if you have to) Most software companies use code reviews to ensure that at least two people check each part of the code base and maintain its quality. Although I prefer pair or team programming over asynchronous code reviews, I recognize that this isn't always possible. In such cases, asynchronous code reviews are the next best option. ## How to become a Trusted Contributor, part 2 DevFeed: [How to become a Trusted Contributor, part 2]() Original publisher: [Read original article]() Published: 2024-01-28T00:00:00Z Content type: article Language: en Sources: [postmarketOS Blog]() Topics: [foss](), [code reviews](), [patches](), [Accessibility]() Tags: [accessibility](), [code-reviews](), [community](), [contributions](), [contributors](), [developer](), [email](), [foss](), [how-to](), [postmarketos](), [support]() ### AI overview This post explains how contributors to postmarketOS can qualify to become Trusted Contributors through sustained contributions beyond code, including accessibility improvements, community support, artwork, writing, and podcast editing. It also outlines the application process, which involves a confidential issue, team endorsements, and a list of contributions. ### Source excerpt After our How to become a Trusted Contributor blog post was received with great enthusiasm by the community (and already have two new TCs since, shout out to @travmurav and @f_), we thought that it would be a great idea to expand its scope. We know that people have been contributing to postmarketOS in many ways, not just via code reviews and submitting patches. So if you have been contributing to postmarketOS for the past six months or longer and don't fancy yourself a developer, there is now a path for you to become a Trusted Contributor too! Some examples of what types of contributions can qualify you as a Trusted Contributor include: making accessibility improvements supporting others in our chat rooms supporting others in our issue trackers creating artwork or other promotional materials writing blog posts for postmarketOS.org (the main and/or "edge" blogs) podcast / audio editing If you're curious how to get started with any of those things today, in hopes of applying to be a TC later, please do not hesitate to reach out to us in chat! If you find other tasks that we didn't think of, which would also have a good impact on the project or our community, feel free to reach out as well. Trusted Contributors enjoy street cred (public contributions to a large FOSS project can look good on a resume!) and their own @postmarketos.org email address. The process to apply is largely the same as what we detailed previously: file a new confidential issue in our application repo, find existing team members to endorse you, and list out your contributions and achievements to support your application. We also got a bit of behind-the-scenes audio for you in the podcast. That's it, thanks for reading this blog post! ## Static Code Analysers DevFeed: [Static Code Analysers]() Original publisher: [Read original article]() Published: 2024-01-22T00:15:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [detekt](), [Kotlin](), [Programming](), [code reviews](), [compilers]() Tags: [android](), [code-reviews](), [compilers](), [detekt](), [generics](), [java](), [jvm](), [kotlin](), [workshop-learning-programming]() ### AI overview This tutorial introduces static analysis as a way to identify bugs and recurring code patterns without running the code. It explains how static analysers can automate and enforce coding patterns in large Kotlin codebases, then begins a practical walkthrough of detekt, a popular Kotlin static analyser. ### Source excerpt All you need to know about Static Code Analysers and Detekt. ## Imperfect #9 - Why and when to code as a manager DevFeed: [Imperfect #9 - Why and when to code as a manager]() Original publisher: [Read original article]() Author: Pedro Gil Carvalho Published: 2022-10-14T11:30:54Z Content type: opinion Language: en Sources: [Pedro Gil Carvalho]() Topics: [Development](), [coding](), [code reviews]() Tags: [code-reviews](), [coding](), [developers](), [engineering-manager](), [process]() ### AI overview This opinion article explains when engineering managers should code. It advises new managers to focus primarily on people, process, and communication, while identifying bug fixing, proofs of concept, code reviews, and hands-on work in small teams as useful exceptions. Regular coding can create missed deadlines, blocked dependencies, delayed releases, and damaged credibility. ### Source excerpt Keeping our skills sharp without blocking anyone ## Code Ownership: Keeping the balance between structure and agility DevFeed: [Code Ownership: Keeping the balance between structure and agility]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2022-02-12T12:53:00Z Content type: article Language: en Sources: [Tobias Mende]() Topics: [Code](), [modules](), [structure](), [code reviews](), [systems]() Tags: [code](), [code-reviews](), [developers](), [modules](), [ownership](), [practices-software-development-technical-leadership-organizational-design-software-craft](), [scale](), [structure](), [systems](), [teams]() ### AI overview The article explains strong, weak, and collective code ownership. It argues that team ownership reduces dependence on individual developers, while knowledge sharing through collaborative editing and code reviews helps teams maintain responsibility for modules. It also notes that collective ownership becomes harder to sustain as systems and teams grow. ### Source excerpt Code Ownership: Keeping the balance between structure and agility Code ownership is an important topic when it comes to enabling your teams and allowing developers to improve the system while keeping the overhead of changes low. ## The value of a thousand little features DevFeed: [The value of a thousand little features]() Original publisher: [Read original article]() Published: 2017-04-13T00:00:00Z Content type: opinion Language: en Sources: [Robin Ward]() Topics: [Software Engineering](), [Development](), [Rails](), [Ember](), [JavaScript](), [Ruby](), [Database](), [code reviews](), [test-coverage]() Tags: [code-reviews](), [coverage](), [database](), [development](), [ember](), [javascript](), [rails](), [ruby](), [software-engineering]() ### AI overview The author reflects on five years of Discourse development, describing how the team settled on major technical choices such as Rails, ActiveRecord, Postgres, Ember.js, and JavaScript. The article also discusses codebase practices, performance improvements, and planned changes including TypeScript, replacing Sprockets, and upgrading Ruby and Rails. ### Source excerpt It's been over a year since I wrote a blog entry! And while of course the universal excuse of "I've been busy" applies, I think we reached a point in Discourse's development where we just were able to focus on the product without a lot of stuff getting in our way. I've now been working on Discourse full time for 5 years. In the beginning we had a lot more uncertainty about technical decisions. Some of the things we debated interally include: ## How Students and New Developers Can Build Skills Through Open Source DevFeed: [How Students and New Developers Can Build Skills Through Open Source]() Original publisher: [Read original article]() Published: 2015-08-31T00:00:00Z Content type: opinion Language: en Sources: [Radek Pazdera]() Topics: [Open Source](), [Programming](), [Git](), [Maintainers](), [code reviews](), [Documentation]() Tags: [beginner](), [career](), [code-reviews](), [collaboration](), [contributors](), [developers](), [git](), [learning](), [open-source](), [portfolio](), [students]() ### AI overview This opinion article argues that students, career switchers, and other newcomers can use open source projects to practice software development and build portfolios. It recommends starting with manageable tasks such as fixing issues, refactoring functions, and addressing TODOs while learning teamwork, Git, code review, and unfamiliar codebases. It also encourages maintainers to make projects more welcoming to beginners. ### Source excerpt I build software products and write on the Internet.