MARC details
000 -LEADER |
fixed length control field |
01542nam a22002297a 4500 |
003 - CONTROL NUMBER IDENTIFIER |
control field |
IIITD |
005 - DATE AND TIME OF LATEST TRANSACTION |
control field |
20230616135551.0 |
008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION |
fixed length control field |
230616b xxu||||| |||| 00| 0 eng d |
020 ## - INTERNATIONAL STANDARD BOOK NUMBER |
International Standard Book Number |
9789355423788 |
040 ## - CATALOGING SOURCE |
Original cataloging agency |
IIITD |
082 ## - DEWEY DECIMAL CLASSIFICATION NUMBER |
Classification number |
005.1 |
Item number |
ZIM-R |
100 ## - MAIN ENTRY--PERSONAL NAME |
Personal name |
Zimmerman, Chris |
245 ## - TITLE STATEMENT |
Title |
The rules of programming : |
Remainder of title |
how to write better code |
Statement of responsibility, etc |
by Chris Zimmerman |
260 ## - PUBLICATION, DISTRIBUTION, ETC. (IMPRINT) |
Name of publisher, distributor, etc |
O'Reilly, |
Place of publication, distribution, etc |
New Delhi : |
Date of publication, distribution, etc |
©2023 |
300 ## - PHYSICAL DESCRIPTION |
Extent |
xiv, 327 p. : |
Other physical details |
ill. ; |
Dimensions |
22 cm. |
500 ## - GENERAL NOTE |
General note |
Includes bibliographical references and index. |
505 ## - FORMATTED CONTENTS NOTE |
Title |
Rule 1 | As Simple as Possible, but No Simpler |
-- |
Rule 2 | Bugs Are Contagious |
-- |
Rule 3 | A Good Name Is the Best Documentation |
-- |
Rule 4 | Generalization Takes Three Examples |
-- |
Rule 5 | The First Lesson of Optimization Is<br/>Don’t Optimize |
-- |
Rule 6 | Code Reviews Are Good for Three Reasons |
-- |
Rule 7 | Eliminate Failure Cases |
-- |
Rule 8 | Code That Isn’t Running Doesn’t Work |
-- |
Rule 9 | Write Collapsible Code |
-- |
Rule 11 | Is It Twice as Good? |
-- |
Rule 12 | Big Teams Need Strong Conventions |
-- |
Rule 13 | Find the Pebble That Started the Avalanche |
-- |
Rule 14 | Code Comes in Four Flavors |
-- |
Rule 15 | Pull the Weeds |
-- |
Rule 16 | Work Backward from Your Result, Not Forward from<br/>Your Code |
-- |
Rule 17 | Sometimes the Bigger Problem Is<br/>Easier to Solve |
-- |
Rule 18 | Let Your Code Tell Its Own Story |
-- |
Rule 19 | Rework in Parallel |
-- |
Rule 20 | Do the Math |
-- |
Rule 21 | Sometimes You Just Need to Hammer the Nails |
650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM |
Topical term or geographic name as entry element |
Computer Science |
650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM |
Topical term or geographic name as entry element |
Semantic Web |
650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM |
Topical term or geographic name as entry element |
Computer Programming |
942 ## - ADDED ENTRY ELEMENTS (KOHA) |
Source of classification or shelving scheme |
Dewey Decimal Classification |
Koha item type |
Books |