Hi guys, sorry I haven’t been blogging in a long time. The holidays + work turned out to be a lot more than I could handle in terms of time and energy. So happy new year/happy lunar new year to those of my followers who read this. I hope everyone has a good year in the year of the horse. I’m excited about this year because I’m a horse and I always look forward to my years.
4 months… it’s really been 4 months since I’ve started my full-time job in my test engineer role. It feels like time’s just flashed right by, but I guess this reflects how busy I am at work these days. Looking back, these 4 months have taught me a lot of lessons. Lessons about the internal strife that is part of working at a big company, tips and tricks that go with the job, and how I view my role within my group.
To start off, I guess I’ll address the internal strife I mentioned above. Working at a big company has its perks. The reputation of the company makes your resume a lot more credible, you yourself make it even more credible when you can actually communicate your role, contributions, and skills acquired in your time at a big company. Your role however in a big company can be quite small/focused. In a sense I’m lucky enough to be in a position where my job can be as big or as small as I want it to be. I’ve come to realize I’ve exposed myself to a lot more responsibility compared to some of my coworkers who have the same role. I’m not saying that I do more than others, but I definitely put myself out there so that my managers and peers know that I’m always willing to learn and learn to do things correctly. The flip side to this ability to become involved in different aspects of work is that there seems to be a lot of confusion when it comes down to who should be doing what. There are definitely situations in meetings where some of the developers, managers, and test engineers have a hard time deciding who should be doing what. This confusion results in a very bad rap when the customer is unhappy with an issue and the fingers are being pointed. In general, working at a big company always comes with its pros and cons.
Skills, tips, and tricks. While I was in college, the projects and tasks I was exposed to generally revolved around the use of one or two skills alone or combined. I’ve come to realize at work that this isn’t the case. Our products combine so many programming languages, levels, and skills that if I hadn’t learned a variety of these languages, I would have a hard time doing my job. If you’re still in college and you’re studying programming, make sure you know SQL, linux/unix, C/Java,and some sort of mark up language. My personal adventures in android/HTML turned out to be very helpful in the workplace when dealing with GUIs and parsing data. Ultimately the potpourri that our software is made from is much more complex than I can contemplate.
As for my role in my team, I’m still NG2, aka new guy 2. There’s a lot that I don’t know or haven’t even been exposed to yet. I have this saying among my coworkers about how I’ve only faced 2 out of 7 dungeon bosses. By that, I mean I’ve only met and survived encounters with two of our customer representatives. As for my experience so far, I know that to a certain degree they depend on me for a facet of our products’ functionality. This also gives me a sense of security when it comes to knowing that I’m being of use. But this sense of security isn’t enough because what I know is only 15% of what our products are capable of. Like I said above, given the opportunities, I’m trying to involve myself in as many opportunities to learn as possible.
With that being said, I still can’t believe it’s been 4 months. I’m hoping that time doesn’t fly by too quickly. At the same time, I’d love for my current project to reach a conclusion so I can put my vacation days to use. Thanks for reading guys. Hopefully I can find time to blog more consistently.