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

use Perl Log In

Log In

[ Create a new account ]

Beatnik (493)

  (email not shown publicly)

A 29 year old belgian who likes Mountain Dew, Girl Scout Cookies, Tim Hortons French Vanilla Flavoured Cappucinno, Belgian beer, Belgian chocolate, Belgian women, Magners Cider, chocolate chipped cookies and Perl. Likes snowboarding, snorkling, sailing and silence. Bach can really cheer him up! He still misses his dog.

Project Daddy of Spine [], a mod_perl based CMS.

In his superhero time (8.30 AM to 5.30 PM), he works on world peace.

Journal of Beatnik (493)

Friday February 20, 2004
06:50 AM

Teaching networking

[ #17515 ]
I asked this on /. but they dropped my request... Anyway in short: I'm teaching Networking basics in evening school. I want to add quite a bit of practical sections to my course. The classroom has no computers in it but I can bring all the required material from work. How can I make a mostly theoretical course less boring? I already brought along cables and got em making cross cables.

I'm open for suggestions :)
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • ...this was the problem in my networking class -- nothing but theory and examples, because they didn't really have any way we could test most of what we were talking about.

    You are what you think.
  • What aspects of networking will you be instructing? LAN switching, WAN routing, Server services, Client applications, security, IP addressing and netmasking, alloftheabove?

    If it's server and client interaction stuff, then VMware might be nice. Or if infrastructure then you about need one router or switch for every two students.

    I know it can be trite and cliched, but getting peeps to think in an OSI model layered approach can make for muchmuchmuch more effective troubleshooters - ie; don't try to debug t
    • I'm discussing cabling types, OSI layers, Ethernet, Token Ring, ATM, FDDI, TCP, UDP,.. The works. There are things I have to repeat a lot but that's probably because a) I'm not as experienced in teaching b) It's quite boring. The course has a 20 page section on Token Ring. 20 pages is probably not a lot but it's boring :) Most of my students have no background in IT so it's like learning Swahili to a bicycle :)