Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

Display Options Threshold:
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • Hey, C# is actually a pretty cool language. It shot the Java fish in the barrel, for example :)

  • I don't like the hype/cult around Joel either, but I'm still an avid reader of his articles because I find them funny, amusing and usually insightful, or otherwise giving good food for thoughts and acting as a useful starting point for further discussion of the matter. I don't always agree with what Joel says, and naturally buy everything he says with a grain of salt, but still find value in what he says.

    It seems there's often an opposite phenomenon from what you describe - that many times I mention something that Joel says for support someone gives an ad-hominem attack [] saying how much Joel sucks and how much it means my article is invalid.

    If you have specific arguments against what Joel (or whoever) said, feel free to mention them giving proper reasons for why you think they are wrong. But from my impression of your Internet persona, you tend to throw many arguments into the air without giving proper explanation or reasoning (like "I disagree. What you said or your link sucks."), and expect us to guess why you think so. To do so is anti-intellectual, and I can easily dismiss what you said for lack of proper reasoning.

    Now I tend to agree with you and Ovid (and the article he quoted) about education, and that it's impossible to teach everything within the scope of the degree, or that high education (or below) can fully prepare people and make them suitable for the job market. I wouldn't accuse Joel of trying to sell his tools on purposes - that doesn't seem to be his primary motivation behind his post, but he still may believe he knows too well how to do things the right way.

    I may have errored with the same error, when I claimed that too little focus is given on reading "real-world code" [], which may not be the most elegant, and may be somewhat buggy. One constantly hear people complain about how bad the code that they work or what other people have written is, and how they would love to start over. (This was in fact inspired by what Joel said in "Things you Must Never Do, Part I" []). In their studies, most people are not exposed to having to read and improve real code, which may be hard-to-read inelegant, or somewhat buggy, but which rewriting it from scratch will be much more time consuming than improving it by writing automated tests, refactoring, etc. In any case, there's little focus given to it in the universities, but I'm not sure if putting it in the curriculum will be a good idea. Maybe giving more projects where students contribute to open-source code (and not necessarily the best open-source code out there - there's a lot that's pretty bad), and then eventually merging it in, instead of writing something from scratch would be a good idea.

    But I agree that measuring universities based on metrics is bad.