Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Rails is so popular to be used to fast build a website, at the beginning we sometimes write codes too fast without considering code quality, but after your company grows fast, you have to pay more attentions on code review to make your website more robust and more maintainable. In this talk I will introduce you a way to build a semi automatic code review process, in this process a tool will analyze the source codes of your rails project, then give you some suggestions to refactor your codes according to rails best practices. It can also check your codes according to your team's rails code guideline. So engineers can focus on implementation performance, scalability, etc. when they do code review.
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In this talk titled "Semi Automatic Code Review," Richard Huang presents a framework for improving productivity in code reviews, particularly in Ruby on Rails projects, as part of the development life cycle. This framework addresses the challenges that arise when code quality is not prioritized in the early stages of a fast-growing company. Key points discussed include: - **Development Life Cycle**: Richard outlines the typical development process which includes new feature implementation, bug fixing, manual code reviews, and QA testing prior to deployment. - **Code Review Importance**: Emphasizing the critical nature of code reviews, he notes that they can identify bugs and performance issues, albeit being a manual process that can introduce complexities. - **Automation Opportunities**: Huang suggests that while many stages of development can be automated, code reviews still largely rely on human evaluation. He introduces the idea of partially automating this by utilizing tools that help analyze code based on best practices. - **Rails Best Practice Gem**: Richard details the creation and functionality of the Rails Best Practice gem, which analyzes Rails project code and offers suggestions for refactoring. He highlights the benefits such as better readability and adherence to coding guidelines. For example, it can suggest using `scope` access for querying posts belonging to the current user, and using built-in methods to simplify code. - **Realbp.com**: In response to the needs identified during code reviews, Richard discusses the launch of realbp.com, an online service that integrates with GitHub. This service allows developers to track code quality over time, share analysis results with teammates, and customize what checks to apply based on team preferences. - **Plugins and Customization**: Richard explains the extensibility of the gem through plugins, allowing teams to adapt the checks to their specific coding guidelines. - **Practical Demonstration**: He provides a step-by-step guide on registering a GitHub repository with realbp.com, analyzing code, responding to suggestions, and tracking improvements. In conclusion, Huang stresses the dual focus of semi-automatic code reviews: improving code quality while enabling engineers to dedicate more time to critical performance and scalability concerns. The main takeaway is the push towards leveraging automation in the code review process to ultimately foster better coding practices and enhanced collaboration among engineers.
Suggest modifications
Cancel