Skip to main content

By changing everything, will anything change?


I just resigned from my +seven (wonderful) years spell at Qentinel working as a SW testing consultant, and am now starting as a SW test engineer at Philips Medical Devices.

The biggest reason for this was that I wanted to remain working as a SW testing specialist but change everything else. Here the everything else means that I will move from:
1. Customer acceptance testing role -> Developing our own products
2. Waterfallish -> Agilish project models
3. Business oriented & simple -> Mission critical & complex domain
4. 8000km from developers -> Few meters from developers
5. Consultant -> Employee
6. Non-technical -> Technical

I am really motivated and enthusiastic about the change. And also perhaps a bit scared if nothing actually changes?

I think that the three main root-causes of most of the many problems that I have encountered in my past career have been due to:
1. lack of communication
2. lack of time
3. lack of understanding on why stuff is being done

I have high hopes that these won't be the biggest issues at Philips.

Time to find out :)
Labels:

Comments

Post a Comment

Popular posts from this blog

Testers doing test automation - is that the most important thing for you to do right now?

I've been thinking quite a lot about tester's moving to do test automation.  Lately beause of these three things: 1.  European testing conference , a great testing conference I attended couple of weeks ago. It is very cool due to many things; the way the speakers get compensated, the focus on the conferring side of conferences making it very easy for people to discuss stuff, the way the talks are chosen, and because there are also a lot of developers joining. So anyway when I was talking with several of the attendees, it was a bit strange how it was easier for me to talk about the product development as a whole with the developers, where as with the testers it more naturally moved into talk of automation and tools. Also on the open space, I think the majority of the topics pitched was automation or tool related. And quite little on the process or on the customer facing side of product development.  2. In my company there are a lot of different products and...
3 comments
Read more

Testing drunk

(My first blog writing ever.) I've been thinking a long time that it's funny how many bugs I find by accident. Try to do something, make a mistake and boom - a bug is found.  Making the mistakes intentionally doesn't quite work - that's why they are called accidents I guess.. So I've thought of ways to make myself more prone to accidents, coming up with an apparent one; testing drunk. TUI (testing under the influence). So this I gotta try. More to come on that later.
3 comments
Read more

Six reasons why testers should do code reviews

I have had quite a lot of discussions about code reviews. Quite many also with testers, by which I have understood that many do not do those. I will not start arguing here on whether code reviews are good/important or not. But I will list a few things why I think testers would benefit of doing them. 1. Code is the only documentation that is up to date . If you really want to know how something really functions, you want to be able to see and read the code. 2. Knowing more about the thing done enables you to do better testing . You can spot things that you should definitely test, and things that you probably don't need to test that much. Like extra things added by coder, usage&modifications of existing functions, data types, etc. And to arguments thinking that one loses their "independence" as a tester by knowing too much, I would worry a lot less about that than about testing stuff that you have no idea on how it has been built. 3. Improve logging . I obse...
2 comments
Read more