MARC Record from marc_nuls

LEADER: 02202cam 22003617i 4500
001 9925254808001661
005 20161004051212.7
008 160901t20162016cc a 001 0 eng d
010 $a 2016448126
020 $a9781491953525$q(paperback)
020 $a1491953527$q(paperback)
035 $a99970070785
035 $a(OCoLC)937454393
035 $a(OCoLC)ocn937454393
040 $aYDXCP$beng$erda$cYDXCP$dDLC$dCPL$dBDX$dNBO$dOCLCF$dHF9
042 $alccopycat
050 00 $aQA76.76.D47$bV573 2016
082 04 $a005.1$223
100 1 $aVisser, Joost,$eauthor.
245 10 $aBuilding maintainable software :$bten guidelines for future-proof code /$cJoost Visser.
250 $aJava edition, First edition.
264 1 $aBeijing :$bO'Reilly,$c[2016]
264 4 $cỨ́2016
300 $axix, 145 pages :$billustrations ;$c24 cm
336 $atext$btxt$2rdacontent
337 $aunmediated$bn$2rdamedia
338 $avolume$bnc$2rdacarrier
504 $aIncludes index.
520 $aHave you ever felt frustrated working with someone elses code? Difficult-to-maintain source code is a big problem in software development today, leading to costly delays and defects. Be part of the solution. With this practical book, youll learn 10 easy-to-follow guidelines for delivering Java software thats easy to maintain and adapt. These guidelines have been derived from analyzing hundreds of real-world systems. Written by consultants from the Software Improvement Group (SIG), this book provides clear and concise explanations, with advice for turning the guidelines into practice. Examples for this edition are written in Java, while our companion C# book provides workable examples in that language. -- Provided by publisher.
505 0 $aWrite short units of code -- Write simple units of code -- Write code once -- Keep unit interfaces small -- Separate concerns in modules -- Couple architecture components loosely -- Keep architecture components balanced -- Keep your codebase small -- Automotive tests -- Write clean code -- Next steps -- How SIG measures maintainability.
650 0 $aComputer software$xDevelopment.
947 $hCIRCSTACKS$r31786103051378
980 $a99970070785