The rules of programming : (Record no. 94805)

MARC details
000 -LEADER
fixed length control field 02044nam a22002537a 4500
003 - CONTROL NUMBER IDENTIFIER
control field OSt
005 - DATE AND TIME OF LATEST TRANSACTION
control field 20240510134730.0
008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION
fixed length control field 240427b |||||||| |||| 00| 0 eng d
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
International Standard Book Number 9781098133115
050 ## - LIBRARY OF CONGRESS CALL NUMBER
Classification number SHS QA 76.6 Z56
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. Chris Zimmerman
264 ## - PRODUCTION, PUBLICATION, DISTRIBUTION, MANUFACTURE, AND COPYRIGHT NOTICE
Place of production, publication, distribution, manufacture Sebastopol, CA :
Name of producer, publisher, distributor, manufacturer O'Reilly Media ,
Date of production, publication, distribution, manufacture, or copyright notice 2023.
300 ## - PHYSICAL DESCRIPTION
Extent xiv, 327 pages ;
Dimensions 23 cm.
336 ## - CONTENT TYPE
Source rdacontent
Content type term text
337 ## - MEDIA TYPE
Source rdamedia
Media type term unmediated
338 ## - CARRIER TYPE
Source rdacarrier
Carrier type term volume
500 ## - GENERAL NOTE
General note Includes index.
505 ## - FORMATTED CONTENTS NOTE
Formatted contents note As simple as possible, but no simpler -- Bugs are contagious -- A good name is the best documentation -- Generalization takes three examples -- The first lesson of optimization is don't optimize -- Interlude: In which the previous chapter is criticized -- Code reviews are good for three reasons -- Eliminate failure cases -- Code that isn't running doesn't work -- Write collapsible code -- Localize complexity -- Is it twice as good? -- Big teams need strong conventions -- Find the pebble that started the avalanche -- Code comes in four flavors -- Pull the weeds -- Work backward from your result, not forward from your code --- Sometimes the bigger problem is easier to solve -- Let your code tell its own story -- Rework in parallel -- Do the math -- Sometimes you just need to hammer the nails -- Conclusion: Making the rules your own -- Appendix A. Reading C++ for Python programmers -- Appendix B. Reading C++ for JavaScript programmers.
520 ## - SUMMARY, ETC.
Summary, etc. "This philosophy-of-programming guide presents a unique and entertaining take on how to think about programming. A collection of 21 pragmatic rules, each presented in a standalone chapter, captures the essential wisdom that every freshly minted programmer needs to know and provides thought-provoking insights for more seasoned programmers"-- Provided by publisher
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 Programming
Form subdivision Philosophy
942 ## - ADDED ENTRY ELEMENTS (KOHA)
Source of classification or shelving scheme Library of Congress Classification
Koha item type Books
Call number prefix EAC Cavite-Senior High School Library
Holdings
Withdrawn status Lost status Source of classification or shelving scheme Damaged status Not for loan Home library Current library Shelving location Date acquired Cost, normal purchase price Total Checkouts Full call number Barcode Date last seen Cost, replacement price Price effective from Koha item type
    Library of Congress Classification     EAC Library Cavite EAC Library Cavite EAC Cavite-Senior High School Library 01/09/2024 4905.00   SHS QA 76.6 Z56 SHS1380 04/27/2024 4905.00 04/27/2024 Books