Hey guys,
I recently started a new IT job which is vastly different from my previous roles. Before, I mainly did phone tech support and enjoyed being buried with work.
This job is in house IT support, and there is a lot of downtime. I am on probation so I constantly feel the need to stay busy or at least appear busy. My fallback plan is to leverage my technical writing skills to create documentation.
I started by documentating our common practices which I would eventually compile into a policies and procedures manual. I thought it would be good to have every single IT routine down on paper. Next, I had the idea to create database documentation. We run queries and create reports on this massive database, and we only have this wall chart as a reference guide.
Today, I had the idea of creating a disaster recovery plan. Let's document out every step that should take place in the event of a data loss or worst case scenario event. Does this sound like a good idea, or just a luxury?
While these self made projects could keep me busy for several months, I'm worried about rushing through them because when it is all done, what do I have left to fall back on? My only thought is to spend the down time studying for a SQL certification. Would that be kosher?
Anyone else been in a similiar situation? What did you do to fill the void?
I recently started a new IT job which is vastly different from my previous roles. Before, I mainly did phone tech support and enjoyed being buried with work.
This job is in house IT support, and there is a lot of downtime. I am on probation so I constantly feel the need to stay busy or at least appear busy. My fallback plan is to leverage my technical writing skills to create documentation.
I started by documentating our common practices which I would eventually compile into a policies and procedures manual. I thought it would be good to have every single IT routine down on paper. Next, I had the idea to create database documentation. We run queries and create reports on this massive database, and we only have this wall chart as a reference guide.
Today, I had the idea of creating a disaster recovery plan. Let's document out every step that should take place in the event of a data loss or worst case scenario event. Does this sound like a good idea, or just a luxury?
While these self made projects could keep me busy for several months, I'm worried about rushing through them because when it is all done, what do I have left to fall back on? My only thought is to spend the down time studying for a SQL certification. Would that be kosher?
Anyone else been in a similiar situation? What did you do to fill the void?