Perhaps I need to add a function to accommodate a specific item we didn't anticipate. This isn't a bug.

However if I have a function that does x,y,z and it turns out it can't do z or it doesn't do y as it should then we consider this a bug. We count these numbers and we ask each other to submit something that states their logic and design process. We also consider inadequate design or lack of a process a bug as well. Poor planning.

We also track time on how long it takes us to fix these bugs and implement the original design. We also ask each other for estimates on how long it would them to implement and we build a schedule on an average of these estimates.

I just ran the query for last year. I had 1 bug each quarter. One of the developers has 178. The last hire has almost 400.

I implemented a plan to reduce draw call overhead. It took me 3 months. That was almost double what other developers estimated it would take them. So far just one issue has been reported and it was more an error using to0 few words in the code comments but I added an `assert` just to warn the developer to look at this and I also fixed the code comments and provided an example.

Edit: Yes, higher ups do and look at this quarterly and I'm not sure what they do with the info to be honest.