63 Stories To Learn About Code Review

Let's learn about Code Review via these 63 free stories. They are ordered by most time reading created on HackerNoon. Visit the /Learn Repo to find the most read stories about any technology.

1. Why You Should Automate Your Code Review

It's 2020 and there are plenty of tools to help you develop better code. The emergence of DevOps tools and the rise of Artificial Intelligence open up opportunities to automate many aspects of the code review process. In this article, we explain why you should automate your code reviews (even if you develop solo), what are the limitations of these tools and what comes ahead!

2. 10 Expert Tips for Improving Code Reviews: A Guide for Developers

Code reviews are an essential part of the software development process. In this article, we'll discuss 10 best practices for conducting effective code reviews,

3. Code like You're Building a Lego Castle

The article compares coding to building a castle with Legos and emphasizes the importance of following best practices to avoid mistakes and build a sturdy code.

4. How Different Tools Enable a More Inclusive Language In Software Development World

Are terminologies meaningful in software development? Yes, a lot! As developers, we’re continually writing code, and we do that by passing messages. Each message carries a lot of context and semantics. Therefore we’re always evolving how to do it in a better way.

5. Here’s a Proof-Of-Concept for CVE-2022–32511 to Gain Remote Code Execution

Proof-of-Concept for understanding and exploiting CVE-2022–32511 to gain Remote Code Execution.

6. Tips for Writing Good Commit Messages

In this article, I’d like to share my opinion on how to write good commit messages that would make your git log useful and improve your code review process.

7. Code Reviews: A Practice That Depends on Culture

It would be way easier for managers if they could only draw a flow chart explaining how code review works. The manager then would email all the peers, telling everyone should follow the new process.

8. Softagram - Making Code Reviews Humane

The story of Softagram is a long one and has many twists. Everything started in a small company long time ago, from the area of static analysis tools development. After many phases, Softagram is focusing on helping developers to get visual feedback on the code change: how is the software design evolving in the pull request under review.

9. For secure code, maintainability matters

Author Robert Collier said that "Success is the sum of small efforts repeated day in and day out." That's especially true when it comes to security.

10. Best Practice For Code Reviews In Engineering Teams

Code review is one of the most important practices engineers should have. Learn what we think are the most important principles in good code reviews.

11. What to do When You're Tired of Slow Code Reviews

An ex-tech lead's guide to create a healthy code review culture that helps you ship your code faster.

12. 6 Ways to Make Pull Requests More Reviewable

After more than a year of helping developers review code, I try to summarize easy and quick takeaways for a better pull request design.

13. The Comprehensive Code Review Checklist

A code review is a helpful tool for teams to improve code quality. Yet, there are many other benefits to reviewing code.

14. What is Code Review and How To Do It Right?

Why do you really need a code review and how to do it right?

15. Do not Troll Your Teammates: 5 Key Rules for Reviewing Code

Code review is an essential step needed for effective software development.

16. Detecting Linked List Cycle. (LeetCode)

Given head, the head of a linked list, determine if the linked list has a cycle in it.

17. How to Set Up a Team's Systems and Culture for Strong Code Reviews

All software companies must take an intentional and structured approach to code reviews. Here are some tips on how to do that.

18. 7 Best Practices for Speeding Up Code Reviews

Code reviews can be painful. But, there are plenty of ways we can make the process a better experience for both the code author and the code reviewer.

19. A Guide to Examining & Modifying Executable Code

A review of tools and techniques to examine and modify executable.

20. 5 Tools That Will Help You Improve Code Reviews on GitHub

In this article, we’ll consider five tools and integrations that can significantly improve your code review experience on GitHub.

21. How to Conduct a Constructive Code Review

What’s the difference between a negative experience and a constructive review?

22. An Essential Guide to Code Quality

Just like quality assurance is done in manufacturing, testing code quality is also done in software development. While developing software or if you're inspecting code written by your team, you need to make sure you verify its quality at every level of development before it gets more complex. In the world of software, the phrase code quality can be interpreted in different ways by different industries and teams.

