Refining history

Heyhey!

I love Hannibal TV series. It's something you don't want to watch while in delicate mental state or eating, but other than that I think it's finally something that meets the level of quality that the legacy of Hannibal Lecter deserves and raises the bar (almost) to the height where it was after Silence of the Lambs.

Speaking of quality, in one the latest episodes of Hannibal Dr. Lecter stated: "It's the distinction that adds an expectation of quality." This is something that attracted my attention to the extent of writing this blog post.

NTD2012 roundup - day 1

Heyhey!

It's been awhile. Again. Even though I'm working on three assignments and haven't got the time to write down all the ideas that are swarming in my mind, things are pretty awsome right now. Namely all of these assignments offer intellectual challenges I've been yearning for so long now; Quality management with some of the most brilliant developers I've ever worked with, testing center of excellence handyman activities in super friendly and responsive environment and a pretty sweet exploratory testing gig for even sweeter product...

Plus I'm getting married soon! Exciting times! \o/

But enough about the hype. Topic of today is Nordic Testing Days 2012 roundup, which unfortunately has been delayed due to the before mentioned reasons. I'm tackling these lightning style i.e. a very short summary about the subjects that touched my heart and mind, divided in two days as the conference itself. This lightning style is of course because of the latency, which have made me to forget things. Very familiar situation in software testing too... ;)

So, time to get tackling (click the headlines for presentation material)!

Tester 3.0

Heyhey,

Just recently my colleagues presented this idea about Tester 2.0. Tapani Aaltio even gave an interview about the subject in EuroStar TV. Go Tapsa!

In short Tester 2.0 integrates itself more deeply into the SDLC, understands it better and creates more value this way while Tester 1.0 just does it's job, doesn't collaborate, pretty much stays put and tests. On this level I'm all for Tester 2.0, but what worries me the most is that in the dark side of all this lies the will to make us all developers...

So let's talk about Tester 3.0.

Community Service

Hi,

I've stumbled across a familiar problem. I've started to write about several subjects. I've been writing with pure joy, from the heart, but when it comes to the the actual professional stuff, the boring stuff, the joy stopped. And so did the writing. According to Belbin Team Inventory assessment, I have very strong tendency towards Resource Investigator and Plant, with a hint of other roles, but no Completer/Finisher. Not even a single bit. Ok, Wikipedia puts Completers/Finishers to be quite anal characters, but it see them as people who get things done, which is an admirable quality. And I lack that, dammit!

And there I go again with the jibberjabber! To dodge this issue, instead of sticking with the original plan, starting with the basics of testing, I'll just write about this happening I participated and how it grew thoughts in my mind...