One of the more unpleasant lessons learned now that I code in a team/professionally is that the vast majority of bugs I fix, even in 'my applications', are not from anything I wrote. It makes sense really. The new guy is going to have written less code than veteran team members; old code is more likely to have its assumptions broken; old paradigms are 'old' because they cause bugs; immature companies will generally have more bugs due to worse processes...
Unfortunately I'm someone who's big into personal responsibility. You create the problem, you fix it. Someone else fixes your problem, it's a favor. This was all nice and good doing sys admin work. I setup the machines I had purview over so if they blew up, I got the call at 4 am.
Not so much doing group software development (at least as I've been dealt it). I mean, I could spew emails 'hey, fix your crap!' to the people who're still with the company... not exactly a good move for the inexperienced new guy.
It's something new that I'm going to have to learn how to deal with, without becoming untrusting or too overly cynical about the local code quality. And I suppose the majority does work; and that's what's important, right?
Yeah...
