Code Reviews That Don’t Suck: Tips for Reviewers and Submitters

Authors

  • Bhavitha Guntupalli ETL/Data Warehouse Developer at Blue Cross Blue Shield of Illinois, USA. Author
  • Venkata ch Software Developer at Northern Trust Bank, USA. Author

DOI:

https://doi.org/10.63282/3050-922X.IJERET-V6I2P109

Keywords:

Code review, pull request, software development, peer review, code quality, submitter tips, reviewer guidelines, DevOps, continuous integration, engineering best practices, collaborative programming, version control, GitHub, merge request, productivity

Abstract

In collaborative software development, code reviews are essential; yet, oftentimes they seem difficult, useless, or even hostile. This paper presents acceptable suggestions to increase the relevance and efficiency of code reviews, therefore addressing the typical problems found by submitters and reviewers. The statistics mostly support a paradigm change: seeing code review as a developmental conversation among peers rather than as a gatekeeping tool. This entails focusing on clarity rather than wit for reviewers, replacing help with sarcasm, and stressing the goal of the code rather than only its syntax. For submitters, it means aggressively clarifying design decisions, embracing comments with their openness, and viewing review as an opportunity for development rather than just a procedural need. The article offers ideas and techniques to handle these recurring problems, including unclear remarks, too much inspection, long review times, and false expectations. Typical motifs are clarity, empathy, technique, and tools. Empathy is learning the humanity concealed under every set of rules. Clarity is writing even for your future self clear, understandable comments and commitments. The procedure includes well-defined policies and timetables to help assessments stay on their intended route or avoid stretching too long. From linters to review templates, tooling can help to reduce friction and direct focus on these critical issues. Regardless of your experience level as an engineer, this piece offers sharp analysis and useful advice to turn code reviews from unwelcome chores into major team building, trust, and technical knowledge possibilities

References

[1] Laurvik, Torgeir Sandnes. Design process behind an educational review system for student submissions-applying knowledge from professional code reviews to an educational assessment setting. MS thesis. NTNU, 2021.

[2] Pasupuleti, Vikram, et al. "Impact of AI on architecture: An exploratory thematic analysis." African Journal of Advances in Science and Technology Research 16.1 (2024): 117-130.

[3] Lalith Sriram Datla, and Samardh Sai Malay. “Transforming Healthcare Cloud Governance: A Blueprint for Intelligent IAM and Automated Compliance”. Journal of Artificial Intelligence & Machine Learning Studies, vol. 9, Jan. 2025, pp. 15-37

[4] Radez, Jerica, et al. "Why do children and adolescents (not) seek and access professional help for their mental health problems? A systematic review of quantitative and qualitative studies." European child & adolescent psychiatry 30.2 (2021): 183-211.

[5] Cohen, Jason, Steven Teleki, and Eric Brown. Best kept secrets of peer code review. Smart Bear Incorporated, 2006.

[6] Talakola, Swetha. “Transforming BOL Images into Structured Data Using AI”. International Journal of Artificial Intelligence, Data Science, and Machine Learning, vol. 6, no. 1, Mar. 2025, pp. 105-14

[7] Platt, David S. Why software sucks--and what you can do about it. Addison-Wesley Professional, 2007.

[8] Syed, Ali Asghar Mehdi. "Zero Trust Security in Hybrid Cloud Environments: Implementing and Evaluating Zero Trust Architectures in AWS and On-Premise Data Centers." International Journal of Emerging Trends in Computer Science and Information Technology 5.2 (2024): 42-52.

[9] Zanjani, Motahareh Bahrami, Huzefa Kagdi, and Christian Bird. "Automatically recommending peer reviewers in modern code review." IEEE Transactions on Software Engineering 42.6 (2015): 530-543.

[10] Allam, Hitesh. “Intent-Based Infrastructure: Moving BeyondIaC to Self-Describing Systems”. International Journal of Artificial Intelligence, Data Science, and Machine Learning, vol. 6, no. 1, Jan. 2025, pp. 124-36

[11] Jabbar Mohammad, Abdul. “Integrating Timekeeping and Payroll Systems During Organizational TransitionsMergers, Layoffs, Spinoffs, and Relocations”. Los Angeles Journal of Intelligent Systems and Pattern Recognition, vol. 5, Feb. 2025, pp. 25-53

[12] MacLeod, Laura, et al. "Code reviewing in the trenches: Challenges and best practices." IEEE Software 35.4 (2017): 34-42.

[13] Jani, Parth. "Modernizing Claims Adjudication Systems with NoSQL and Apache Hive in Medicaid Expansion Programs." JOURNAL OF RECENT TRENDS IN COMPUTER SCIENCE AND ENGINEERING (JRTCSE) 7.1 (2019): 105-121.

[14] Remillard, Jason. "Source code review systems." IEEE software 22.1 (2005): 74-77.

[15] Veluru, Sai Prasad. "Reversible Neural Networks for Continual Learning with No Memory Footprint." International Journal of AI, BigData, Computational and Management Studies 5.4 (2024): 61-70.

[16] Boland, Angela, Gemma Cherry, and Rumona Dickson, eds. "Doing a systematic review: a student′ s guide." (2017).

