Software engineering at Google : (Record no. 80305)
[ view plain ]
| 000 -LEADER | |
|---|---|
| fixed length control field | 02021nam a22002417a 4500 |
| 008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION | |
| fixed length control field | 220824b2020 |||||||| |||| 00| 0 eng d |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
| International Standard Book Number | 9789352139743 |
| 082 ## - DEWEY DECIMAL CLASSIFICATION NUMBER | |
| Classification number | 005.1 WIN-T |
| 100 ## - MAIN ENTRY--PERSONAL NAME | |
| Personal name | Winters, Titus |
| 245 ## - TITLE STATEMENT | |
| Title | Software engineering at Google : |
| Remainder of title | lessons learned from programming over time / |
| Statement of responsibility, etc. | Titus Winters, Tom Manshreck and Hyrum Wright |
| 260 ## - PUBLICATION, DISTRIBUTION, ETC. (IMPRINT) | |
| Place of publication, distribution, etc. | India |
| Name of publisher, distributor, etc. | Shroff Publishers |
| Date of publication, distribution, etc. | 2020 |
| 300 ## - PHYSICAL DESCRIPTION | |
| Extent | 571 p. |
| 365 ## - TRADE PRICE | |
| Price type code | INR |
| Price amount | 2100.00. |
| 500 ## - GENERAL NOTE | |
| General note | 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.<br/><br/>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.<br/><br/>You’ll explore three fundamental principles that software organizations should keep in mind when designing, architecting, writing, and maintaining code:<br/><br/>How time affects the sustainability of software and how to make your code resilient over time<br/>How scale affects the viability of software practices within an engineering organization<br/>What trade-offs a typical engineer needs to make when evaluating design and development decisions. |
| 650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM | |
| Topical term or geographic name as entry element | Google (Firm) |
| 650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM | |
| Topical term or geographic name as entry element | Computer software--Development |
| 650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM | |
| Topical term or geographic name as entry element | Software engineering--Management |
| 650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM | |
| Topical term or geographic name as entry element | Software engineering |
| 650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM | |
| Topical term or geographic name as entry element | Computer programming |
| 650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM | |
| Topical term or geographic name as entry element | Computer software |
| 700 ## - ADDED ENTRY--PERSONAL NAME | |
| Personal name | Manshreck, Tom |
| 700 ## - ADDED ENTRY--PERSONAL NAME | |
| Personal name | Wright, Hyrum |
| 952 ## - LOCATION AND ITEM INFORMATION (KOHA) | |
| Withdrawn status | |
| Lost status | Source of classification or shelving scheme | Damaged status | Not for loan | Collection code | Home library | Current library | Shelving location | Date acquired | Total Checkouts | Full call number | Barcode | Date last seen | Date last checked out | Price effective from | Koha item type |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Dewey Decimal Classification | 003-007 | BITS Pilani Hyderabad | BITS Pilani Hyderabad | General Stack (For lending) | 24/08/2022 | 1 | 005.1 WIN-T | 46110 | 13/07/2024 | 22/04/2023 | 24/08/2022 | Books |