However! I see a lot of developers who would have a hard time fixing a bug / making a small change in an area which has a lot of legacy cruft present without going and rewriting the whole thing. Now, they are right that rewriting it is probably the best course of action from a codebase-health viewpoint... but it's not necessarily the actual best use of their time. If code is working then it's not an urgent priority that it get rewritten.
To be slightly trite, "perfect is the enemy of good."
That's why we'd like to get developers who are okay with the idea of working on a codebase that contains legacy code. And that's why I'm a little bit over the top about it.
What kind of working environment do you have that in a team of less than 25, a member of that team can be that far off-base?
Also I'm bad at estimating these things apparently. :P
They're also not the only company that has a "We're Hiring" post in each of these threads which strikes me as a good thing--assuming the term of employment for new developers is longer than a month. :)