01.02.2013 Views

Software Development Cross Solution - Index of - Free

Software Development Cross Solution - Index of - Free

Software Development Cross Solution - Index of - Free

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

CHAPTER 11<br />

414 Chapter 11<br />

Tools for your <strong>S<strong>of</strong>tware</strong> <strong>Development</strong> Toolbox<br />

<strong>S<strong>of</strong>tware</strong> <strong>Development</strong> is all about developing<br />

and delivering great s<strong>of</strong>tware. In this chapter,<br />

you learned how to debug like a pro. For a<br />

complete list <strong>of</strong> tools in the book, see Appendix ii.<br />

<strong>Development</strong> Techniques<br />

Before you change a single line <strong>of</strong> code,<br />

make sure it is controlled and buildable<br />

When bugs hit code you don’t know, use a<br />

spike test to estimate how long it will take<br />

to fix them<br />

Factor in your team’s confidence when<br />

estimating the work remaining to fix bugs<br />

Use tests to tell you when a bug is fixed<br />

Here are some<br />

<strong>of</strong> the key<br />

techniques you<br />

learned in this<br />

chapter...<br />

<strong>Development</strong> Principles<br />

Be honest with your customer, especially<br />

when the news is bad<br />

Working s<strong>of</strong>tware is your top priority<br />

...and some <strong>of</strong> the<br />

principles behind<br />

those techniques.<br />

Readable and understandable code comes a<br />

close second<br />

If you haven’t tested a piece <strong>of</strong> code,<br />

assume that it doesn’t work<br />

Fix functionality<br />

Be proud <strong>of</strong> your code<br />

All the code in your s<strong>of</strong>tware, even the<br />

bits you didn’t write, is your responsibility<br />

Download at WoweBook.Com<br />

�<br />

�<br />

�<br />

�<br />

�<br />

Before you change a<br />

single line <strong>of</strong> code, take<br />

ownership <strong>of</strong> it by adding it<br />

into your build process and<br />

putting it under source code<br />

management.<br />

Take responsibility for all<br />

the code in your s<strong>of</strong>tware.<br />

If you see a problem, then<br />

don’t cry “it’s someone else’s<br />

code”; write a test, then fix<br />

it.<br />

Don’t assume a single line<br />

<strong>of</strong> code works until there is<br />

a test that proves it.<br />

Working s<strong>of</strong>tware comes<br />

first; beautiful code is<br />

second.<br />

Use the pride test. If you’d<br />

be happy for someone else<br />

to read your code and rely<br />

on your s<strong>of</strong>tware, then it’s<br />

probably in good shape.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!