July 2003
Intermediate to advanced
106 pages
2h 11m
English
Content preview from Extreme Programming Pocket GuideBecome an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Chapter 22. Starting Feedback
As your team continues to improve, start gathering feedback. This will allow you to see change occurring and to adapt to it. If you’re fortunate enough to have a customer right now, great! Getting her feedback will help guide your development. If not, you can still learn from the feedback loops within the coding process.
The most important question right now is “Does the code work?” The only way to know is to test it (see Developer Practice 1: Adopt Test-Driven Development in Part II). Test-driven development will give you immediate confidence that the current code acts as it should and long-term assurance that new bugs and regressions can be fixed quickly. You must trust each other to write new tests, to run existing tests, and to fix broken tests.
It’s much easier to start testing from the beginning, but few projects have that luxury. Halting new development to add tests retroactively is unpleasant and time consuming. Instead, adopt test-driven development for all new features, including bugfixes.
Writing a test for a bug before you fix it has several benefits. First, it defers the cost of retroactive testing until it’s needed. Noticing the bug tells you the code is wrong. Capture that knowledge in a test! Second, it adds tests where they’re most needed. Third, it prevents the bug from reoccurring. (Too often bugs are fixed and subsequently unfixed several times.) The buggiest—likely ugliest—sections of your code will benefit from ever-improving test ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.