Name: Software Engineering at Google: Lessons Learned From Programming Over Time (en Inglés)
Price: 163589.00 COP
Availability: InStock
Author: Winters, Titus ; Manshreck, Tom ; Wright, Hyrum
ISBN: 9781492082798

portada Software Engineering at Google: Lessons Learned From Programming Over Time (en Inglés)

Formato

Libro Físico

Autor

Editorial

Año

2020

Idioma

Inglés

N° páginas

599

Encuadernación

Tapa Blanda

Dimensiones

23.1 x 17.5 x 3.3 cm

Peso

0.98 kg.

ISBN13

9781492082798

N° edición

Categorías

Gestión de proyectos empresariales
Pruebas y verificación de software
Análisis y diseño de sistemas

Software Engineering at Google: Lessons Learned From Programming Over Time (en Inglés)

Titus Winters (Autor) · Tom Manshreck (Autor) · Hyrum Wright (Autor) · O'Reilly Media · Tapa Blanda

Libro Nuevo

$ 163.589

$ 327.178

Ahorras: $ 163.589

50% 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 15 de Mayo y el Miércoles 29 de Mayo.

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

Reseña del libro "Software Engineering at Google: Lessons Learned From Programming Over Time (en Inglés)"

Today, software engineers need to know not only how to program effectively but also how to develop proper engineering practices to make their codebase sustainable and healthy. This book emphasizes this difference between programming and software engineering. How can software engineers manage a living codebase that evolves and responds to changing requirements and demands over the length of its life? Based on their experience at Google, software engineers Titus Winters and Hyrum Wright, along with technical writer Tom Manshreck, present a candid and insightful look at how some of the worldâ s leading practitioners construct and maintain software. This book covers Googleâ s unique engineering culture, processes, and tools and how these aspects contribute to the effectiveness of an engineering organization. Youâ ll explore three fundamental principles that software organizations should keep in mind when designing, architecting, writing, and maintaining code: How time affects the sustainability of software and how to make your code resilient over time How scale affects the viability of software practices within an engineering organization What trade-offs a typical engineer needs to make when evaluating design and development decisions