My first day(ish) as the new guy

Originally, I was supposed to join the Communicator team today, but a cancelled day of vacation pushed my start date up to yesterday…but there was a meeting I wanted to attend on Monday, so I’ve basically been out of building 21 (EE land) and in or near my new office since Monday afternoon. So, let me tell you’ what I’ve been up to since then!

It’s been a bit of a slow start – given that I started early and the pace that the hr backend is updated, I don’t have permission to enlist in the source code yet. On top of that, I’m told it will take a week or two to get my server account moved so I can use the in-development release. I’m also still waiting on my new computer (I still have my laptop and a computer that will become my secondary machine, so I’m certainly not completely blocked).

And, despite waiting for permissions, I don’t feel blocked in my ramp up either. I have a 3-pronged approach to ramping up on a test team that is working well for me so far. First off, although I normally don’t like going to meetings, I’ve already attended half a dozen or so. Some, I’m invited to, and others I just tag along. It’s a good way to figure out what’s going on in the project, learn faces, and get a sense of the team dynamic. Secondly, I’ve spent several hours reading through bug reports. It’s great – without talking to hardly anyone, I already have a sense of the types of testing approaches used on the team, a sense of how the database fields are used and interpreted, and even some insight into individuals on the team. I’ve recommended reading bug reports as a way for testers to ramp up quickly on a team for years, and I’m delighted to see that it works. And – I’ve read team wikis, test plans, and whatever other collateral I can find in order to help round out what’s going on.

I’ve been reading so much, in fact, that by Tuesday afternoon, my eyes were aching and my vision was fuzzy. So fuzzy, in fact, that I visited the optometrist on the way home for my first ever eye exam. Shortly later, I ordered my first ever pair of eyeglasses. I’ll post photos of my new look as soon as they show up.

Today, I made sure I took a few breaks to rest my eyes – I used the time mostly to unpack a few items and tidy up a bit. My new office is now entirely unpacked except for a big box full of random cables that I’m afraid to get rid of because the moment I do, I’ll need one of them.

I think that’s about it. Oh – except that I’m giving a talk tomorrow on random career tips. I think it will be interesting, but we’ll see. Looking forward to sharing them here at a future date…or perhaps over live meeting??? 🙂

Similar Posts

  • A call to action: let’s fix the Wikipedia page on software testing

    Today, I had a few minutes, and wanted to try, yet again, to make some positive change to the article on software testing on wikipedia I failed. It’s a mess, and I don’t know where to start. It’s too long. It’s unorganized. Many / most of the citations are a decade or more old. Some…

  • Australia 2013-2014

    No testing related content in this post – just a quick trip report of our family vacation to Australia that I can point people to as necessary. Sydney (part 1) After a long flight, we landed in Sydney, where we immediately set out to explore a bit (I’ve found that walking in the sun is…

  • Five for Friday – June 11, 2021

    It’s a sort-of-sunny day in the Pacific northwest, and I have the day off from work (which probably means I’m cleaning the garage today. Here are some links to ponder from my recent browser history. Camille Fournier posted a wonderful (and incomplete) list of skills senior engineers need, beyond coding Lisi Hocke wrote a wonderful…

  • Fuel for work

    Due to some unforeseen issues, my experiments in remote work are continuing. These days, the situation is a bit different though – I’m working in the same time zone,and I’m showing my face at work one to two days a week. Of course, my observations and musings about working remotely continue. The days that I’ve…

  • Status and Progress

    Status meetings are boring. More importantly, status meetings are unneeded. Meetings are for discussion, and updates on status rarely require that (until, of course, they do). Nothing – nothing is more painful than sitting through a meeting where people go around the table and say, “Today, I’m doing X”.  Hopefully nothing alarming so far. A lot of teams…

  • Tester DNA

    In HWTSAM, we (Ken, actually) talked a bit about tester DNA – that bit of mental goo that makes some people better (or at least more prone to being) testers. As I’ve been talking to (potential) testers lately, I’ve had a chance to dwell on this a bit more. What is it that makes a…

2 Comments

  1. I’ve been reading through bug reports for my new job as well. I’ve found that it can make for very interesting reading, especially if the bug tracker allows for users to vote on an issue. Shows a product’s pain points pretty quickly.

    Can’t wait to see the new look 😉

  2. “because the moment I do, I’ll need one of them” –> completely agree on that aspect.

    absolutely agree about going over the bug reports – especially when lack of proper documentation, going over the latest set of test cases and bug reports ; at the same time playing with the product gives tremendous information about the product itself – and to an extent – tells/reveals (1) product quality (2) test case and defect reporting quality (3) standards and processes team follow or followed at the time of product dev/execution cycle.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.