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

Periodical retrospectives are lame

  "You got nothing, not a single thing?! Well lets just end this here then." I remember well when I said this, being very frustrated. About ten years ago I had been working as a Scrum master for a team some months, and putting quite a lot of effort into planning our scrum teams sprint retrospectives. Lot of work also because I felt we were not getting too much out from them; not very good discussions, very few actions, and even the few actions we did come up with did not stick.  And then it happened: a retro where none of the participants came up with anything to say about the sprint. Regardless of the retro topic boxes, reading of books on retrospectives, getting inspiration from tools like retromat.org, having them in different places, using all kinds of different formats and rainbow coloured post-it notes. Not a single thing. Blank.  So then I said the words, out of frustration, mainly to myself. Why couldn't I get this thing everyone is so hyped about to work? After t
Post a Comment
Read more

I don't report bugs

I don't report bugs . Bug is such a loaded word that people understand very differently, that instead of using it and explaining what I mean by it I rather just use other words. Like observations, thoughts, surprises, ideas, alternatives, or something similar. (And no I don't use fault, defect, or error either). Bug has also quite a negative connotation. "Reporting a bug" is kind of like telling someone that they've been served. And as we are actually giving away the gift of information, why wrap it in such a nasty package? And maybe more importantly it is very likely that whatever you might have to say is wrong. If not plain wrong, then at least incomplete. So I like to approach the kind of situations with the assumption that I am probably wrong. Cutting off anything that might sound arrogant makes stuff quite a lot easier. Especially after you realise later on that you have been wrong. I leave plenty of observations unreported . I don't want to waste
Post a Comment
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