Coverart for item
The Resource Programming beyond practices : be more than just a code monkey, Gregory T. Brown

Programming beyond practices : be more than just a code monkey, Gregory T. Brown

Label
Programming beyond practices : be more than just a code monkey
Title
Programming beyond practices
Title remainder
be more than just a code monkey
Statement of responsibility
Gregory T. Brown
Creator
Subject
Language
eng
Cataloging source
OQX
http://library.link/vocab/creatorName
Brown, Gregory T
Illustrations
illustrations
Index
index present
Literary form
non fiction
Nature of contents
bibliography
http://library.link/vocab/subjectName
Computer programming
Label
Programming beyond practices : be more than just a code monkey, Gregory T. Brown
Instantiates
Publication
Bibliography note
Includes bibliographical references and index
Carrier category
volume
Carrier category code
  • nc
Carrier MARC source
rdacarrier
Content category
text
Content type code
  • txt
Content type MARC source
rdacontent
Contents
Using Prototypes to Explore Project Ideas. Start by understanding the needs behind the project; Use wireframes to set expectations about functionality; Set up a live test system as soon as you start coding; Discuss all defects, but be pragmatic about repairs; Check your assumptions early and often; Limit the scope of your work as much as possible; Remember that prototypes are not production systems; Design features that make collecting feedback easy -- Spotting Hidden Dependencies in Incremental Changes. There's no such thing as a standalone feature. If two features share a screen, they depend on each other; Avoid non-essential real-time data synchronization; Look for problems when code is reused in a new context -- Identifying the Pain Points of Service Integrations. Plan for trouble when your needs are off the beaten path; Remember that external services might change or die; Look for outdated mocks in tests when services change; Expect maintenance headaches from poorly coded robots; Remember that there are no purely internal concerns -- Developing a Rigorous Approach Toward Problem Solving. Begin by gathering the facts and stating them plainly; Work part of the problem by hand before writing code; Validate your input data before attempting to process it; Make use of deductive reasoning to check your work; Solve simple problems to understand more difficult ones -- Designing Software from the Bottom Up. Identify the nouns and verbs of your problem space; Begin by implementing a minimal slice of functionality; Avoid unnecessary temporal coupling between objects; Gradually extract reusable parts and protocols; Experiment freely to discover hidden abstractions; Know where the bottom-up approach breaks down -- Data Modeling in an Imperfect World. Decouple conceptual modeling from physical modeling; Design an explicit model for tracking data changes; Understand how Conway's Law influences data management practices; Remember that workflow design and data modeling go hand in hand -- Gradual Process Improvement as an Antidote for Overcommitment. Respond to unexpected failures with swiftness and safety; Identify and analyze operational bottlenecks; Pay attention to the economic tradeoffs of your work; Reduce waste by limiting work in progress; Make the whole greater than the sum of its parts -- The Future of Software Development
Control code
ocn962767795
Dimensions
24 cm
Edition
First edition
Extent
vi, 123 pages
Isbn
9781491943823
Media category
unmediated
Media MARC source
rdamedia
Media type code
  • n
Other physical details
illustrations
System control number
  • (Sirsi) a547375
  • (OCoLC)962767795
Label
Programming beyond practices : be more than just a code monkey, Gregory T. Brown
Publication
Bibliography note
Includes bibliographical references and index
Carrier category
volume
Carrier category code
  • nc
Carrier MARC source
rdacarrier
Content category
text
Content type code
  • txt
Content type MARC source
rdacontent
Contents
Using Prototypes to Explore Project Ideas. Start by understanding the needs behind the project; Use wireframes to set expectations about functionality; Set up a live test system as soon as you start coding; Discuss all defects, but be pragmatic about repairs; Check your assumptions early and often; Limit the scope of your work as much as possible; Remember that prototypes are not production systems; Design features that make collecting feedback easy -- Spotting Hidden Dependencies in Incremental Changes. There's no such thing as a standalone feature. If two features share a screen, they depend on each other; Avoid non-essential real-time data synchronization; Look for problems when code is reused in a new context -- Identifying the Pain Points of Service Integrations. Plan for trouble when your needs are off the beaten path; Remember that external services might change or die; Look for outdated mocks in tests when services change; Expect maintenance headaches from poorly coded robots; Remember that there are no purely internal concerns -- Developing a Rigorous Approach Toward Problem Solving. Begin by gathering the facts and stating them plainly; Work part of the problem by hand before writing code; Validate your input data before attempting to process it; Make use of deductive reasoning to check your work; Solve simple problems to understand more difficult ones -- Designing Software from the Bottom Up. Identify the nouns and verbs of your problem space; Begin by implementing a minimal slice of functionality; Avoid unnecessary temporal coupling between objects; Gradually extract reusable parts and protocols; Experiment freely to discover hidden abstractions; Know where the bottom-up approach breaks down -- Data Modeling in an Imperfect World. Decouple conceptual modeling from physical modeling; Design an explicit model for tracking data changes; Understand how Conway's Law influences data management practices; Remember that workflow design and data modeling go hand in hand -- Gradual Process Improvement as an Antidote for Overcommitment. Respond to unexpected failures with swiftness and safety; Identify and analyze operational bottlenecks; Pay attention to the economic tradeoffs of your work; Reduce waste by limiting work in progress; Make the whole greater than the sum of its parts -- The Future of Software Development
Control code
ocn962767795
Dimensions
24 cm
Edition
First edition
Extent
vi, 123 pages
Isbn
9781491943823
Media category
unmediated
Media MARC source
rdamedia
Media type code
  • n
Other physical details
illustrations
System control number
  • (Sirsi) a547375
  • (OCoLC)962767795

Library Locations

    • Westlake Porter Public LibraryBorrow it
      27333 Center Ridge Rd, Westlake, OH, 44145, US
      41.447741 -81.924363
Processing Feedback ...