StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHow to make a program bug-free (or, with the less possible bugs)
text
Body
copied!<p>OK, I know it's a stupid question to ask, so let me clarify.</p> <p>My boss thinks that, "by now, with your level of knowledge, you should never have bugs in your software anymore". While it may be correct, given the correct set of tools and with a proper method, those are never allowed to me, maybe because I don't know what to answer him exactly (I'm the only developer here, so I don't have anyone to turn to when it happens).</p> <p>So, here is my question : what tools and methods do you use to have the less possible bugs in your software ?</p> <hr> <p>Bottom line : a code without any error is impossible. However, here is what is possible to do :</p> <h2><a href="http://en.wikipedia.org/wiki/Software_testing" rel="nofollow noreferrer">Testing</a></h2> <ul> <li><a href="http://en.wikipedia.org/wiki/Test_driven_development" rel="nofollow noreferrer">Test-driven development</a></li> <li><a href="http://en.wikipedia.org/wiki/Unit_testing" rel="nofollow noreferrer">Unit testing</a></li> <li><a href="http://en.wikipedia.org/wiki/Automated_testing" rel="nofollow noreferrer">Automated testing</a></li> <li>Functionnality testing</li> <li><a href="http://en.wikipedia.org/wiki/Mutation_testing" rel="nofollow noreferrer">Mutation testing</a></li> <li>Test by a team and <a href="http://en.wikipedia.org/wiki/Hallway_testing#Hallway_testing" rel="nofollow noreferrer">bypassers</a></li> </ul> <h2>Tools</h2> <ul> <li><a href="http://en.wikipedia.org/wiki/Source_control" rel="nofollow noreferrer">Source control</a></li> <li><a href="http://en.wikipedia.org/wiki/Integrated_development_environment" rel="nofollow noreferrer">Good editor / IDE</a></li> <li><a href="http://en.wikipedia.org/wiki/Bugtracker" rel="nofollow noreferrer">Bugtracking software</a></li> <li><a href="http://en.wikipedia.org/wiki/Static_code_analysis" rel="nofollow noreferrer">Static code analysis</a></li> </ul> <h2>Practices, management, environment</h2> <ul> <li><a href="http://en.wikipedia.org/wiki/Code_coverage" rel="nofollow noreferrer">Code coverage</a></li> <li><a href="http://en.wikipedia.org/wiki/Software_peer_review" rel="nofollow noreferrer">Peer code review</a></li> <li>Assertions to check assumptions</li> <li><a href="http://en.wikipedia.org/wiki/Continuous_integration" rel="nofollow noreferrer">Continuous integration</a></li> <li><a href="http://en.wikipedia.org/wiki/Scrum_(development)" rel="nofollow noreferrer">Development stages</a></li> <li><a href="http://en.wikipedia.org/wiki/Zen" rel="nofollow noreferrer">No distractions while working</a></li> <li><a href="http://en.wikipedia.org/wiki/Time" rel="nofollow noreferrer">Time</a></li> </ul>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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