2019 is here and 15 days have already passed, just 23 fortnights to end the year 🙂 Anyway 2018 had been a great year for me with regards to the IT centric learning. I’ve been through job redundancy, a Great holiday in India and Parenting at it’s best. Fun times!!!
I gave an attempt to complete CWNA on 2nd November but failed to do so. May be it was a hasty decision to complete it before going on holiday but lesson learnt. Will give it a try soon in next month or so.
I managed to nail CCDA keeping my Cisco certifications alive. That’s one good thing.
In 2018, I also managed to learn RF basics with regards to Wireless Technologies. Strengthening my skills around wireless site surveys and they way radios work.
I will aim at writing better blog posts. 2019 will be even more better in terms of learning. Learning about different aspects of technologies that bind together.
Change control is an important part of ITIL and any organized form of business. It is the source and essence of the day to day tasks and it encompasses the same logging that used to be done in early days which is now a days replaced by online/computer format change control. Change control also gives a scope to peer review and avoid is a mishap by casting multiple opinion on the upcoming change.
Not logging a change or documenting can prove too costly most of the times. In some cases logging the change alone can save you from lot of questions in case it does work out the way it is planned. After the change is being approved and the outcome is not good or as planned this might work in your favor as the person approving it is somehow responsible for its failure. Having said that it also depends that the change is done as per the documentation and rollback procedures are followed.
What are your thoughts on this?