AI Personalization

Code Review Matters: Best Practices From Engineers

Carine Alexis

|

February 11, 2020

Software Engineer Kate Ruggeri [spoke with Built In NYC](https://www.builtinnyc.com/2020/02/06/code-review-best-practices-nyc?utm_source=press_kit&utm_medium=social_media&utm_campaign=movableink) about how our team manages code reviews, including best practices, how we foster a positive code review culture, and what our team does when differences arise.![](https://s3.amazonaws.com/movableink-blog-production/wp-content/uploads/2020/02/10135708/Screen-Shot-2020-02-05-at-4.10.44-PM.png)Our engineering team**What best practices does your team follow when doing code reviews?**----------------------------------------------------------------------I’m lucky to work with such smart, empathetic and curious folks who aren’t afraid to ask questions and challenge each other. Probably the best advice I’ve ever had for giving good code reviews is to not let a single line of code get past you that you don’t understand. The team also has clear goals on incorporating modern Ember practices such as switching over to use Ember Octane. We like to leave things cleaner than we found them.**You can check out the rest of Kate’s interview along with best practices from 4 other engineers** [**here**](https://www.builtinnyc.com/2020/02/06/code-review-best-practices-nyc?utm_source=press_kit&utm_medium=social_media&utm_campaign=movableink)---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------