There are an awful lot of people following what I'd call (hat tip to Travis for this phrasing) "solution oriented development - by which I mean, "keep pounding on the code until it works". That's fine for smaller apps, but tends to get you into trouble (in maintenance terms) down the road. The latest example: Facebook, which has suffered a code leak:

The second implication with this leak is that the source code reveals a lot about the structure of the application, and the practices that Facebook developers follow. From just this single page of source code a lot can be said and extrapolated about the rest of the Facebook application and platform. For instance, the structure doesn’t follow any object oriented development practices, and it seems that the application is one large PHP file with a large number of custom functions living in the same namespace (they also seem to be using the Smarty templating engine).

I'd guess that the same could be said about a lot of running code out there.