4 ms·
Your feedback isn't very constructive, and reflects poorly on your time management skills. 200 bugs is just two bugs per week for two years. At three hours per
by DevFactor 12y ago
Your feedback isn't very constructive, and reflects poorly on your time management skills.
200 bugs is just two bugs per week for two years. At three hours per bug, that's 6 hours per week - 312/yr and 614 total. Significantly less than a college degree.
Alternatively, spend some time learning to code: https://www.youtube.com/devfactor https://www.youtube.com/devfactor - build some cool projects and present them to your employer.
- cpncrunch 12y agoI think that's a bit optimistic. To be honest I don't come across that many bugs in open source software. Google and Apple products, yes, but I generally don't have access to their source. Right now there are just a couple of open source bugs that are annoying me, but each of those would likely take me at least a few weeks of full-time work to track down. IMO you're much better actually building something impressive rather than fixing a bunch of bugs if you're looking for a job.