Amazon cover image
Image from Amazon.com

The rules of programming : how to write better code

By: Material type: TextTextPublication details: O'Reilly, New Delhi : ©2023Description: xiv, 327 p. : ill. ; 22 cmISBN:
  • 9789355423788
Subject(s): DDC classification:
  • 005.1 ZIM-R
Contents:
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 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 Your Code Rule 17 | Sometimes the Bigger Problem Is 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
Tags from this library: No tags from this library for this title. Log in to add tags.
Star ratings
    Average rating: 0.0 (0 votes)
Holdings
Item type Current library Collection Call number Status Date due Barcode Item holds
Books Books IIITD General Stacks Computer Science and Engineering 005.1 ZIM-R (Browse shelf(Opens below)) Available 012053
Total holds: 0

Includes bibliographical references and index.

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
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
Your Code Rule 17 | Sometimes the Bigger Problem Is
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

There are no comments on this title.

to post a comment.
© 2024 IIIT-Delhi, library@iiitd.ac.in