23. 6 Surefire Ways To Suck At Maintaining Projects

Do you want to ensure that working with your repo is a constant source of frustration for your fellow developers? Read on for some awful tips.

24. Code Review: It's Bad, Expensive, and Ineffective [in most cases]

I am reviewing a practice we’re all aware of: code review.

25. How to Create PR Review Apps with Render

By making it simple to visually review changes, PR review apps make it more likely that code reviewers will actually do so.

26. Code Reviews: Tips On Getting More Feedback

Nobody leaving comments on your code reviews? Try out these 3 tips on getting eye balls on your pull requests

27. Software Engineers use Code Reviews to Improve Product Quality

Software engineers need to do code reviews in order to improve overall product quality and learn from each other. Code review process has a set of best practices like any other complex processes. Check best practices below. Do you follow them on your current project?

28. Code Review Is Inherently Flawed. Here’s How to Fix It

The classic code review process contains several severe flaws and should be redesigned. The story depicts how to do so.

29. The Myths and Realities of Bug-Free Code

30. Turning Debugging into a Life-Long Mission

Debugging is a means to tackle problems but what if it is possible to solve debugging itself?

31. How to Avoid Code Smells - A NDepend Tutorial

.NET developers can evaluate and visualize the codebase using the robust static analysis tool NDepend. It aids programmers in understanding the quality and main

32. How COVID-19 Is Changing The Way We Deliver Software In Brazil [Analysis]

At SourceLevel, we're in a privileged spot to gather some data on how software engineering teams are dealing with COVID-19, home office, social distancing, and so on.

33. Pandemic Remote Work != Remote Work

Have you switched to remote work in the past couple of weeks/days? Well, chances are high you have, or you will. I want to share my words of caution and tips to make pandemic remote work better.

34. Best Practices, Guidelines and Tools for Code Reviews

Code reviews are a type of software quality assurance activity that involves evaluations of code in order to identify bugs, improve code quality, and...

35. Technical Debt is Eating The World

The concept is simple: due to a lack of resources, people sometimes do not address a problem correctly when shipping a new feature or fixing a bug. This debt must be repaid (e.g. the problem needs to be addressed correctly) or the debt will accumulate and impact the software development in the future.

36. The Ultimate JavaScript Beginner's Guide To Static Code Analysis

The answers to every what, why, when, and how about Static Code Analysis in JavaScript. Information about in-depth scanning, guard rails, and more.

37. Onboard New Developers with Better Coding Practices

Onboard new developers take time, so you need to set up an efficient process to boost their appropriation of your technical culture and your best practices

38. How to Write Meaningful Code Comments

In this guide, you will learn why it is important to write code comments, what are different code comment types, and the 4 best practices.

39. Code Reviews For Non-technical People. Explained.

40. How to Use CodeSee's Code Automation to Create Dynamic Code Review Checklists

Wouldn’t it be nice if your pull request checklists could be dynamic and only show relevant reminders? With CodeSee Code Automation, we can enforce best practic

41. Navigating Big, Hairy Codebases Should Be Easy

With the insight that big code is big data, Sourcegraph uses the power of knowledge graphs to help developers search and understand any codebase in the world.

42. How to Make an Unforgettable Code Review? Guide for Authors

Code review is an integral part of any software development process. Here are a couple of rules for making great code review.

43. Pair Programming and Code Reviews Can Work, Sometimes.

In the post pandemic screen-sharing workspace, is it time for pair programming to get another shot?

44. Top 7 Techniques For The Ideal Secure Code Review

Considering today's cyber threat landscape, it is undeniable to say that the internet-facing applications are at major risk due to rapid increase in vulnerability exploits and ways to penetrate applications leveraging the hidden weaknesses in them.

45. Why Does it Often Take Nearly a Month to Ship a Few Lines of Code?

