Saturday, December 22, 2012

Real World Code Sucks...

Dave Mandl writes (intro):
There’s a kind of cognitive dissonance in most people who’ve moved from the academic study of computer science to a job as a real-world software developer. The conflict lies in the fact that, whereas nearly every sample program in every textbook is a perfect and well-thought-out specimen, virtually no software out in the wild is, and this is rarely acknowledged.

To be precise: a tremendous amount of source code written for real applications is not merely less perfect than the simple examples seen in school — it’s outright terrible by any number of measures.

Due to bad design, sloppy or opaque coding practices, non-scalability, and layers of ugly “temporary” patches, it’s often difficult to maintain, harder still to modify or upgrade, painful or impossible for a new person joining the dev team to understand, or (a different kind of problem) slow and inefficient. In short, a mess.
His experience matches my own, at least for any body of code that wasn't written by a single individual (that's nearly everything these days, as software keeps getting bigger and more complex).

But for the most part, it works anyway – which some might consider to be an inexplicable miracle...

No comments:

Post a Comment