That early experience changed how I approached learning when I eventually moved into IT. I quickly realized that the same principle applied: you don’t truly understand something until you’ve worked with it yourself. Concepts like networking, systems administration, or cloud infrastructure can seem clear in theory, but they only start to make sense when you configure them, break them, and troubleshoot them in a real environment.

Because of that, I stopped relying only on coursework and started building my own hands-on experience. I set up a home lab using multiple machines and virtual environments where I could install Windows Server, configure Active Directory, and work with DNS and DHCP. More importantly, I used that environment to test things, make mistakes, and figure out how to fix them. That process taught me far more than just following instructions in a lab manual.

Another thing I have learnt after college is that troubleshooting is the most important skill in IT. In real-world scenarios, things rarely work perfectly the first time. Whether it’s a network issue, a configuration error, or a system failure, the ability to stay patient, investigate the problem, and work toward a solution is what really matters. Learning how to think through problems is just as important as knowing the tools.

I also came to appreciate how everything in IT connects. My background in web development helped me understand how applications interact with servers, domains, and hosting environments. That made it easier to grasp bigger concepts in infrastructure and systems. Instead of seeing each topic as separate, I began to see IT as one connected ecosystem.

Looking back, I would have focused less on trying to “complete courses” and more on consistently building and experimenting. Real skill comes from repetition, curiosity, and hands-on practice. Once I made that shift, everything started to click, and my confidence grew much faster.