Is spent troubleshooting or finding bugs, not fixing them, etc.
If your primary job responsibility is bug squasher please indicate so in the replies.
Cheers,
Alex
How much of your day
Moderator: General Moderators
-
alex.barylski
- DevNet Evangelist
- Posts: 6267
- Joined: Tue Dec 21, 2004 5:00 pm
- Location: Winnipeg
- Jonah Bron
- DevNet Master
- Posts: 2764
- Joined: Thu Mar 15, 2007 6:28 pm
- Location: Redding, California
Re: How much of your day
I voted 30%, but thinking about it, it's probably closer to 20%. I actually like the challenge of a good (bad) bug.
The other 70% is on Devnet
The other 70% is on Devnet
- John Cartwright
- Site Admin
- Posts: 11470
- Joined: Tue Dec 23, 2003 2:10 am
- Location: Toronto
- Contact:
Re: How much of your day
Probably around 10%. Unit tests + QA department + Testing department handles most of this for me.
Most of the bugs I'll come across are usually from integration testing, which are basically impossible to predict.
The other 90% on devnet.
Most of the bugs I'll come across are usually from integration testing, which are basically impossible to predict.
The other 90% on devnet.
-
alex.barylski
- DevNet Evangelist
- Posts: 6267
- Joined: Tue Dec 21, 2004 5:00 pm
- Location: Winnipeg
Re: How much of your day
I love how you guys mentioned DN as a time consumer. If you are lucky enough to have a QA department, I would be curious to know how much time relative to the whole of a project, was spent on finding bugs.
I have for years, invested a great deal of personal (and company) time trying to record/calculate metrics to monitor my performance
Cheers,
Alex
It's important to note I meant specifically the diagnosis of a bug, not finding it, or solving it. Rather, you found a bug (or customer), logged it in a bug tracker, estimated it's time to completion/correction. It's this actual time spent diagnosing a bug, figuring out what is wrong, that I am trying to better understand.I actually like the challenge of a good (bad) bug.
I have for years, invested a great deal of personal (and company) time trying to record/calculate metrics to monitor my performance
Cheers,
Alex
- John Cartwright
- Site Admin
- Posts: 11470
- Joined: Tue Dec 23, 2003 2:10 am
- Location: Toronto
- Contact:
Re: How much of your day
It's a tough one to answer because it varies from bug to bug. For instance, we have a bug with our event processing system which is sending multiple emails for a specific event. However, it is a lot more complicated than that because it involves a server farm with file based and MySQL replication, among other complications. We have a team that has been working on this for 2 weeks.
On the other hand, bugs in the codebase are generally squashed very quickly (minutes) because of unit testing.
I would say Unit Tests are the biggest time saver when it comes to bugs in the code. The upfront time costs are nothing compared to the time you'll save when working with a heavily developed and large codebase to identify bugs.
On the other hand, bugs in the codebase are generally squashed very quickly (minutes) because of unit testing.
I would say Unit Tests are the biggest time saver when it comes to bugs in the code. The upfront time costs are nothing compared to the time you'll save when working with a heavily developed and large codebase to identify bugs.
Re: How much of your day
We write software to solve problems, so 100% :p
But seriously, about 40% of my time is spent on deviations. A very small percentage of that is bugs, most of it refactoring and removing code smells.
But seriously, about 40% of my time is spent on deviations. A very small percentage of that is bugs, most of it refactoring and removing code smells.