SmartBear
Cart
Login
Welcome back to SmartBear Software
Click the links below to login to your favorite tool or into your client services portal
SmartBear Forum
Register
Log in
Development
DevComplete
ALMComplete
AQtime Pro
Automated Build Studio
Testing & QA
TestComplete
TestExecute
TestRecorder
QAComplete
LoadCOmplete
Web Monitoring
AlertSite
Free Tools
QAPlanner
DevPlanner
Looking for a Free Trial?
Products
Products
For Development
Collaborator
Code Review & Document Review
ALMComplete
Lifecycle Management
AQtime Pro
Performance Profiling
Automated Build Studio
Software Release Management
SoapUI Pro
API Testing - SoapUI Pro
All Development
For Testing & QA
TestComplete
Automated Testing
QAComplete
Test Management
WebLoadUI Pro
Load Testing
AQtime Pro
Performance Profiling
LoadUI Pro
API Load Testing
All Testing & QA
For Web Monitoring
AlertSite
Website Monitoring
AlertSite API Monitoring
Free API Monitoring
AlertSite Insite
Internal Website Monitoring
Free Tools
AlertSite for API Monitoring
CodeReviewer
WebLoadUI
DéjàClick
AlertSite for Magento
Open Source Tools
SoapUI
LoadUI
Get the Free Tools
For Your Needs
Agile Testing
API Testing
Automated Testing
Code Review
Load Testing Tools
Test Management
Web Monitoring
Resources
Resources Overview
eBooks
Templates & Worksheets
Videos
Whitepapers
Support
Support when you need it
SmartBear technical representatives are always ready to help with your product needs.
Browse our support portal
Know what you're looking for?
Downloads
User Guides
How To Tutorials
Technical Articles
Screencasts/Videos
General support
Forums
Troubleshooter
FAQs
Product Versions
Community
About Us
Contact Us
Our Partners
Our Team
Our Customers
Careers
Awards
Our Speakers
Request a Speaker
News & Events
News Releases
Events
In the News
Webinars On-demand
Prior Events
Blog
Share
Home
›
Be Selective
Be Selective
SPEAKER: But then there's a little bit of inception in a sense in that you feel like, OK, got to do something in code review. Something, maybe not review all the code like we do. Although a lot of our customers do. Because once it's efficient, there you go. But if you're now thinking like, OK, we've got to do something with some of our code, but I don't want to do too much because it might be a waste of time, and I want to measure whether it's a waste of time or not before rolling it out everywhere and so on, where can I start? What can I do a little bit of that probably has a good return on time? And maybe you'll never do more than that. Maybe you just stick with a small sliver that definitely has a good return on your time. Or maybe you sort of let that grow, and keep measuring whether it's a good return on time, and just stop when it's not. So I wanted to give you some very simple ways to get started like that that you can do tomorrow if you want. Wait. Yeah. Tomorrow's Friday. Maybe Monday. So one of the obvious things is just pick certain files, like you have a stable code branch that you sometimes make patches on. Well, if you do patches on a stable branch, like it's really clear that it's worth spending extra time to make those right because, a bad patch like that obviously costs a whole lot of money and annoyance, and so forth. So maybe just those. And especially in RTC when you have the ability to have all kinds of code paths and branches, and streams and whatnot. Then it's sort of natural that you would do something like that. Or another one is I have a core module that 97% percent of the code indirectly runs through. So obviously it changes to that. Super important for that to not break. Super important for the unit tests on that to be really good, and so forth. And so maybe that's worth putting extra time on in a code review sense. There's also, in every project you know that there's like, at least one, maybe five files that nobody ever wants to touch. This is the scary, complicated, horrible file, right? Everyone's like, oh, no. So a really simple process would just be if anybody touches one of those code review time. Because nobody's going to stand up and go, I'm super comfortable messing with this 4,000 line crazy class, right? No one's comfortable, so get help. Like, it's kind of obvious, right?
