Understanding databases falls into the same category in my opinion. Some things I run into I can make sense of only because of days of using dBase IV to catalog and categorize my albums. Knowing the difference between a record and a row is sometimes the difference between comprehending it or not, for example.
Dave -----Original Message----- From: Erik Goldoff [mailto:[email protected]] Sent: Wednesday, May 26, 2010 7:01 PM To: NT System Admin Issues Subject: RE: Veering even more OT - was: Re: Big Changes Ahead for IT - Anyone seen this? It all comes down to this : The OSI model is part of the 'fundamental' knowledge. It's not 100% required to learn concepts above and more accurate, but it *does* provide a great background for learning and applying the knowledge you do gain. Erik Goldoff IT Consultant Systems, Networks, & Security ' Security is an ongoing process, not a one time event ! ' -----Original Message----- From: Ken Schaefer [mailto:[email protected]] Sent: Wednesday, May 26, 2010 9:54 PM To: NT System Admin Issues Subject: RE: Veering even more OT - was: Re: Big Changes Ahead for IT - Anyone seen this? OSI, per se, doesn't help anyone do anything. But it provides a framework, so that when you're discussing some problem with another engineer/architect/PM and they say "why don't we do 'x'?" you can draw up something quick and say: "the problem is here: +- | <- what you are talking about +- | +- | <-problem is here +- This can help when architecting an encryption solution, or when you're troubleshooting some network issue. It provides a hierarchy of requirements (upper levels are not going to work if something lower in the stack isn't). Cheers Ken ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
