Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You don't necessarily have to spend 20% of your time fixing bugs litteraly, but - yes - most programmers have to face the problem of bug fixing. Hopefully you'll be able to spend less than 20% on your time bug fixing, if you're not careful it might even take more of your time. </p> <p>No matter how good a programmer you are it is highly likely that you'll introduce a few bugs at some time. If you're diciplined with <a href="http://en.wikipedia.org/wiki/Unit_testing" rel="nofollow noreferrer">unit testing</a> you can hopefully avoid bugs best possible. I highly recommend you to look into <a href="http://en.wikipedia.org/wiki/Test-driven_development" rel="nofollow noreferrer">Test Driven Development</a> (TDD) if you want to do your best for avoiding bugs. </p> <p>There are several questions about unit testing and TDD on StackOverflow if you need help getting started. Here are a few of them: </p> <ul> <li><a href="https://stackoverflow.com/questions/67299/is-unit-testing-worth-the-effort">Is unit testing worth the effort</a></li> <li><a href="https://stackoverflow.com/questions/1742323/tdd-vs-unit-testing">TDD vs Unit Testing</a></li> <li><a href="https://stackoverflow.com/questions/1365943/how-to-start-unit-testing-or-tdd">How to start unit testing or TDD</a></li> <li><a href="https://stackoverflow.com/questions/917334/should-i-use-tdd">Should I use TDD?</a> </li> <li><a href="https://stackoverflow.com/questions/1195230/getting-started-with-tdd">Getting started with TDD</a></li> <li><a href="https://stackoverflow.com/questions/163454/getting-started-with-tdd-interfaces-and-mockups">Getting started with TDD, interfaces and Mockups</a></li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload