Skip to main content

TV Quotes applied to Software Engineering.... Quabity Ashuance??

Apologies for the lack of posts recently, I spent last week in Disneyland Paris having a truly awesome time. I am going to be writing another blog post about that at a later date... however as a stop gap...

I was rewatching The US Office for the umpteenth time yesterday and was watching this episode which made me laugh, as I've met some people in Testing/QA (not getting into that debate right now), who this would be perfectly applicable to! They've come into testing just to get paid and are lacking some of the fundamental skills, and do the bare minimum to get by.... And whilst this video in particular is not related to Technology, but I still thought it was funny!


I must admit it is becoming less and less as times move on, maybe it's because I know what I am looking for when hiring good QAs so I tend to cross paths with these people less and less, or maybe (and perhaps far more likely :) ) there is a shift in recognizing QA/Testing as a valuable Career Path so people devote more time to learning and progressing.... either way it's good to see.






Comments

  1. Hiring a good QA engineer is very important for the further working process. I have been searching near 4 months for qa in http://www.nixsolutions.com/services/quality-assurance-services/ quality assurance company. It was difficult to find a specialist with good experience and knowledge.

    ReplyDelete
  2. Simply duplicate the organizer you have recently separated, and glue it into the PSP's "SAVEDATA" envelope.
    click here

    ReplyDelete
  3. In this age of hypocrisy, the writer has written every word with all his soul poured into it.
    resumeyard.com

    ReplyDelete

Post a Comment

Popular posts from this blog

Delusions of Testing

So I've got in touch with my old QA friend, Richard Lee and we spoke about guest blogging on each others blogs... Richard is an IT Professional for a FinTech based company in London. His activities vary from Release Manager, Build Manager, Database Administrator. Working in a Microsoft workshop, his expertise lies in MSBuild/Workflow/Powershell/SSAS/SSIS/SSRS/SQL, basically whatever isn’t anyone elses’ problem is Richard's problem! When not solving other peoples problems he can be found blogging at redphoenix.me , and jogging to and from home, where he lives with his heavily pregnant wife. Hello, my name is Richard, and I am a former tester. Like most people and their careers, I fell into testing; I first got into testing about 6 years ago, after I had graduated. I went to a university where the attitude was that you should try to get on a graduate scheme with one of the big companies. If you weren’t interested in that, well, good luck with getting any support from ...

QA is Awesome!

No real point to this post other than I have had the song stuck in my head and figured I could change it slightly and quite easily make QA is Awesome! Oh and I haven't even seen the movie all the way through! But for some reason that song is incredibly catchy! Not much point to this post in fact, just thought I'd put it out there :)

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