Red Hat announced a multi-stage alliance to offer customers a greater choice of operating systems to run on Oracle Cloud Infrastructure (OCI).
It shouldn’t come as a surprise that software quality is a top concern for organizations of all shapes and sizes. But heavy workloads, time constraints and lack of manpower plague many organizations. Despite the obstacles, however, with the right tools and best practices, teams can successfully and consistently peer review all code – leading to higher quality software in less time and at a reduced cost.
According to survey respondents in SmartBear Software's new report State of Code Quality 2016: Trends & Insights into Dev Collaboration, code review is looked at as the number one way to improve code quality.
However, ad-hoc or “over the shoulder” code review is the most commonly used type of code review within organizations with nearly three-quarters of respondents participating in ad-hoc reviews throughout the year.
Half of respondents are doing meeting based code review with 37 percent doing it as least once a month.
63 percent are doing tool-based code review with only 23 percent doing it on a daily basis.
Aside from code review, unit testing is considered to be the next most critical method for improving code quality.
Methodology: SmartBear surveyed 600 software developers, testers, IT/operations professionals and business leaders representing more than 30 different industries. The global online survey was conducted during December 2015. Participants in the survey work on software teams ranging from less than five employees up to more than 50 employees, and work for companies ranging from small businesses with less than 25 employees, to enterprise organizations with 10,000 employees or more.