Yes, and unfortunately, you do see this crap occasionally. They're usually the guys who can't solve an easy top coder problem within an hour, but will gladly take an hour to explain why the 13 design patterns they used to parse a simple test file are necessary. They're obsessed with decoupling everything, design patterning everything, middleware everything, documenting everything. All this guy is really saying is that unit testing isn't idiot proof.
[offtopic]BTW, I'm officially gonna recommend TopCoder to any newbie wanting to learn a language.[/offtopic]
What you described above was my time at JPMorgan Chase.
I always struggled comprehending developers. When I came out of college, I knew all these algorithmic stuff but not patterns...in the real world (at least at Chase), they told me that the Pattern gods would hate me if I didn't include at least one pattern in my code.
I never really learned patterns, I don't really implement them in my code base but my obsession to decouple everything stems from creating simple objects. Less is more, I say. It's easier to test and mock decoupled objects. I prefer to test behavior and making sure that my objects do as they're supposed too.