Update (January 2015):
Well, it has been just over three years since my original “About Me” post and quite a lot has changed. To begin with, I’m no longer 27 and no longer working for the same company I was at the time of writing the original post. I’m now 30 and have been working as a Consultant for the past few years. My current gig has me working in a FlexPod (UCS, NetApp and VMware) environment for a Cloud Services provider.
I completed the CCNP and did start studying for the CCIE R&S certification, but recently decided to put it on the back burner and began working on other areas. These areas include Netapp, Cisco UCS (to be covered in future blog posts), AWS (also to be covered in future posts) as well as various other bits and pieces.
While on the topic of certifications, I have recently passed the DCICN (one of two exams required to become a CCNA DC) as well as the DCUCD (one of four exams required to become a CCNP DC). Other exams/certifications which I hope to be sitting in the near future include:
- The remaining CCNA Data Center exam Done! I am now a CCNA DC.
- The remaining CCNP Data Center exams (DCUCD exam is done)
- Cisco Certified Design Associate (CCDA)
- Cisco Certified Design Professional (CCDP)
- NetApp Certified Storage Associate (NCSA)
- NetApp Certified Data Management Administrator (NCDA)
- AWS Certified Solutions Architect – Associate
- AWS Certified SysOps Administrator – Associate
Palo Alto Accredited Configuration Engineer (ACE) Done!
- Palo Alto Certified Network Security Engineer (CNSE)
I have been very lucky in my career to date. Over the years I have been given the privilege of working in some great roles and executive jobs which I have thoroughly enjoyed. But perhaps it’s not luck which has helped me get these roles? In this blog post I’ll explain my attitudes towards work in the hope that it helps you land your dream job too.
While the traits below may seem unrelated at first they’re actually very tightly related as you will see by the end of this post.
As the saying goes, “Honesty is the best policy”. Whether you’re in a job interview, talking to peers, chatting to your boss, always be honest. As another saying goes, “Trust takes years to build and seconds to break”. If you get caught lying in a job interview you can pretty much guarantee that you won’t be getting an offer. It’s just like when employees ask candidates to do a pre-employment assessment, you shouldn’t lie on that either. Test like these are used to gather more information from an individual, before a decision is made. Knowing this will benefit you in the search of finding your dream job. If you want to learn more, be sure to do your research before any interview you accept. If you get caught lying to peers or superiors, your credibility will take a hit which you may never recover from.
Everyone respects honesty. It shows integrity and proves your trustworthiness.
Be passionate about what you do. You spend most of your life at work so make sure you’re doing something you enjoy. After all, to use another saying, “If you do what you love, you’ll never work a day in your life”.
Original (November 2011):
2015 Update: See this page to find out what I’ve been up to over the years since this entry was originally posted.
I have received a few e-mails from readers asking me questions about myself and what I do, so I thought I’d write a blog entry about it.
I’m a 27 year old Cisco network engineer living in Australia. I work for a large, multinational company, and have been with them for about seven months now and am thoroughly enjoying myself.
I’m currently studying for the CCNP certification, and once completed, I plan to start studying for the CCIE R&S certification.
In my spare time, when I’m not studying or blogging on here, you can usually find me helping out on internet forums. The one I most frequently visit would be the Whirlpool forums where I post under the name OzNetNerd.
Hello and welcome to my blog.
I know what you are thinking, “not another Cisco Blog!”, but this one will be different, I promise :)
The point of this blog is to patch up the holes that other blogs/websites leave in the information that they provide. While researching topics in the past, I have found on more than a few occasions that some sites fail to fully explain what it is they are talking about (whether it be a protocol, QoS, troubleshooting, etc) and by the end of it I am left scratching my head and feeling like I know less than I did before I found the site.
So with this in mind I am going to explain each topic I discuss in great detail to ensure that this sort of thing does not happen to my readers. Having said that though, I do not plan to re-invent the wheel. If there is a great resource out there that will assist me in explaining a topic, I will gladly link to it and perhaps expand on it if need be.