Any career can be short and unsuccessful or long and full of achievements, everything depends on the ways of development, efforts applied and knowledge of a person. And there are some tips and shortcuts that can help to be more successful that you have ever expected.
Here you will find some useful pieces of advice how to succeed in the network engineer career from people who spent a lot of time teaching novices how to develop skills and knowledge in this area.
This article will give you two the most important things to take into consideration:
Step 1. Every action should be well-thought-out
Engineers know that there are too many devices, technologies and actions, so it is almost impossible to know everything in detail. Before you do anything on a production network, make sure that you know the answer on these questions:
- Is it necessary?
- What will it do?
- How to back it out?
The first question will stop you from rushing into action as here it is necessary to sit and think what changes this action will make.
The second one requires at least the basic knowledge of the technologies you use – you need to know how this action will work and what it will change during the work. There are no ways to skip this step as it is necessary to know the principles of work to be able to answer this and the next question:
How to back it up? Sooner or later there will be a necessity to undo the changes you have made, so you have to be ready for it. Always prepare the back-out plan that will save you time and efforts.
Step 2. Always document everything that you are doing.
This step is very important especially in the team work. Even the most talented and knowledgeable engineer should do this as afterwards it will be important to leave the way for others to follow you. It is also useful as you will not remember some ways and methods you use in a year or two, so with proper documentation you will be able to repeat it afterwards when you will need it.
In addition, it is necessary to label all physical port and gear. All installations and changes should be documented in one standard way so every member of the team should understand the notes.