Skip to main content

Famous Movie Quotes applied to software engineering - Dirty Harry



Do you feel luck punk? Well.... Do Ya?


I've spoke of it in my very first blog post, about a developer who blindly put their code live without any testing, without any consideration for the side effects that may have been caused by his changes. I've got to think that before he put it live, that he asked himself "Do I feel lucky?" there's no other explanation for why he did what he did!

So now, if anyone were to come to me and say I'm putting this live, without any testing (ignoring the gates that he/she would have to go through in order to get anything live..) I'd have to say to them:

You've got to ask yourself one question: 'Do I feel lucky?' Well, do ya, punk?

Comments

  1. So this sort of movie will work as a great source of entertainment in true words. Due to is humor feature this movie is ranked. watch free movies

    ReplyDelete
  2. 123movies free, Watch HD Movies Online For Free and Download the latest movies without Registration at 123Movies.
    watch series Online

    ReplyDelete
  3. the finest selection of movies on the entire internet. You can just Search Movie name ON your computer and watch the movies of your choice, all from the comfort of your home. 123movies

    ReplyDelete
  4. Crush and smash film or still pictures as 3D pieces detonate to uncover the following picture from Pixel Film Studios. With the 3D camera and lights in Movement 5, clients can produce their smash results to the following level. Turn, rotate or container around the media as it breakes into many minor pieces. FCPX Templates

    ReplyDelete
  5. This is on the grounds that the inward parts of the application won't be as natural to a great many people as non specific off the rack programming will be. https://www.sigmanest.com

    ReplyDelete
  6. People who create viruses for computers are always coming up with new approaches. This means the good guys have to also come up with new solutions and safeguards on a regular basis. Getintopc

    ReplyDelete
  7. Mmm.. good to be here in your article or post, whatever, I think I should also work hard for my own website like I see some good and updated working in your site. http://www.getinntopc.com

    ReplyDelete
  8. Wow Very Nice Information Thanks For Sharing It.
    file hippo

    ReplyDelete
  9. Watching movies is has never been this agreeable! You get the chance to invest quality energy with your family. www.123movieshub.it

    ReplyDelete
  10. This comment has been removed by the author.

    ReplyDelete
  11. Wow very nice information.Thank You So Much Sharing It.

    ReplyDelete
  12. nice and more useful information by the admin

    ReplyDelete
  13. This is one awesome blog post.Much thanks again. Great. software download

    ReplyDelete
  14. Softhives
    Get your hands on latest mac and pc software. You can download unlimited games and pc applications cracks easily. PowerISO Crack With Activation Code

    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...

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...

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...