Skip to main content

Career influences

This isn't necessary a QA centric post, but I felt that it's something that has affected me and I feel like I should say.

We all have career influences in life, people who we meet throughout our career who have a profound affect on the actual career path that we take. 

I am soon going to say goodbye (in that she left the company) to one of these people, she was someone who would always push me to do my best, and is partly the reason why you are reading this blog. She pushed me to get into blogging (along with others, and you can read her blog here), but she's had a major impact on my career and as such my family.

She's someone who really pushed upper management to recognise my talents, and helped them come up with a 6 month career development plan that I hope will get me to where I want to be. I owe her so much gratitude, and I don't think she realises just how much everything she has done for me actually means. (And to think she's not even a tester!) 

I will miss her an awful lot, and my company will miss her too, but there comes a time in everyones life when they have to move on. Hopefully our paths will cross again!

I hope one day I can have a similar effect on some people, but right now I'm eternally grateful for all that she has done for me, and I am sure that we will remain friends.

There have been other people who have had major influences on my career another person was someone who I met at a Hedge Fund, when I hadn't been in testing for long, but he made me realise that I could do so much with my skills, and made me realise that I am better than a lot of other testers out there. He made me believe in myself, and helped me on a personal level too with regards to buying my first house.

Let's not forget, another major influence and someone who will always be a major influence, my wife (I'd have got told off otherwise!)! Who has given me great support and given me the drive to be the best I can on a personal and professional level to provide for my family.

So, who's been your major influence on your career so far (like me it doesn't have to be a QA professional)? How do you think you've influenced peoples career for the better?

Comments

  1. Thanks for sharing wonderful post..It reminded my first company and my team including my managers and VP - They gave me the support to grew up in my professional and personal career.

    ReplyDelete
    Replies
    1. No problem, hopefully you will find more career influences as your career grows in QA. :)

      Delete
  2. Gareth, you are very lucky to have someone like that. Yes, I have my wife and parents to support me in my personal life but none in professional life yet. I am very jealous about this, but I guess it mostly got to do with hard work.

    All the best for your future!

    ReplyDelete
  3. We need more such articles that we can read with such enthusiasm.
    resumeyard.com

    ReplyDelete

Post a Comment

Popular posts from this blog

What is a PBI?

After my last post, I had the question of what is a PBI... so I thought i'd write a short blog post about what they are and why they are used. A PBI is an acronym for Product Backlog Item. It is a description of a piece of work that your SCRUM team will develop and deliver. When you have a list of Product Backlog Items, you then refer to that collective list as a Product Backlog. The product backlog is often prioritised and yourteam will work through each PBI, and release on a regular schedule... I am however going deep into the world of Agile development, which isn't entirely what this post is about, so I will stop myself now. A Product Backlog Item is made up of the following: Title - This is often a one liner that gives the team an idea of what the PBI is about, although it can just be an ID for the item and the team work off of that. Description - Breaks down the PBI in a bit more detail, and can be written in any style, however I prefer it to be written as follow...

Coding something simple.... or not! Taking a screenshot on error using Selenium WebDriver

I recently wrote a little function that takes a screenshot at the end of a test if it has errored. What sounded very simple at the start turned out to be quite a bit of work, and quite a few lines of code to handle certain scenarios! It's now over 50 lines of code! I'll start with what I had at the beginning, this was to simply take a screenshot in the working directory, we are using SpecFlow and Selenium to run the tests, so we are going to check if the ScenarioContext.Current.TestError isn't null, if it is, then using Selenium, take a screenshot (note the below code is a simplified version of what I had at the beginning). [AfterScenario]         public static void TakeScreenShotOnError()         {             if (ScenarioContext.Current.TestError == null) return;             var screenshotDriver = Driver as ITakesScreenshot;             if (screenshotD...

The Stickman Tester... The full version complete with deleted "scenes"!

As some of you may have seen, a little while ago I performed a 99 second talk on the Stickman Tester for the Ministry of Testing. Owing to the fact that it had to be 99 seconds, this unfortunately meant that a verse was left out in order to keep it within the time frame! It's only now that I have found the time to put the deleted verse/scene back in, and re-record it and upload it! (It's now a 120 second talk!) It talks about a testers journey in an Agile team, about how not everybody has it as good as others, and basically talks about not giving up, keep searching, or trying to change your role to make it what you want it to be. Anyway, here it is, in all it's glory. Hope you enjoy it!