The second week of the QA program has seen a move away from technical subjects into the weird and wonderful world of Enterprise Architecture. Normally the academy runs this course first to give context to the more technical aspects. However, due to us being moved down to the local art gallery due to overcrowding at QA, we only began EA in our third week having been thrown in at the technical deep end of Java. It turns out this is because the Hexagon room at the Lowry where we were working does not have any computers unlike the work rooms at QA. This meant that for each group of 8 people we were given a single laptop to do the project, which would have made doing the java course somewhat impractical.
The highlight of the EA course has to be the interview stage where we had to plan and perform interviews with a variety of colourful characters played by the academy training staff. From the easily intimidated Ben Back to the rather clueless Kitty Food the characters were designed to teach us to deal with extreme characters in an interview scenario and left many memorable impressions on our team. Notably due to staff holidays we had to perform these interviews a day later in the process than normal leaving us in a situation where Thursday of the first week was a little on the unproductive side to say the least, whilst Friday was incredibly hectic in preparation for the mid-project report as the interviews contained all the information required to move forward with the project.
Apart from the project itself which is where most of the time is spent during EA, there is also a lot of theory presented in interview form. This course contains far more acronyms than I have ever had to learn before. With some of them even containing acronyms within acronyms. Needless to say I expect the exam to be 90% regurgitation of lecture material that would normally be memorized the night before. Unfortunately from that perspective, Thursday night (which is tonight as I write this post) is the welcome drinks event. This is a regular event held every 6 weeks to welcome people to the academy with free drinks down at the Dockyard. I do not expect to get much revision done.
Next week we have been told is the start of the actual QA program. After this week we are no longer allowed to drop out (and they are also not able to just get rid of us), things are expected to ramp up in intensity. This is part of our specialization into one of the high paced technologies offered by QA. Currently this is Cloud, Pega, DevOPS and MuleSoft. we were each told to select our preference for one of these techs (those of us who havn't already been plucked form the group and assigned to other specializations), as every one shuffled about into groups to decide, not a single person went to MuleSoft, seemingly because no one actually knew what it was. We are eagerly awaiting the announcement about who gets assigned to their preference and who is pushed into the dark and mysterious world of MuleSoft. Personally I don't mind where I end up as I don't really know anything about any of the softwares, I chose DevOPS because I have technically done some of it earlier in the course.
Ultimately these two weeks mark the end of the beginning of the overall academy course and I am looking forward to progressing further.
Thursday, 15 September 2016
The first week of QA training has been a fun and interesting start to my first proper job. Living way out in Stretford I have had to be getting up as early as 6.45am in order to get ready and walk in to the offices. This is a significant change to the student lifestyle of barely getting up at all most days. In spite of this initial challenge the walks have proven highly productive in allowing me to get through a large back catalog of assorted podcasts. I have also found walking in to be a better way of waking up in the morning than the standard cup of coffee which more often than not leads to me crashing by about 11 so being less than optimal from a productivity perspective.
Whilst the early morning feel like a departure from student life I have found myself thinking of much of the work being more reminiscent of the past three years of my life. We started with Java rather than enterprise architecture unlike most of the trainees here, and the first week has been spent observing lectures and working through Java tasks. This has proven to be fairly easy going and actually quite enjoyable. Being someone who loves logic puzzles I felt very at home working out how to achieve various tasks through assorted programming techniques. It felt a lot like the programming lectures at university but on a much faster timeline. I feel like I learned more about Java in the first day at QA than I had in a three month long course in C++. So a week in I feel like I can program anything.
The most notable event in the week was of course the Friday evening social time. Where I expected a single beer to be handed out to each person as a fairly token gesture and for people to be heading home by about 5.30. This proved to be far from the case. Everyone who attended was really friendly and I had a great time whittling away the hours chatting to people from all the trainee groups and also the permanent academy staff. One of the most amusing things I have found about interacting with the other groups around QA is how much more experienced they seem than myself and my fellow group mates. You can always tell who has been here longer which is interesting given there is only a month between the groups and yet they feel as far ahead as third years seem to freshers in the first week at university. They are all incredibly supportive and informative as well, I look forward to continuing the incredible pace of learning that this course appears to offer throughout the coming weeks.
Week two began with a flying start when I was so enthusiastic I turned up to work an hour early, forgetting that on Mondays we start at 10 rather than 9. So after an hour spent in the local coffee shop with a few other over-enthusiastic trainees I was ready to start working on Dev-Ops and continuous integration which is more interesting than the name suggests, although that is not particularly difficult. So after a few more lectures and a lot of typing commands and then retyping them with “sudo” at the start, I continue to feel high spirited about the coming months of training.