All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

Please Log In to Continue

* 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

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.