Christmas 2013

Merry Christmas to all of my family, friends, readers, and subscribers reading this. I hope everyone has the chance to spend time with the people who are dear to them. I know this year that’s the only gift I was looking forward to, the little bit of time I could get with my friends who normally have a traditional family Christmas.

This Christmas Eve was a busy one. It’s funny how the holidays become much more complex as you get older and all the relationships between your friends and family get more complex. We end up realizing how precious the time we spend with our friends and family is as well as who holds you in the same priority. As someone who didn’t grow up with money, I was actually able to afford giving gifts this year to a lot of people who I would not be able to afford giving gifts to in the past. I’m very grateful for the ability to do that. During the holidays we should remember that no matter where we are in life, we’re somewhere safe and warm for the holidays.

Once again, merry Christmas to everyone. Stay safe as you celebrate. Thanks for reading!


9 Weeks

So this week was crunch time for my first project. I can proudly say that I passed my acceptance testing and all that is left is installation. After a stressful beginning to the week, my project smoothly passed acceptance testing without any major issues. What have I learned from my first project?

First and foremost, I have to thank all the other people who helped me along the way when I didn’t know about a certain functionality or aspect of the system. My peers were very willing to help and if it wasn’t for this then I’d be lost due to the lack of documentation we have on our systems. With all the components involved that come together to form a system, the amount of information that would be encapsulated in documentation would’ve taken too much time to read through just to get to what I needed to know. As for their help on the online system we use to open issues, update work items, and process project stages, their help was invaluable there as well. I’ve come to realize online systems for paperwork are ridiculous and quite frankly more time consuming than just filling out a normal form.

Secondly, at the end of the day, all the matters is results. I’ve come to realize that listening to my project manager rushing my schedule is pointless because in the end my project was successful. My project manager’s distractions and pressure resulted in my mistakes as well as the delays that came along with those mistakes. If I was left to my self to test everything rather than being pushed to move my project to the next stages, then I would’ve been able to catch most of the non critical issues that will need to be addressed in the future. My SQA and my manager both emphasized to me that in the end, all the customer, management, and the company cares about is the successful delivery of the product through any means possible. So from now on, even if my testing method seems slow, I know that I’m covering all the bases necessary such that I deliver a quality product to my client and our end users.

Finally, at the end of the day, as the focal of the project, I have final say over what I want to do over my project because I’m the one that knows the ins and outs of my project. Not my client, not my project manager, and not my coworkers. At most, the people mentioned above have a general idea about what my project is capable of, but I am the focal, therefore I am the “expert” regarding my project. This means that when I report, I need to be more confident in my answers and the way I vocalize my answers. From here on out, I have a pretty good idea of what to expect, what mistakes are commonly made, and what resources I have around me to help solve/troubleshoot issues that I encounter.


Thanks for reading! Feel free to comment.