Nordic Testing Days 2019

This past week I was fortunate enough to be able to not only attend, but to speak at Nordic Testing Days 2019. Nordic Testing Days is a fantastic, and highly attended, conference that takes place every year in Tallinn, Estonia. They bring together speakers, attendees, and sponsors from not only the northern EU but also from around the world to discuss and learn more about testing and tech as a whole. With a bit of background now given, let's dive into what this year was like, from my perspective!

Day 1/2 - Exploring Tallinn Heading off to Tallinn, Estonia for Nordic Testing Days (NTD from here on) was my first trip across the Atlantic. Yes, this was my first ever trip to Europe. After a nice 14 hours of travel time, I arrived in Estonia on May 28 around 1:30pm. Sadly, with the time zones and travel I was absolutely too exhausted to be exploring Tallinn that day. I spent most of that day just holed up on the hotel trying to get enough sleep at the right time to be able to properly …

So you want to speak at a conference...

Alright so, you've decided you want to try your hand at speaking at a conference. That decision alone is exhilarating... and terrifying. But where do you start? If you don't have a mentor (yet) who has some experience with conference speaking it can be really daunting to think about how to break into the conference speaking circuit, but it isn't as hard as you think (in my experience, with testing conferences)! In this blog post I'll go into details about how (and where) to get started up to the application process, I'll cover actually speaking in a follow up!

Shoutout to Shannon Draper for inspiring me to write this after a long winded conversation (in a small town in Colombia) about speaking at conferences
Disclaimer: I am not an expert, this is simply my advice based on my experiences!

So where do I start? Pick a topic!       The ideal starting place for speaking at a conference, is to have a topic in mind. It's great to want to speak at conferences but the b…

Knowing When To Let Go... And Who To Let Go Of

In my last post I talked about knowing when it was time for me to let go of my old job and old company in search of better things for myself and my career. This time I'm going to change it around a little bit, how do you know when you need to let go of someone from your team, for the good of your team? 
Recently I saw our QA team be cut in half due to layoffs. Although I wasn't directly involved with the decisions that were made at that point in time I did need to mentally come to terms with what had happened and come to terms with the fact that I played a part in a small way. 
When I started at my new company I had been told that the team had some growing to do and that there would be challenges that I would be asked to help find solutions for. Fortunately, a week before I started someone else also started, a Senior Test Strategist who is one of the most incredible testers I've ever had the pleasure of knowing. So the good news was that I wasn't going to be going into…

Career Paths and Generational Gaps

Approximately three months ago I made the decision that I wanted to change jobs. I was choosing to leave my job for a variety of reasons, that I'll get to later, but this decision revealed to me how different career paths are for those entering the full time workforce now vs the time when our parents would have. I mentioned to my mom in mid-August that I was looking for a new job. Her response to me was, "I swear you're going to be the death of me child." I had no idea what she was talking about.

Over the course of my search as I reached out in the community to find opportunities, applied to different jobs, and eventually interviewed at different companies I had conversations with my mom that lead me to one very important realization; my generation doesn't view career paths as a linear, vertical trajectory. When my mom got her first full time job, she planned to stay there for as long as possible and work her way up. That was the only way she saw it. She saw chan…

The Importance of Community

Community. It's a wonderful thing. In technical terms it generally refers to a unified group of individuals. Most often used to refer to a collection of homes in a given area it can also refer to any group that considers themselves unified by anything.

When looked at as a unified group it's pretty easy to see that your life is made up of communities. The area you live, your group of friends, your sports team, all of the fans of your favourite sports team and yourself, there are many communities you may belong to. The chances are, if you're reading the blog anyways, you're also part of the tech community. Additionally, you may also identify as part of the developer community, or the tester community, or both, or any other faction of the tech sector. The bottom line is that this is one of your communities. It wasn't until a year ago that I started to fully explore the depth that this community can have and I am now here to explain why I feel it is so important to be …

Don't Take It Personally - Round One

After a multi-month hiatus from posting I am finally back with some very exciting things to share. After my last blog post, "It's Not Personal", I had an idea. I attended my first ever conference, Targeting Quality, in September of last year (September, 2017). I LOVED it. I attended talks that taught me about new skills, new ideas, and a lot about myself. I decided I wanted to try and go to more... which is when my mentor, and great friend, told me that the best way to go to conferences was to speak at them. So, after writing my last blog post and realising how passionate I was on the topic, how much I had learned on the topic already, and how much others could likely benefit from my experiences I decided to write a proposal. This is where I remind everyone that I am by no means an expert at this. It is just something I am passionate about and have spent a great deal of time researching and working on.

Now, I won't go into all of the details of the experience of appl…

It's Not Personal

It's not personal. I'm sure everyone has heard that said to them at one time or another throughout their lives, in this post I'm going to discuss what this means to me in testing from two perspectives: not catching every bug and not making found bugs personal.

Every time that a bug is found that was introduced by something you helped to test it is hard to not blame yourself for letting it slip through. It's hard to reason with why that isn't your fault and what you could have done differently to find it. The only way to get through those situations is, you guessed it, don't take it personally! Now, don't think that I am some expert at this. In fact, I struggle with this every single day. I still have to give myself pep talks every once in a while to remind myself not to take it personally and to just keep moving forward. 
There is no way to find every bug. That just is not possible, no matter how good you are, no matter how good your team is, something will…