The "switch to something else to fix a bug" strategy is clearly unsustainable. What do you do when you find a bug in chrome then? Switch back to firefox? Switch to opera first before you switch back to firefox? Just change browsers every month in the hope that they all have different bugs?
(chrome has plenty of bugs: the latest update on linux has a tendency to hang and use 100% cpu in some glib functions)
On the other hand to do changes to large code bases on short notice is a big asset to your programming skills. See it as a challenge. It's well something you could put up on your resume.
Often the main challenge is just to find the code, and if
you can't do that can you deal with any other non toy
code bases? Once you found it a lot problems are easy.
(chrome has plenty of bugs: the latest update on linux has a tendency to hang and use 100% cpu in some glib functions)
On the other hand to do changes to large code bases on short notice is a big asset to your programming skills. See it as a challenge. It's well something you could put up on your resume.
Often the main challenge is just to find the code, and if you can't do that can you deal with any other non toy code bases? Once you found it a lot problems are easy.
nn -- (who has one patch in Firefox)