Hey there! I've been reflecting on my 8-year journey through the tech landscape, moving between different companies and collecting programming languages along the way. It's been quite the experience! 👀 Starting Out: Villa College Days At Villa College, I started as an IT Officer handling everything from printer troubles to network issues. What most people don't know is that working at an educational institution had its own unique challenges. The doctors (faculty) there had particularly high expectations - make one mistake during a class presentation or while fixing equipment, and you might get scolded right in front of students. Nothing builds character quite like troubleshooting a projector while a professor gives you the death stare! During this time, I was also building a Movie Renting Software for my diploma project using Visual Basic. The interface wasn't winning any design awards, but I was pretty proud when I got that payment system working without crashing e...
When people ask me about transitioning from IT hardware to software development, they often wonder if these are completely different domains. But here's an interesting perspective: my hardware background has become an unexpected advantage in my software development career. The Universal Challenge of Troubleshooting One striking parallel between hardware and software worlds is what I call the "why is it (not) working?" phenomenon. Every IT professional knows those days - you're staring at a piece of equipment or code that's either working mysteriously or failing inexplicably. Early in my career, I assumed these moments were just symptoms of my limited knowledge. However, I've come to realize something profound: even after years of experience and continuous learning, these puzzling moments remain a regular part of the job. The Evolution of Hardware-Software Relationship Interestingly, since moving into software development, I've noticed my hands-on interacti...