[17] Chaganti, Krishna Chiatanya. "Securing Enterprise Java Applications: A Comprehensive Approach." International Journal of Science And Engineering 10.2 (2024): 18-27.

[18] Hamasaki, Kazuki, et al. "Who does what during a code review? datasets of oss peer review repositories." 2013 10th Working Conference on Mining Software Repositories (MSR). IEEE, 2013.

[19] Sriram Datla, Lalith, and Samardh Sai Malay. “Zero-Touch Decommissioning in Healthcare Clouds: An Automation Playbook With AWS Nuke and GuardRails”. Los Angeles Journal of Intelligent Systems and Pattern Recognition, vol. 5, Mar. 2025, pp. 1-24.

[20] Chaganti, Krishna Chaitanya. "AI-Powered Threat Detection: Enhancing Cybersecurity with Machine Learning." International Journal of Science And Engineering 9.4 (2023): 10-18.

[21] Okoli, Chitu. "A guide to conducting a standalone systematic literature review." Communications of the Association for Information Systems 37 (2015).

[22] Talakola, Swetha. “The Optimization of Software Testing Efficiency and Effectiveness Using AI Techniques”. International Journal of Artificial Intelligence, Data Science, and Machine Learning, vol. 5, no. 3, Oct. 2024, pp. 23-34

[23] Tawfik, Gehad Mohamed, et al. "A step by step guide for conducting a systematic review and meta-analysis with simulation data." Tropical medicine and health 47 (2019): 1-9.

[24] Balkishan Arugula, and Suni Karimilla. “Modernizing Core Banking Systems: Leveraging AI and Microservices for Legacy Transformation”. Artificial Intelligence, Machine Learning, and Autonomous Systems, vol. 9, Feb. 2025, pp. 36-67

[25] Ridley, Diana. "The literature review: A step-by-step guide for students." (2012): 1-232.

[26] Allam, Hitesh. "Policy-Driven Engineering: Automating Compliance Across DevOps Pipelines." International Journal of Emerging Trends in Computer Science and Information Technology 6.1 (2025): 89-100. -mar

[27] Veluru, Sai Prasad. "Threat Modeling in Large-Scale Distributed Systems." International Journal of Emerging Research in Engineering and Technology 1.4 (2020): 28-37.

[28] Kraus, Sascha, Matthias Breier, and Sonia Dasí-Rodríguez. "The art of crafting a systematic literature review in entrepreneurship research." International Entrepreneurship and Management Journal 16 (2020): 1023-1042.

[29] Abdul Jabbar Mohammad, and Guru Modugu. “Behavioral TimekeepingUsing Behavioral Analytics to Predict Time Fraud and Attendance Irregularities”. Artificial Intelligence, Machine Learning, and Autonomous Systems, vol. 9, Jan. 2025, pp. 68-95.

[30] Wolfswinkel, Joost F., Elfi Furtmueller, and Celeste PM Wilderom. "Using grounded theory as a method for rigorously reviewing literature." European journal of information systems 22.1 (2013): 45-55.

[31] Jani, Parth. "Document-Level AI Validation for Prior Authorization Using Iceberg+ Vision Models." International Journal of AI, BigData, Computational and Management Studies 5.4 (2024): 41-50.

[32] Arugula, Balkishan. “Prompt Engineering for LLMs: Real-World Applications in Banking and Ecommerce”. International Journal of Artificial Intelligence, Data Science, and Machine Learning, vol. 6, no. 1, Jan. 2025, pp. 115-23

[33] Kupanarapu, Sujith Kumar. "AI-POWERED SMART GRIDS: REVOLUTIONIZING ENERGY EFFICIENCY IN RAILROAD OPERATIONS." INTERNATIONAL JOURNAL OF COMPUTER ENGINEERING AND TECHNOLOGY (IJCET) 15 (2024): 981-991.

[34] Vasanta Kumar Tarra. “Ethical Considerations of AI in Salesforce CRM: Addressing Bias, Privacy Concerns, and Transparency in AI-Driven CRM Tools”. American Journal of Autonomous Systems and Robotics Engineering, vol. 4, Nov. 2024, pp. 120-44

[35] Kodete, Chandra Shikhi, et al. "Robust Heart Disease Prediction: A Hybrid Approach to Feature Selection and Model Building." 2024 4th International Conference on Ubiquitous Computing and Intelligent Information Systems (ICUIS). IEEE, 2024.

[36] Bacchelli, Alberto, and Christian Bird. "Expectations, outcomes, and challenges of modern code review." 2013 35th International Conference on Software Engineering (ICSE). IEEE, 2013.

[37] Sreekandan Nair, S., & Lakshmikanthan, G. . (2021). Open Source Security: Managing Risk in the Wake of Log4j Vulnerability. International Journal of Emerging Trends in Computer Science and Information Technology, 2(4), 33-45. https://doi.org/10.63282/d0n0bc24

Downloads

Published

2025-05-20

Issue

Section

Articles

How to Cite

1.
Guntupalli B, ch V. Code Reviews That Don’t Suck: Tips for Reviewers and Submitters. IJERET [Internet]. 2025 May 20 [cited 2025 Oct. 28];6(2):71-80. Available from: https://ijeret.org/index.php/ijeret/article/view/220