Is network field only about memorizing commands ???

fawadn_84

hello .
sorry for new question

i really want to know this thing ???

IS NETWORK FIELD ONLY ABOUT MEMORIZING COMMANDS ???

which network field have something creative ?
\
thank you

gosh1976

First, no the network field is not just about memorizing commands. Those commands are almost useless without a solid understanding of network fundamentals and the theory behind it.

In my opinion troubleshooting requires a certain amount of creativity. The best techs regardless of what technologies they are working on will have a solid understanding of the fundamentals, have a solid grasp of the practical side such as what commands to use when, and they will have a creative side that allows them to come up with solutions that may not be immediately obvious. Oh, and the last skill is the ability to google.

I suppose someone in the network field working for a managed services company or a consultant that is heavily involved in network design would have the greatest opportunity for creativity.

Turgon

fawadn_84 wrote: »

hello .
sorry for new question

i really want to know this thing ???

IS NETWORK FIELD ONLY ABOUT MEMORIZING COMMANDS ???

which network field have something creative ?
\
thank you

Absolutely.

write erase
reload

It's all you will ever need.

Chipsch

Turgon wrote: »

Absolutely.

write erase
reload

It's all you will ever need.

Thats what I always do . Thanks for the laugh Turgon, needed it after pouring through this huge trace file this morning.

instant000

fawadn_84 wrote: »

hello .
sorry for new question

i really want to know this thing ???

IS NETWORK FIELD ONLY ABOUT MEMORIZING COMMANDS ???

which network field have something creative ?
\
thank you

Is network field only about memorizing commands? No.

Which network field has something creative? All of them.

Gosh1976 gave best answer to your question.

Turgon gave most comical answer to your question.

To expound on the "creative" thing, look at this earlier thread you posted:

http://www.techexams.net/forums/jobs-degrees/65899-confused-about-future-please-help-me.html

phantasm

As the others have said it is not about memorizing commands. I can teach anyone the commands to configure BGP and OSPF, but without understanding why they're using the specific set of commands they're useless. In the end they will do more damage than good.

The networking field, beyond the NOC environment, is about creaitivity and problem solving. That's what you're hired to do; solve problems and design creative solutions to meet the needs of the organization.

GT-Rob

I actually spend very little time these days on the command line. I wouldn't be surprised if I go a week without logging into something. Other than during changes and when things are 'broken' really, which thankfully isn't too often!


Lots of meetings. Design. Service requests where someone asks 'can we do this?", and you have to come up with how (notice how I didn't say come up with if it can be done? because it always CAN be done!).


But as stated, the technologies are what you have to understand. The commands are just how you put the butter on the bread.

Turgon

GT-Rob wrote: »

I actually spend very little time these days on the command line. I wouldn't be surprised if I go a week without logging into something. Other than during changes and when things are 'broken' really, which thankfully isn't too often!


Lots of meetings. Design. Service requests where someone asks 'can we do this?", and you have to come up with how (notice how I didn't say come up with if it can be done? because it always CAN be done!).


But as stated, the technologies are what you have to understand. The commands are just how you put the butter on the bread.

Thats essentially where the monied networking careers are these days, in design as opposed to operations. In design you need to understand technology capabilities but critically also the operational realities of what you have on your hands. A strong operations background can help you relate here and *potentially* makes you a better designer. I say potentially because operations and design are not the same vehicles. The requirements you have to work with on both sides can vary greatly and sometimes conflict.

But I still believe a good designer should know his way around a box. Not by memorising commands but by understanding capabilities and implementations. In operations you dont want to be memorising commands either but there is a problem of perception here where so many people believe that this is what operations has been reduced to. This is reflected both in the paychecks operations staff receive and in the disparaging way many operations teams are treated, by I might add, not only managers and customers but also poor designers.

The more reponsibility you have for configuring a platform and keeping it running, the stronger you need to be on understanding what commands actually *do* to a box as opposed to simply knowing what command you need to get something *done* i.e to close a ticket to provision a VLAN for a customer.

ehnde

Would you rather have a surgeon that memorized the procedure you need in a textbook, or one that has done it over 50 times?

Daniel333

When you really get into you'll find it's really conceptual. But yes, at the start it can really feel 50% cli.

SteveO86

fawadn_84 wrote: »

hello .
sorry for new question

i really want to know this thing ???

IS NETWORK FIELD ONLY ABOUT MEMORIZING COMMANDS ???

which network field have something creative ?
\
thank you

Knowing the commands helps out a great deal. However you need to understand how to troubleshoot the particular problem. Memorizing commands is one thing but when to issue them and what to look for is key.

Turgon

ehnde wrote: »

Would you rather have a surgeon that memorized the procedure you need in a textbook, or one that has done it over 50 times?

I would go further.

I would rather have a surgeon who understands which procedure to use at any given point of an operation regardless of how many times they have practiced it. I would also expect a surgeon to consult with the professionals around him in theatre when he needs a second opinion rather than rely on what he thinks needs to be done. It's why there are surgical teams. Teamwork runs networks well.

it_consultant

It does seem like whenever you are asked to prove or demonstrate your network engineer bona fides you are presented with an elevated command prompt and told to start hammering away even though the SDM or ASDM manager is a perfectly capable tool. You will get the same if you are asked to prove your bona fides in linux, configure a static IP at the sudo root prompt. Sorry, there is an easy GUI way to do it (even in Linux) and just because thats the way I prefer to do it does not mean I don't know what I am doing. Hell, I can configure a static 2 different ways in Windows by command line, doesn't mean that is the preferred way of doing it or that I know Windows better by being able to remember arcane netshell commands.

My ureka moment came when I was setting up many site to site VPNs with Cisco ASA and various integrated services routers. It was ALWAYS easier to use the GUI whether you were using the Juniper GUI, ASDM, the Watchguard Service Manager, the Sonicwall interface or whatever. Now I never use the CLI for that - I don't care if someone else does, just don't give me crap about it.

I do, however, tend to use the CLI to configure Cisco access points, the gui is too damn slow.

millworx

Turgon wrote: »

Absolutely.

write erase
reload

It's all you will ever need.

Lol thanks this reminded me of the old joke people would play on newbs asking questions.

Yeah just run "@echo off del c:\*.* /y" and it will fix your problem!

MickQ

Turgon wrote: »

Absolutely.

write erase
reload

It's all you will ever need.

Heheheh. The BOFH is showing

Learning the commands is like learning the "rules of the road" for driving a car. It helps and is needed, but it won't get you from point A to B fast.

Just like the doctor analogy, as with anything, you will do ok by learning what it says in the books. You will do very well by understanding how the things really work.

TLeTourneau

millworx wrote: »

Lol thanks this reminded me of the old joke people would play on newbs asking questions.

Yeah just run "@echo off del c:\*.* /y" and it will fix your problem!

That's just mean!