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

Treating Test Code as Production Code

It's important when writing automated tests to remember that the code you write should be up to production standards, meaning any conventions that you have in place should be adhered to and that it should follow good design patterns. Too many people often say why does it have to be as good as production code, it's "Only" a test, so long as it passes then that's fine... To answer this we need to look at why we want our tests to be written in such a structured and efficient manner: - Maintainability - by making the test code structured and efficient, it becomes far easier to maintain and in doing so changes in the future can happen quickly as the test isn't linked to anything that it shouldn't be and it's easy to understand for a new set of eyes. - Durability - Again by making the tests structured they should be resistant to changes, if you change a variable name for instance then it shouldn't effect the unit test unless it absolutely has to....
1 comment
Read more

Testers: Be more like a Super-Villain!

Who doesn't love a Super Hero? Talk to my son, and he'll tell you how much he loves them, talk to many adults and they'll say the same! Deep down, we all love to be the Super Hero, we all want to save the day! However, I want to talk about the flip side of Super Heroes, the Super Villains... I often play Imaginext with my son, and I (unfortunately?) am nearly always the Super Villain! Be it Lex Luthor, Joker, Two Face, Mr Freeze or The Riddler! These are all great characters and great Super Villains, but why would I want to write about Super Villains? A while ago where I worked, we had a few Super Heroes, people who would be able to come in and "fix" things that had broken and help deliver projects on time. We then shifted, we decided to do away with the Super Hero culture and try and prevent from being in that position in the first place, whilst we didn't go as far as wanting to hire Super Villains, it's definitely a story that has stuck with me and t...
2 comments
Read more

Using BDD and gherkinising your Acceptance Tests

In my post Testing of Automated tests , I mention about a BDD framework which involves using BDD to drive your acceptance tests. BDD stands for Behaviour Driven Development.  One effective method of writing BDD tests are by using a format known as Gherkin language. These consist of Given, When, Thens. The main advantage of the gherkin language is that it's readable by the business, and in an ideal world forms part of the Conditions of Acceptance around a PBI. Also, using a Visual Studio plugin of SpecFlow , you can integrate your Gherkinised COAs into your solution with feature files, and then drive the automated tests, however, for this post I will focus solely on how to effectively gherkinise your acceptance tests. A Feature file consists of a feature outline, which details what the feature file is testing followed by Scenarios and examples (parameters).  The BDD scenarios are made up of a Given, When, Then... These are effectively an initial state (Given), an action (W...
6 comments
Read more