Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Should We Do "Computer Science"? 4 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • * Communication skills (there's a reason I listed this one first) * Automated testing * Source control * Working in teams on new code * Working in teams on existing code * Multiple language paradigms * Complexity management * Usability * More that hasn't occurred to me in this brief write-up ...

    Computer science is as much about computers as astronomy about telescopes, right?

    Everything you wrote up here is explainable within a couple of days. Most of it requires lot

    • Re:No! (Score:1)

      by chromatic (983) on 2009.03.05 14:41 (#67711) Homepage Journal

      Everything you wrote up here is explainable within a couple of days.

      I'd love to hire super geniuses like the ones you've taught, but unfortunately the rest of the world isn't nearly that capable. Some ten years in, and I'm still figuring out the nuances of automated testing.

      • Nuances are nuances. You do understand the principle points of it, eh? You're a bright fellow. Just like we all can do division, but the larger the numbers, the easier it is to screw up, and it takes time when someone does something screwy.

        • I can explain the principal points of functional programming to my five year old nephew in a few minutes, but even Abelson and Sussman spent more time on it at MIT.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.