Painting of the walls completed, some minor painting of woodwork remaining. 3 of the 4 lights back in place, one has some minor patching remaining. Radiator back in place, and hot water system re-pressurised. New blind and curtains in place. Almost there! (Yes, there's one wall that's not been painted...)
Ceiling completed with a coat of magic pink paint! (Hopefully, it will dry white as advertised...)
Most of the walls painted - just a few places where the patching of cracks etc. is still ongoing (the cold weather is extending the drying time).
Crack-filling base coat in place and dry, window frame undercoat and gloss top coat completed.
Lights patched.
Removed the radiator for painting.
Patching the walls almost completed.
Patching the lights.
Removing two layers of old skirting board to get down to the original skirting.
Patching the walls.
Signal vs. Noise nail what makes a bad outage notification:
“One of the worst stock dummies that even I have resorted to in a moment of weakness is this terrible non-apology: ‘We apologize for any inconvenience this may have caused’. Oh please.”
This puts me in mind of Joel Spolsky’s take on what makes a good one:
“… we set up a blog where we would document every outage in real time, provide complete post-mortems, ask the five whys, get to the root cause, and tell our customers what we’re doing to prevent that problem in the future.”
I want every site I use as a service to do this. Not one of the systems I’ve experienced which were supposed to tell me about outages have ever done the job properly.
From the Agile in Action blog:
“Quality goes down and technical debt increases with every corner cut. When prioritized against the next feature promising to deliver business value, debt never gets repaid.”
“[Business decision makers] understand the cost of goods returned, the cost of rework, and the loss of customers but they choose to remain ignorant of the fact that these are typically the consequences of not valuing quality.”
How very true!
Shame, Jake, shame!
I’m certainly not opposed to experimentation on the general public – in fact, I think it’s a good idea.
But this is just crazy.
Yeah yeah, I know, I know. The main problem is that work is going well, apart from the fact that we’re all flat out getting the next beta release ready for public use. It’s a rather big one! Oh, that and the change of address.
I’ll start posting again once the desk comes for the spare room, and I can set up my computer again. Promise!
In the mean time, Demian has some nice things to say:
“OpenX don’t have as much to worry about as I first thought.”
Thanks!