Normalization is not an incorrect model for designing and implementing databases - it's actually used and useful. Achieving first normal form or second normal form is not hard, and leads to efficiencies, and is used every day, even if further normalization isn't used as much.
Aside from X.400, it's hard, if not impossible, to cite an actual implementation of the OSI model. Kurt On Wed, May 26, 2010 at 21:47, Ken Schaefer <[email protected]> wrote: > Agreed. > > You don't need to know OSI to be able to put some network infrastructure > together. You don't need to know normalisation to design a database. You > don't need to know OOP to write an application. But all of this theory is > quite useful in doing things in a better way, because they provide frameworks > that have been around for a long time, which many people are familiar with, > and which haven't been replaced with something better yet. And as you acquire > new knowledge, they provide the background info that lets you see how it all > hangs together. > > Cheers > Ken > > -----Original Message----- > From: Erik Goldoff [mailto:[email protected]] > Sent: Thursday, 27 May 2010 10:01 AM > 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/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
