Real World Code Sucks 292
An anonymous reader tips an article at El Reg about the disparity between the code you learn at school and the code you see at work. Quoting:
"There is 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."
Obligatory XKCD (Score:5, Funny)
Re:same... (Score:4, Funny)
And English class samples (such as books and essays that they have you read) versus the comments you read on YouTube.
Re:From the article (Score:5, Funny)
The last page bashes Haskell using a snippet from Uncyclopedia as anecdotal evidence that it is "all but impossible to write readable code" in Haskell.
Beyond it is another dimension: a dimension of whinge, a dimension of fallacy, a dimension of diminished journalistic integrity. You're moving into a land of more shadow than substance, of vague and half-baked wit; you've just crossed over into the Register.
Re:Captain Obvious? (Score:5, Funny)
Re:Captain Obvious? (Score:5, Funny)
* Meskimen's Law: There's never time to do it right, but always time to do it over.
* Ninety-Ninety Rule of Project Schedules: The first ninety percent of the task takes ninety percent of the time, and the last ten percent takes the other ninety percent.
http://www.panopticoncentral.net/2010/08/01/murphys-computer-law/ [panopticoncentral.net]