|
|
|
|
| LEADER |
03097nmm a2200397 u 4500 |
| 001 |
EB001926006 |
| 003 |
EBX01000000000000001088908 |
| 005 |
00000000000000.0 |
| 007 |
cr||||||||||||||||||||| |
| 008 |
210123 ||| eng |
| 050 |
|
4 |
|a QA76.76.D47
|
| 100 |
1 |
|
|a Kanellopoulos, Yiannis
|
| 245 |
0 |
0 |
|a Improving code quality
|b a survey of tools, trends, and habits across software organizations
|c Yiannis Kanellopoulos and Tim Walker
|
| 250 |
|
|
|a First edition
|
| 260 |
|
|
|a Sebastopol, CA
|b O'Reilly Media
|c 2017
|
| 300 |
|
|
|a 1 volume
|b illustrations
|
| 505 |
0 |
|
|a Includes bibliographical references
|
| 653 |
|
|
|a Technologie de l'information / Gestion
|
| 653 |
|
|
|a Information technology / Management / fast
|
| 653 |
|
|
|a Développeurs de logiciels / Attitudes
|
| 653 |
|
|
|a Computer software / Development / http://id.loc.gov/authorities/subjects/sh85029535
|
| 653 |
|
|
|a Computer software / Development / fast
|
| 653 |
|
|
|a Génie logiciel
|
| 653 |
|
|
|a Computer software developers / Attitudes
|
| 653 |
|
|
|a Software engineering / http://id.loc.gov/authorities/subjects/sh87007398
|
| 653 |
|
|
|a Software engineering / fast
|
| 653 |
|
|
|a Information technology / Management / http://id.loc.gov/authorities/subjects/sh2008006980
|
| 700 |
1 |
|
|a Walker, Tim
|e author
|
| 041 |
0 |
7 |
|a eng
|2 ISO 639-2
|
| 989 |
|
|
|b OREILLY
|a O'Reilly
|
| 776 |
|
|
|z 9781491985090
|
| 856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/9781491985106/?ar
|x Verlag
|3 Volltext
|
| 082 |
0 |
|
|a 658
|
| 082 |
0 |
|
|a 000
|
| 082 |
0 |
|
|a 620
|
| 520 |
|
|
|a Everyone in software development supports the goal of producing high-quality code. And yet, long-term observations in the field by the Software Improvement Group (SIG) reveals that many organizations don't have the necessary resources or institutional processes to make it happen. In this report, you'll learn how 1,442 software developers responded to a 2016 survey on code quality conducted by SIG in collaboration with O'Reilly. The results reinforce previous findings that, although code quality is valued in principle, software development organizations often measure and manage it unevenly--or not at all--in their day-to-day practices. This report provides a detailed assessment of responses to survey questions about working environments, accountability for code quality, and the use of code quality processes and tools. Major findings reveal that: A large majority of respondents believe that accountability for code quality rests with individual developers and their teams Most developers don't use tools for improving software quality, largely because they lack the budget to acquire them Many developers can't rely on common code quality tools because those tools don't support the technologies and languages they use Other developers are simply unaware of available tools, or are working with teams that have never used them How does your organization and development team stack up against these survey results? Compare your coding habits to the questions in this report and learn about your own code quality efforts and capabilities
|