Download Safari Books Online apps: Apple iOS | Android

Entire Site

Safari Books Online

    Free Trial

    Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.


    Head First Software Development
    Dedication
    A Note Regarding Supplemental Files
    Advance Praise for Head First Software Development
    Praise for Head First Object-Oriented Analysis and Design
    Praise for Head First Design Patterns
     
    How to use this Book: Intro
    1. Great Software Development: Pleasing your customer
    2. Gathering Requirements: Knowing what the customer wants
    3. Project Planning: Planning for success
    4. User Stories and Tasks: Getting to the real work
    5. Good-Enough Design: Getting it done with great design
    6. Version Control: Defensive development
    You’ve got a new contract—BeatBox Pro
    And now the GUI work...
    And a quick test...
    And Bob does the same...
    Demo the new BeatBox for the customer
    Standup meeting
    Let’s start with VERSION CONTROL
    First set up your project...
    ...then you can check code in and out.
    Most version control tools will try and solve problems for you
    The server tries to MERGE your changes
    If your software can’t merge the changes, it issues a conflict
    Now show the customer...
    More iterations, more stories...
    Standup meeting
    We have more than one version of our software...
    Good commit messages make finding older software easier
    Now you can check out Version 1.0
    (Emergency) standup meeting
    Tag your versions
    Tags, branches, and trunks, oh my!
    Fixing Version 1.0...for real this time.
    We have TWO code bases now
    When NOT to branch...
    We fixed ersion 1...
    ... and Bob finished ersion 2.0 (so he says)
    Version control can’t make sure your code actually works...
    Tools for your Software Development Toolbox
    7. Building your Code: Insert tab a into slot b...
    8. Testing and Continuous Integration: Things fall apart
    9. Test-Driven Development: Holding your code accountable
    10. Ending an Iteration: It’s all coming together...
    11. The Next Iteration: If it ain’t broke... you still better fix it
    12. Bugs: Squashing bugs like a pro
    13. The Real World: Having a rocess in life
    A. Leftovers: The top 5 topics (we didn’t cover)
    B. Techniques and Principles: Tools for the experienced software developer
    Index
    About the Authors
    Copyright
    • Create BookmarkCreate Bookmark
    • Create Note or TagCreate Note or Tag
    • PrintPrint
    Share this Page URL
    Help

    6. Version Control: Defensive developmen... > We have more than one version of our...

    We have more than one version of our software...

    The real problem here is that we have more than one version of our software—or more accurately, more than one version of our source code—that we need to make changes to. We have version 1.0 of the code built and out there, but Bob found a pretty serious bug. On top of that, we’ve got version 2.0 in the works, but it’s full of untested, unworking features.

    We need to separate them somehow...

    image with no caption

    You’ll always have tension between bugs cropping up in released versions, and new features in upcoming versions. It’s up to you to work with the customer to BALANCE those tensions.

    Bullet Points

    • Bugs to released versions are usually a higher priority to the customer than implementing new features.


      

    You are currently reading a PREVIEW of this book.

                                                                                            

    Get instant access to over
    $1 million worth of books and videos.

      

    Start a Free Trial