WANT: Tech support for knives!!!! (networking)

Walking Man

Walking Man

BANNED
Feedback: +3 / =0 / -0
Joined
May 28, 2003
Messages
9,606
Hello, everyone.
I have almost graduated from a community college with an associate's in Comp. Network, but I am so disappointed in my education and I feel like I don't know nearly as much as I should. I'll probably be getting a job soon, and I thought that the best thing to do is to find someone on the inside that might be able to help me out when I need.
I'd like to trade some knives for the ability to call you for help in limited quantites. Maybe something like: once during the work week, and three times nights or weekend. I really need your help, I paid a WHOLE LOT of money for this "education" and I feel really insecure. They had exactly (0) servers in the building and didn't even get server installed on any machines until 3 months into the program (3/6 months of networking classes), and they didn't even give us A+. So think about it, I have some nice stuff, nothing in the 800+ range, but stuff that I think any knife lover would enjoy.
thanks for your time.
 
Okay,
also, I don't have the job yet,
so I don't know 100% that I'll need the help.
more later.
thanks.
 
Walking man, depending on which segment of "network comp." you're aiming at there are differen resources far more usable to learn from than your average course hosted by money-craving gmps who don't have a slightest idea as to what they are blurbing about.

If you're into network [applicaton] programming i'd recommend you Richard W. Stevents: Unix network programming (latest edition avaliable, the man is unfortunately dead) - title aside, this book isn't really Unix-specific but it is a bible of network programming. They don't get any better than that, it also faces other aspects (various concepts of daemon writing, such as forked versus threaded, versus pre-threaded, etc.).

If you're into regular network administration youll probably get the best bang for your buck out of [free] projects such as Linux (*BSD, etc.). Gather old hardware that can be networked (various architectures and heterogenous systems) and make it work together - learning by example, nothing beats it.

If yur course was meant as strictly M$-centric crap you'd be well off with #2, excluding the heterogenous environment part. You'd be surprisedto know how crappy M$ courses are and how much one learns trying to interface an implementation ("a knockoff") of buggy crappy ****** M$ piece of canine poo to "the real thing" (buggy crappy ****** M$ piece of canine poo). Such is life.

Classes are no approximation for the real life - i'm young (compared to quite some forum members) and i know that. Whatever they taught you there, learn how to use it in practice. In the end the titles mean very little, what you know and what you can do is what matters. Make use of whatever you learned and use the avaliable low-cost solutions to LEARN MORE.

Good luck !!!

*edit* who would have guessed that $hitty is a censored word (especially when referring to $****** M$ products). Anyway, i wanted to add this: i'm not a know-it-all but i do know a thing or two about networking, if you have any questions feel free to drop me a line :D
 
You must log in or register to reply here.
Back
Top