000			01542nam a22002297a 4500
003			IIITD
005			20230616135551.0
008			230616b xxu||||| |||| 00| 0 eng d
020			_a9789355423788
040			_aIIITD
082			_a005.1 _bZIM-R
100			_aZimmerman, Chris
245			_aThe rules of programming : _bhow to write better code _cby Chris Zimmerman
260			_bO'Reilly, _aNew Delhi : _c©2023
300			_axiv, 327 p. : _bill. ; _c22 cm.
500			_aIncludes bibliographical references and index.
505			_tRule 1 | As Simple as Possible, but No Simpler _tRule 2 | Bugs Are Contagious _tRule 3 | A Good Name Is the Best Documentation _tRule 4 | Generalization Takes Three Examples _tRule 5 | The First Lesson of Optimization Is Don’t Optimize _tRule 6 | Code Reviews Are Good for Three Reasons _tRule 7 | Eliminate Failure Cases _tRule 8 | Code That Isn’t Running Doesn’t Work _tRule 9 | Write Collapsible Code _tRule 11 | Is It Twice as Good? _tRule 12 | Big Teams Need Strong Conventions _tRule 13 | Find the Pebble That Started the Avalanche _tRule 14 | Code Comes in Four Flavors _tRule 15 | Pull the Weeds _tRule 16 | Work Backward from Your Result, Not Forward from Your Code _tRule 17 | Sometimes the Bigger Problem Is Easier to Solve _tRule 18 | Let Your Code Tell Its Own Story _tRule 19 | Rework in Parallel _tRule 20 | Do the Math _tRule 21 | Sometimes You Just Need to Hammer the Nails
650			_aComputer Science
650			_aSemantic Web
650			_aComputer Programming
942			_2ddc _cBK
999			_c171336 _d171336