Ever wondered why it takes nearly a month to ship out a few lines of code change to the star and reliable customers of your company? When the changes made are formally aligned with the product, marketing and application managers, what stops it from being shipped immediately? Why do managers quote timelines for a maintenance release that seems so "unrealistic" to you? These were the thoughts that were going through my mind during my first few months of writing production-quality code.

46. To Code Is To Communicate: 8 Ways to Write Better Code Reviews

When I started programming, Code Review wasn’t part of my routine. First, like everyone, I learned how to print Hello World in the programming language that was studying. Then, what is an if, while, for, and other essential structures. Sometime later, I was coding.

47. What is Primitive Obsession and How Can we Fix it?

Primitive obsession is a code smell in which primitive data types are used excessively to represent your data models.

48. 4 Data Management APIs for Better and Faster Innovation

Application Programming Interfaces, or APIs, have revolutionized the way we do programming. Through them, we’re able to get two applications to communicate with each other without any need to intervene manually.

49. The Unsung Peer-to-Peer Review

The benefits of peer-to-peer reviews accrue to both the organization and the individuals.

50. 4 Ways Software Engineers Organize Their TODOs

TODOs are a tricky subject for developers. Many codebases are guilty of having TODOs linger around while nobody knows who’s responsible for a TODO or even has the required context to tackle it. Yet, should we feel ashamed for our lingering TODOs?

51. A Code Review Checklist to Focus on the Important Parts

A code review checklist, as well as clear rules and guidelines around code reviews, can make your code review practice so much more beneficial to your team and significantly speed-up code reviews.

52. How To Perform a Successful Incident Postmortem

An incident postmortem is a meeting that brings together all of the people that were directly or indirectly involved in a project to discuss and document it.

53. A Complete Guide to Code Reviews

Code review is not a battlefield, the reviewer is not an opponent of the author. Both of them are aligned on the same goals.

54. The Best 7 Coding Tools Powered by AI

7 most innovative AI (and especially ChatGPT) powered low-code code tools.

55. Effective Code Reviews For Remote Teams

Code Reviews in a remote-driven world yield a better software design and solution. Find out why that is the case in this latest article by John Vester.

56. Pull Request Checklist: What You Need to Do Before Assigning a PR to Someone

If you work in a team opening a Pull Request (or Merge Request) looks appropriate. It’s a common practice nowadays. However, have you ever thought about opening a Pull/Merge Request when working by yourself?

57. 5 responsibilities of a Tech Lead and 17 Metrics to Track Their Performance

Tech lead, team lead, software architects, and engineering managers — as any developer already knows, naming is hard. Throughout the industry, those roles are as fuzzy as their responsibilities.

58. GitHub Actions To Bring You Consistency

Read an article on how to use the GitHub Actions Evrone wrote to run rubocop, brakeman, reek, fasterer, hadolint, and dotenv-linter linters on your project.

59. Gradual Code Releases: An In-House Kubernetes Canary Controller

Our short-term strategy involved developing an in-house Canary deployment process powered by a custom Kubernetes controller.

60. The Ultimate Guide To Creating Review Apps on Heroku

Is there a way that we can use review apps and still ensure we’re not paying for resources we don’t need?

61. A Practical Guide to Better Code Reviews

A CODE REVIEW is a part of the development process in which a developer and their colleagues work together and look for bugs within some code that may be ready for release. At such a moment, you can be either the code developer or one of the reviewers.

62. 5 Critical Topics Covered at Once: Code Review Practises You Cannot Miss

Why do code reviews? How reviews help improve culture? In this article we'll summarize the lessons from a dozen of official company engineering blogs.

63. Pull Request Etiquette: 20 Core Principles For Handling PRs As A Software Developer

“Pull requests let you tell others about changes you've pushed to a branch in a repository on GitHub. Once a pull request is opened, you can discuss and review the potential changes with collaborators...” - Github

Thank you for checking out the 63 most read stories about Code Review on HackerNoon.

Visit the /Learn Repo to find the most read stories about any technology.