24th May 2012

The Ten Networking Commandments

Although my version would be slightly different, I think this covers the major elements. If you run a Network team using these as a basis for business planning and operational excellence then you will be successful.

The Ten Networking Commandments

1. Thou shalt above all, maintain the integrity of the network.
2. Thou shalt have a long term strategic direction.
3. Thou shalt always opt for quality before expediency.
4. Thou shalt meet the requirements, exceed the expectations and anticipate
the needs of users.
5. Thou shalt benefit from a successful implementation by careful project
planning.
6. Thou shalt provide reliability, availability and serviceability.
7. Thou shalt maintain detailed, timely and accurate documentation.
8. Thou shalt commit to continuous training.
9. Thou shalt test in a test environment.
10. Thou shalt install and label cables properly.”
1080103_old_hebrew_prayer_book.jpg
Source:
The 10 Networking Commandments

Image Credit
This post is copyright of Thropos Ltd ©2008-2011 at Etherealmind.com - contact | email: greg.ferro@packetpushers.net - twitter: @etherealmind | All rights reserved
About Greg Ferro

Greg Ferro is a Network Engineer/Architect, mostly focussed on Data Centre, Security Infrastructure, and recently Virtualization. He has over 20 years in IT, in wide range of employers working as a freelance consultant including Finance, Service Providers and Online Companies. He is CCIE#6920 and has a few ideas about the world, but not enough to really count.

He is a host on the Packet Pushers Podcast, blogger at EtherealMind.com and on Twitter @etherealmind and Google Plus

  • Randy Pope

    Amen

  • http://alouche.net Ali

    11. Thou shall not covet thy Neighbor’s network
    (unless it is to improve yours :-P )

    Heh Greg, who said Networkers’s weren’t spirituals ;-)

  • http://datacenterguy.com Steve D

    For me, you’ve left out the #1 rule, which can be said a number of ways.

    -Complexity, while sometimes a necessity, should be avoided.
    -Keep it simple stupid.
    -Complexity is the enemy of supportability
    -Just because you can, doesn’t mean you should

    The other thing I think I would add is:

    Know thy applications.

  • loopback0

    I see #7 – #10 violated by many engineers…feel it is beneath them…