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
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 Conscientious
Be Conscientious
SPEAKER: And then actually, I think a great process is the same as my mom's answering machine message. Which is that. And people like to use process, I guess to sort of control what people do. And enforce, I don't know, good practices on folks. But I think the bottom line is that if you don't trust your developers, if you can't trust developers to make, in general, good choices, you're never going to have very good code. It's never going to be an efficient experience because they're not trying, or they don't want to, or they can't, or whatever, right? So assuming that your developers in general want to do a good job, and the process is just there to do natural mistakes, which again is what I think code review is. Natural mistakes that of course you make, just like when you write. And therefore, you can also trust them to decide when code review is going to be effective. You know when you make a change, and it's really just a typo in a string constant somewhere, I don't really need to waste someone else's time. And you also know when you make some changes you're not that comfortable with, where there's no unit test coverage. And you're not the domain expert in this part of the code, but you're helping out anyway. And you kind of get that feeling like, I have no confidence that what I just did didn't break something. That's when you ask for a code review, maybe from someone who is a domain expert in this part of the code. Hopefully that, just to get the double check. And you know you should get a double check. So I feel like leaving it in the hands of your conscientious developers is not a bad process. And probably a good use of time. They won't in general waste too much time on that. They feel they need something. They feel they need a double check, good. I'm glad you asked. Let's just have a process in place that's easy to measure that we're doing that.
