Friday, 25 January 2019

Imprompute Hack Day!

Yesterday we were on a company away day. A day of talks, workshops and speakers both internal and external. Covering a range of subjects around things like technology, design, data science and psychology.

All very interesting, except our team missed a couple of hours in the middle of the day because we were dealing with a thing. But we still had an interesting session where we did a lot of learning!

Ok. Full disclosure. We did kind of cause the thing in the first place. And in the interest of embracing failure and learning from it, I'm sure nobody will mind me blogging about this...

Wednesday, 2 May 2018

I nearly didn't write this blog post. It seemed too obvious.

There's a phrase that I've caught myself using a few times recently and I really need to stop.
I was going to say that - but it seemed so obvious.

Or another one that comes up now and again.
I was going to suggest that, but it sounded silly!

Every time I've said one of these things I've kicked myself afterwards.

Friday, 13 April 2018

Daily Standups - How do you do yours?

Another blog post that's basically an extension of a Tweet!

We all know that when it comes to building software, there's no one right way of doing anything, and that rules and best practices are only really meant to be treated as suggestions and guidelines. It's agile, innit!

But what is the best way of doing a stand up? Or a scrum? Or whatever you call it...

Wednesday, 21 March 2018

Yes. No. NULL. Aardvark.

We're building something at the moment that relies on several services talking to each other.

We've already established contracts between all of them so everyone knows what format to expect.

Work has started on all of these systems in parallel, so we've got a lot of stubs and mocks.

So how do we know it's all going to work when we start actually passing data around?

Thursday, 9 November 2017

It works... And also it doesn't.

Just a quick one while it's in my mind space...
Testers need to make sure that something works, but also make sure that it doesn't not work.
This is another one of those phrases that I've been trotting out for so long I've forgotten if I invented it or just stole it from someone cleverer than me. I said it in a planning meeting yesterday and had a room full of confused people looking at me.

If something works how can it also not work?

Tuesday, 18 July 2017

Alexa-ing the Worcester Wave

This page still gets a few hits per day, so I've broken out the steps and example code into a bitbucket repo. If that's all you're after then head over there now -->


Our new boiler came with one of those WiFi thermostats that everyone has these days. Unfortunately, not a Nest, as that would have knocked a couple of years off the guarantee. So I went with the sensible OEM option and ended up with a Worcester Bosch Wave.
While it does come with a half decent smartphone app, it doesn't appear to be compatible with Google Assistant, Alexa, IFTTT or any other third party do-things-with-stuff type services. Which is a shame - mainly because I just bought an Echo Dot on #primeDay!

Or so I thought...

Tuesday, 13 June 2017

Your test team is a challenge - not a safety blanket!

It seems that the 'us and them' relationship between devs and testers is gradually dying out. But I'm not so sure that this was entirely a bad thing. I've even experienced developers almost relying on their testers as a safety net. You need a bit of healthy competition.

A while ago I heard a developer say:
"That'll do. If it's not right then Test will spot it..."
While I appreciate this vote of confidence, it felt as if he was just passing the buck.