Name: Building Mantainable Software, Java Edition (en Inglés)
Price: 46.67 USD
Availability: InStock
Author: Visser, Joost ; Rigal, Sylvan ; Leek, Rob Van Der
ISBN: 9781491953525

portada Building Mantainable Software, Java Edition (en Inglés)

Formato

Libro Físico

Autor

Editorial

Año

2016

Idioma

Inglés

N° páginas

168

Encuadernación

Tapa Blanda

Dimensiones

23.3 x 17.8 x 0.9 cm

Peso

0.28 kg.

ISBN13

9781491953525

N° edición

Categorías

Pruebas y verificación de software

Building Mantainable Software, Java Edition (en Inglés)

Joost Visser (Autor) · Sylvan Rigal (Autor) · Rob Van Der Leek (Autor) · O'Reilly Media · Tapa Blanda

Libro Nuevo

$ 46.67

$ 71.79

Ahorras: $ 25.13

35% descuento

Envío normal

Origen: Estados Unidos (Costos de importación incluídos en el precio)

Se enviará desde nuestra bodega entre el Miércoles 29 de Mayo y el Miércoles 12 de Junio.

Lo recibirás en cualquier lugar de Ecuador entre 1 y 3 días hábiles luego del envío.

Reseña del libro "Building Mantainable Software, Java Edition (en Inglés)"

Have you ever felt frustrated working with someone else's 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, you'll learn 10 easy-to-follow guidelines for delivering Java software that's 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.Write short units of code: limit the length of methods and constructorsWrite simple units of code: limit the number of branch points per methodWrite code once, rather than risk copying buggy codeKeep unit interfaces small by extracting parameters into objectsSeparate concerns to avoid building large classesCouple architecture components looselyBalance the number and size of top-level components in your codeKeep your codebase as small as possibleAutomate tests for your codebaseWrite clean code, avoiding "code smells" that indicate deeper problems