Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I am not sure what counting your bugs is going to do with out something to compare it with. What if the software you made was very hard and had lots of edge cases? You need some kind some kind of comparison...</p> <p>Even though one of the other answers was clearly a joke code reviews are also probably a good idea. If you have too many bugs hire better engineers or have them write less code.</p> <p>Edit: Added after considering comments...</p> <p>Every bug is a like a unique sucky snow flake (a suckflake?). They have different levels of impact on your customers and developers. I would at least take this into account. Maybe adding severity (a measure of customer push for fix) and engineering hours spent fixing it might help improve accuracy. My concern I guess is that this is still over simplification of "quality" when it comes to developing software. </p> <p>Sadly software quality != product quality. A recently released game called Fallout 3 won tons of awards and made lots of money (at least I assume) but was also a buggy hunk of junk on PC at least. </p> <p>Just make sure you are tracking and optimizing the correct thing. Tracking # bugs vs time is just tracking # of bugs vs time. Reading any more into it requires some level of assumption however correct or incorrect.</p> <p>What are your goals? Bugs are but one part of software quality. If you want to continue you to support your software maintainability is key. A lot of times bug fixes can make things less maintainable if your coder did things in a rush. This in turn makes future fixes and features harder and fixes can add new bugs.</p>
    singulars
    1. This table or related slice is empty.
    1. POTracking and prediciting quality level
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USfuzzy-waffle
    1. USfuzzy-waffle
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COA couple of people responded that they did not understand how bug rates are meaningful. On the Y axis, chart the total number of bugs found. On the X axis, chart time. Over the course of development and test the graph forms an S. A flattening curve can predict quality when you will be bug free.
      singulars
      1. PO
      1. This table or related slice is empty.
    2. COA measure of quality is not in the bug rate itself but in its evolution, i.e., its derivative. This shows that the code gets better (or worse).
      singulars
      1. PO
      1. USmouviciel
    3. COAs fuzzy said, it's only meaningful if the concept of a bug is rigidly defined, which is both difficult to do and asinine.
      singulars
      1. PO
      1. USBenson
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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