“A lazy systems administrator is a good systems administrator” –Anonymous
The job of a systems administrator is generally not visible to other IT services or end users. Most of the time, they look at systems administrators and wondering why they do not seem to do much. When you see a systems administrator who’s always running around in all directions, trying to extinguish the technical fire, constantly engaged with tech problems, you might think he works hard and is really his job. When you see a System Administrator (UNIX / Linux, database, network), who apparently did not seem to tread a lot in the office, always seems relaxed and did not seem to have an activity visible, you can be sure he does his job.
Here are 12 reasons why a lazy system administrator the best systems administrator:
1. Who is the leader? : They do not see quite the machine like other computer services. There is a difference between developers and system administrators. Developers think they are there to serve the machines by writing code. There is nothing wrong with this approach because the developers take great pleasure in writing code. But system administrators think everything else. They believe instead that the machines are in service. All they have to do is feed the machine, make it happy and let the machine do all the hard work while they relax and laze. The first step to becoming a lazy system administrator may request a slight change in attitude: it is to know the machine you’re the boss.
2. Write scripts for recurring tasks: Being lazy is to be smart. A smart system administrator has mastered all scripting languages (bash, awk, sed, etc..). Whenever it is required to do a task, and there is a vague possibility that it may need to work even later, he wrote a script to do the job. So when he asked later to redo the same work, he will not have to think, it will simply run the script then return lazy.
3. Save All: Being lazy means save all. A lazy systems administrator knows to give a little time in creating the backup process, and then write backup scripts for all applications and all critical systems. When something goes wrong with the saved data, disk scheduling, processing, he just needs to restore a backup to return to a peaceful position as it was before.
4. Plan a recovery: System administrators do not like having to gesticulate in all directions in an emergency. When all goes well, they take a little time to create a plan for disaster recovery. When things go wrong, they can follow certain techniques & solve it quickly to return to a normal position.
5. Configure a system high redundancy: Administrator do not like being woken up in the middle of the night because of a beast of system failure. They therefore ensure that peripherals are highly redundant. This includes both hardware and software: they have two brief configured network cards, dual power supplies, two hard drives, two of everything. Like that, if any of the equipment to fail, the system will still work and our lazy administrator can focus on repairing the faulty equipment after rising in the morning.
6. Leave room for unexpected growth: A lazy system administrator never allows the system to run at full speed. He always keeps the free space for the unexpected issues. He ensures that the system has enough CPU and disk space and RAM available. When the sales department decides to dump tons of data during the night, he did not need to think about how to handle this unexpected growth.
7. Be proactive: Being lazy does not mean that you just have to sit and twiddle your thumbs. It just means to be proactive. Therefore, they always anticipate difficulties and expansion. When they have free time available (and they have a lot), they keep a close eye on projects to manage future growth and avoid unanticipated problems befall.
8. Love the keyboard shortcuts: Lazy systems administrator knows all the shortcuts of all his favorite applications. If he spends significant time daily on an application, the first thing he does is to master the keyboard shortcuts for this application. He wants to spend as little time as possible on the application to achieve its purposes, and become lazy.
9. Skip to master the command line: This applies to Linux system administrators, administrators, database, network administrators, etc. If you see an administrator launch a GUI while the same task can be done from the command line, then you identify that he is not a lazy system administrator. There are two reasons for systems administrators lazy love command lines. One, it can do things quickly from the command line. And secondly, it gives the impression that he is the boss and not the system. When you use the command line, you have control; you know exactly what you want to do.
10. Learning from mistakes: Administrators lazy systems like never to make the same mistakes twice. They hate working on unforeseen problems, but when they appear they work to fix it as soon as possible. Think about how it’s handled and controlled immediately by applying the necessary logics so that it does not happen again. Work on the same problem twice is considered a sin for a real lazy system administrator. He likes to work on the problem once, do whatever it takes to prevent the occurrence of the same error in the future, and return quietly lounging.
11. Is continuously forming new technologies: There is nothing wrong with learning new technologies for a better job or just to maintain progress in the field. But a lazy system administrator does not learn new technologies for this reason, because he likes to keep control over the system permanently. He knows that he is the head and not the machine. Thus, when a new technology arrives, he takes the time to study it. Now it has new tools to deal with the system as it continues to laze. It’s laziness that is the main motivation for its formation.
12. Document everything: You see, the lazy system administrator hates to be disturbed while he is on the beach enjoying his vacation. So what does he do? It documents everything, so that when he is not there than others can do the job base in place of him, and things do turn undisturbed during his vacation. There is another reason why the lazy system administrator documenting all because he forgets things. As lazy, you tend to forget what you did the previous month. A lazy system administrator does not like at all think twice on the same subject, so he documents everything and when he needs to do the same thing in the future, he will return to its documentation to understand what he had done earlier.