English | MP4 | AVC 1280×720 | AAC 44KHz 2ch | 9h 8m | 1.45 GB
Deliver code reviews that consistently build up your team and improve your applications.
“Looks Good to Me” offers a unique approach to delivering meaningful code reviews that goes beyond superficial checklists and tense critical conversations. Instead, you’ll learn how to improve both your applications and your team dynamics.
“Looks Good to Me” teaches you how to:
- Understand a code review’s benefits proactively prevent loopholes and bottlenecks
- Co-create an objective code review system
- Clarify responsibilities: author, reviewer, team lead/manager, and the team itself
- Establish manageable guidelines and protocols
- Align with your team and explicitly document the policies they will follow
- Automate code quality with linting, formatting, static analysis, and automated testing
- Compose effective comments for any situation
- Consider combining code reviews with pair programming or mob programming
- AI for code reviews
Inside “Looks Good to Me” you’ll find comprehensive coverage of every part of the code review process, from choosing a system to keeping reviews manageable for everyone involved. With this mix of tools, processes, common sense, and compassion, you’ll run a highly effective review process from first commit to final deployment.
Transform code reviews into the positive, productive experiences they’re meant to be! Whether it’s your code under the microscope or you’re the one giving the feedback, this sensible guide will help you avoid the tense debates, fruitless nitpicking, and unnecessary bottlenecks you’ve come to expect from code reviews.
“Looks Good to Me” teaches the considerate, common sense approach to code reviews pioneered by author Adrienne Braganza. You’ll learn how to create a cohesive team environment, align review goals and expectations clearly, and be prepared for any changes or obstacles you may face. Along the way, you’ll master practices that adapt to how your team does things, with multiple options and solutions, relatable scenarios, and personal tidbits. You’ll soon be running highly effective reviews that make your code—and your team—stronger.
What’s Inside
- Why we do code reviews
- Automate processes for code quality
- Write effective comments
Table of Contents
Part 1. Code review foundations
Chapter 1. The significance of code reviews
Chapter 1. How this book is structured
Chapter 1. You should want code reviews
Chapter 1. Convincing your team
Chapter 1. Making code reviews better
Chapter 1. Summary
Chapter 2. Dissecting the code review
Chapter 2. How does a code review work?
Chapter 2. Elements of a great PR
Chapter 2. Code review participants and expectations
Chapter 2. Summary
Chapter 3. Building your team’s first code review process
Chapter 3. Choose your tools
Chapter 3. Set guidelines
Chapter 3. Refining the process
Chapter 3. Summary
Part 2. Elevated code review essentials
Chapter 4. The Team Working Agreement
Chapter 4. Setting team expectations with a Team Working Agreement
Chapter 4. Establishing a TWA with your team
Chapter 4. What to consider including in your TWA
Chapter 4. This TWA is the team’s document now
Chapter 4. Summary
Chapter 5. The advantages of automation
Chapter 5. Automation prerequisites
Chapter 5. Automations before the review
Chapter 5. Automations during the review
Chapter 5. Summary
Chapter 6. Composing effective code review comments
Chapter 6. Tone of voice
Chapter 6. Code compliments
Chapter 6. Summary
Part 3. Dealing with dilemmas
Chapter 7. How code reviews can suck
Chapter 7. So, what do we do?
Chapter 7. Summary
Chapter 8. Decreasing code review delays
Chapter 8. “I don’t understand the PR”
Chapter 8. “There are too many files to review”
Chapter 8. “Feature is too large to review”
Chapter 8. “There’s too much discussion back and forth”
Chapter 8. “Code needs to be refactored (sometimes over and over)”
Chapter 8. Summary
Chapter 9. Eliminating process loopholes
Chapter 9. Loopholes (and how to fix them)
Chapter 9. Summary
Chapter 10. The Emergency Playbook
Chapter 10. What goes in an Emergency Playbook?
Chapter 10. When do we use the Emergency Playbook?
Chapter 10. Summary
Part 4. Pairing code reviews with other practices
Chapter 11. Code reviews and pair programming
Chapter 11. Integrating pair programming
Chapter 11. Summary
Chapter 12. Code reviews and mob programming
Chapter 12. Integrating mob programming with code reviews
Chapter 12. Summary
Chapter 13. Code reviews and AI
Chapter 13. Limitations of AI in code reviews
Chapter 13. What can an AI-powered code review do?
Chapter 13. Integrating AI into your code reviews
Chapter 13. The future of code reviews: Human-AI collaboration
Chapter 13. Summary
Resolve the captcha to access the links!