I started my journey as a Technician working with computer hardware, while studying at TUT, did a few odd jobs to make ends meet, most of that was near and around PCs or fixing PCs or assembling PCs or any odd job really. When I went for my CCNA it was basically me trying to differentiate myself in the market place with a new skill, it got to the point where I realized that there are so many different vendor-specific certs you will need quite a few to become relevant in the networking profession. So I decided to return to school after I’d saved up some cash. I ended up being a Lab Assistant towards the end of my studies. [Lab Maintenance & Ensuring the lab is ready for classes, setting up hardware & such]. I also had work off-campus from time to time. School fees became a primary expense. After graduating I started my professional career as a Software Developer, which came as a surprise since in my professorial qualifications I am a Software Engineer not Software Developer but I still got into it. Soon IT became not only a hobby but also a sport. Nowadays I try to apply my mind to solving problems as opposed to fixing software issues. The aim is to cater to the client by understanding a customers’ needs and delivering as close to their requisite as possible without over-complicating the proposed solution. Sometimes the problem isn’t as it was laid out. Sometimes trying too quickly to fix something can lead to even greater problems. To inspect the source and understand the customers need in detail I find leads to the most generous feedback and resolution practices. I try to not look at the ticket and just resolve it, getting a gist of the issue from only one perspective is the beginning of completing a resolution cycle.