Skip to main content

Say Yes!

I was talking to a good friend of mine and she was discussing how she's started the year and a new year resolution was for her to not say "No" to things, much like the "Yes Man" movie, unless she physically can't do something, she is trying to say "Yes" to everything that is asked of her.

Whilst this may lead to a busy and stressful time, I also think it's a very positive and good outlook to take. I have to steal a line from one of my favourite movies, Empire Records, being this:


For those that haven't seen it  I can strongly recommend watching it, it's an easy to watch film and has an amazing soundtrack!

However, I digress, there are always a million reasons not to do something, so it's very easy to say "No" to something. Yet, if we all take a "Yes" attitude, so much more would be done.

Where is this leading?

Well I had a "Yes" moment a few months ago, when I volunteered to speak in front of 250+ people (which coincidentally is where I am heading now) about a topic of my choice (technology related). Public speaking is always something that I have wanted to conquer and get even master, so I said "Yes". I'm not going to lie, there have been moments where I have thought...



But having said that, I'm genuinely looking forward to conquering this mini fear and then moving onto other things.

A key factor of the past few months has been deciding on the content for the presentation, and with the audience being a mix of techies and non techies (all University Students as well) it was important that I didn't alienate either. With this in mind I plan on talking about all the people involved in coming up with an idea and going through the development lifecycle and how it ends up on a website.

I will definitely write something about how it went over the next few days, and if it goes well (which I'm sure it will) then I plan on speaking (or at least submitting ideas to speak) at a number of events coming up, so hopefully you'll see and hear much more of me!

Comments

  1. Anonymous13 November 2017 at 06:19

    you will collect your newly-baked scholastic cardstock during the twinkling associated with an vision!
    https://eliteessaywriters.com/

    ReplyDelete

Post a Comment

Popular posts from this blog

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...
15 comments
Read more

How to manage resources within new teams?

Working where I work we are constantly spinning up new teams to take on new workloads as business come up with new demands and new features they want developed and tested. The problem with this is how do we ensure the work of the newly spun up team is of sufficient quality. One method is by taking people from other established teams and placing them on the new team. This works great for the new team, but unfortunately it will oftenl eave the established team lacking in a resource whilst they try and fill the gap left by the person who has left. We are seeing this often with our offshore teams, it can be damaging to the team structure and the teams velocity, but try as I might, I can't think of another way around it. It's far easier to take 1 person from a team that is established than it is to build a whole new team from scratch. At least by leaving the core of a team in place, you should be guaranteeing that the new team are aware of any coding standards or any QA standard...
Post a Comment
Read more

Considerations when creating automated tests

We recently released to a number of teams our automated regression pack that has been worked on over the past few months. This regression pack tests legacy code, but contains a large number of tests.  As a bit of background, a number of teams are working on new solutions whilst some are still working on legacy code. With this in mind we constructed an email with a list of guidelines when creating new tests that need to be added to this regression pack.  I figured that these can be quite broad so should apply for any organisation, so thought it would make an interesting blog post...  So here goes,  when creating automated tests, it's important to consider and adhere to the following: - Think about data . The tests need to retrieve or set the data they need without any manual intervention - This should help them be more robust and easier to run without manual intervention. - The tests need to be idempotent - By making it so that each test is standalone and does...
Post a Comment
Read more