Being a system administrator is a really hard job. If one of us has been dealing with server installations and management, he knows very well that being a system administrator is not just as easy as setting up and maintaining a server as it sounds. To be a successful system administrator, it is necessary to know how the code works and how to intervene in whatever is broken.
If you work as a system administrator, we have compiled 18 golden rules that we assume you have already learned the easy or the hard way by now. By checking our list, you can get an idea of system administrators and non-festive working conditions for homes. If you are a newly employed system administrator, you can take the necessary courses in advance.
1) Avoid Making Changes That You Cannot Undo
Be sure to back up your files before working at regulatory times. Do not try to rely on your memory in this matter, a small change you forget can cause big problems. Do not try to apply your changes to your original system without trying them on a test system. It may sound challenging, but try to avoid irreversible mistakes.
2) Do Not Make Changes Before The Holidays
Do not make changes before a few days when you will not be around or work. Make sure there is a period of time to observe the changes you have made.
3) Try to Find the Root of the Problem
When there is a problem you encounter, try to dig into the deepest of the problem, avoid superficial solutions. When you run into problems, follow the "5 Reasons" rule. Try to assess the root of the problem so that you can find at least 5 problems for yourself. “The server is not working properly, why? Because the memory is insufficient, why? Because some operations run wrong, why? " Create at least 5 problem chains with questions such as.
4) Check Again Your Crisis Plan
Decide beforehand what to do in a crisis. If you don't review your plan, it will probably be like this, you won't know what to do or you won't be sure of what you are doing. Let's say you urgently need to transfer a database to another server unit. Do you know the steps you need to take? Are you aware of the estimated processing time? Do you believe you can handle the migration? Do you have the data to check whether the transaction was successful?
5) Don't Trust Codes You Have Not Completely Tried
Do not rely on untested code in every sense. Always test your code from different angles, think differently. Know that people different from you may think differently and find vulnerabilities in your code that you did not anticipate.
6) Keep Your Codes In Order
Keeping your code organized will always save you time and reduce your risk of making mistakes. Save the codes you use often as function files and name them meaningfully. Thus, both your speed will increase and it will be easier for you to control. You can read the Clean Code Suggestions article we wrote earlier on this subject.
7) Add Comments to Your Codes
Add comment lines as you write your code. The codes you write may mean something to you, but others may not be able to understand your code. Also, just because you understand the codes you are working on does not mean that you can understand it after a while. One of the main elements of keeping your code organized is adding comments.
8) Learn From Your Mistakes
Remember that you may experience job blindness. Don't be pessimistic about it when you make simple mistakes. You may have mistyped a simple code, forgot to reset your passwords. Just be aware that these errors are normal and try not to repeat them.
9) Don't Miss Paranoia
Don't be afraid to be paranoid when writing your code. Always think about the shortcomings of your code, be skeptical about who can and how. Get stuck with the details, think for others and try to see your code from the outside.
10) Anticipate Errors
As you write your code, you cannot expect all errors to be visible. Or some errors may not just appear while you are writing code, they may take time. In this case, try to consider and evaluate the errors that may arise. In short, do not expect everything from the state.
11) Spend Time For Security
Never underestimate your security-related work and do not try to be easy about it. Be aware of who you store their data. Be prepared for situations that require a security alarm.
12) Review Error Feedback Frequently
Frequently review your error feedback and log files, try to solve your problems by writing your own codes, do not avoid details. This way, you can avoid big mistakes without getting worse.
13) Get a Backup of Every File
Make sure you have a backup of the server you are using. Consider the customers whose data you are storing and how it will make data loss a problem. Always have a backup plan.
14) Time is Money Anyway
You remind yourself that other people's time is as precious as your own. Know that your customers who are looking for help do not share the same perspectives with you, that it is possible that they have not been able to understand the solutions you will find, and try to intervene as quickly as you can.
15) Update Your Customers Like Your Codes
Do not forget to inform your customers about the solution of their problems and the solution process. Provide detailed explanations to your users for the updates and changes you have made.
16) Be Flexible
You may not be happy with the attitude of the people or customers you work with, but a system administrator should not be inaccessible and should be able to solve everyone's problem. Consider stretching your boundaries and changing your paths.
17) Improve Your Abilities
Always follow the trends and the most popular methods. Change and improve your abilities. Always try to move forward. Falling back is another name for losing.
18) Balance Your Work and Private Life
Even if you are very committed to your job, always keep your work and private life in balance. Don't get caught up in your business and turn into ambitious, asocial people. Know that your profession does not define you, and that you can do other things besides your job.
I hope my article has been useful for you. If you like my article, do not forget to like and comment.
Felicitaciones me gustó mucho tu artículo! !