Skip to main content

Windows Hate


So sometimes I'm a consumer. I like to think a reasonably savvy consumer, but a consumer nonetheless. And when something that I have paid for and depend on doesn't work, as a consumer, I don't like it.  Not just that, I actively resent it. Time I spend making it work is time I am not spending on something of more value to me. I already paid for that thing. It should work.

But the intellectual challenge of finding the solution? Means nothing.

But the sense of achievement when it's resolved? Don't give me that. I've no time for it. I'm all about how now I can get on with what I have to do, and with the backlog of stuff I didn't do because I was fixing that thing that I already paid for, and the new backlog that's building up while I deal with the old backlog, because of that thing that I depend on, that should just work.

So an unreasonable consumer? Not from my point of view.

As a consumer, I recently encountered a Windows 8.1 update issue with KB2919355. It failed and rolled back, with a banal message displayed and no information on where I might get more details on the failure.

Each attempt took around 30 minutes.

I made plenty of attempts.

I tried letting Windows Update do it automatically, I downloaded the update and ran it manually via Windows Update, I downloaded the update and ran it from the command line, I rebooted and was forced to reapply the update, I was forced to reboot and unintentionally applied the thing during attempts at fixing the damn thing. The thing that I paid for, that I depend on, that should just work.

I spent a lot of time on Microsoft and other forums in the virtual company of other poor souls in a similar position to me but with different environments, error codes, error messages and conflicting and incomplete advice from well-meaning onlookers whose systems, that they'd paid for, that they depended on, all appeared to be working.

I uninstalled the update, I cleaned out the older versions of the update with dism, I reviewed the status of my file system with sfc, I installed with and without peripherals attached, I uninstalled VPN software, I spent an awful lot of time looking at various log files, I edited my registry and more.

And I fixed it. In the end. But my goodwill towards Windows 8, which I've otherwise been getting on with pretty well, having made the jump straight from XP, was reduced. With your software development head on you might say this is not particularly rational. It's a product. It was some kind of bug. These things happen sometimes. Most people were OK.

But I am a consumer, and I paid for that thing, and I depend on it, and it happened to me and it wasn't fixed right away and I had to spend my time to fix it and maybe I'll think a bit more about other alternatives next time I'm ready to part with some cash.

Are your customers consumers?
Labels:

Comments

  1. Peter HozákJuly 3, 2014 at 3:36 PM

    I've seen people struggle with Linux, with pe̶r̶lrogramming languages and with browsers as well and complaining about it just as righteously, so I don't think the emotion is dependent on having spent some money on the product.

    Perhaps quite the opposite might be true - the more you pay, the less serious the problems seems and the less likely you are to complain about how a bad decision you've made... Would you write a blog about this if the privilege to install the update cost you £2,000?

    ReplyDelete
  2. James ThomasJuly 4, 2014 at 6:41 AM

    @Peter. I might have resented the time spent even had I not paid for the software in question, true. With free software such as a browser, though, I might also have just given up and used another rather than spend the time fixing a particular one. (And I have done this.)

    I don't know whether I would feel more or less justified in complaining at some particular absolute price point. I have written before about how relative costs - including the purchase cost, my time, opportunity cost and so on - can combine in some notion of value and affect judgements.

    ReplyDelete

Post a Comment

Popular posts from this blog

Can Code, Can't Code, Is Useful

The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "If testers can’t code, they’re of no use to us" My first reaction is to wonder what you expect from your testers. I am immediately interested in your working context and the way
Post a Comment
Read more

Testing (AI) is Testing

Last November I gave a talk, Random Exploration of a Chatbot API , at the BCS Testing, Diversity, AI Conference .  It was a nice surprise afterwards to be offered a book from their catalogue and I chose Artificial Intelligence and Software Testing by Rex Black, James Davenport, Joanna Olszewska, Jeremias Rößler, Adam Leon Smith, and Jonathon Wright.  This week, on a couple of train journeys around East Anglia, I read it and made sketchnotes. As someone not deeply into this field, but who has been experimenting with AI as a testing tool at work, I found the landscape view provided by the book interesting, particularly the lists: of challenges in testing AI, of approaches to testing AI, and of quality aspects to consider when evaluating AI.  Despite the hype around the area right now there's much that any competent tester will be familiar with, and skills that translate directly. Where there's likely to be novelty is in the technology, and the technical domain, and the effect of
Post a Comment
Read more

Testers are Gate-Crashers

  The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "Testers are the gatekeepers of quality" Instinctively I don't like the sound of that, but I wonder what you mean by it. Perhaps one or more of these? Testers set the quality sta
3 comments
Read more

Am I Wrong?

I happened across Exploratory Testing: Why Is It Not Ideal for Agile Projects? by Vitaly Prus this week and I was triggered. But why? I took a few minutes to think that through. Partly, I guess, I feel directly challenged. I work on an agile project (by the definition in the article) and I would say that I use exclusively exploratory testing. Naturally, I like to think I'm doing a good job. Am I wrong? After calming down, and re-reading the article a couple of times, I don't think so. 😸 From the start, even the title makes me tense. The ideal solution is a perfect solution, the best solution. My context-driven instincts are reluctant to accept the premise, and I wonder what the author thinks is an ideal solution for an agile project, or any project. I notice also that I slid so easily from "an approach is not ideal" into "I am not doing a good job" and, in retrospect, that makes me smile. It doesn't do any harm to be reminded that your cognitive bias
Post a Comment
Read more

Play to Play

I'm reading Rick Rubin's The Creative Act: A Way of Being . It's spiritual without being religious, simultaneously vague and specific, and unerring positive about the power and ubiquity of creativity.  We artists — and we are all artists he says — can boost our creativity by being open and welcoming to knowledge and experiences and layering them with past knowledge and experiences to create new knowledge and experiences.  If that sounds a little New Age to you, well it does to me too, yet also fits with how I think about how I work. This is in part due to that vagueness, in part due to the human tendency to pattern-match, and in part because it's true. I'm only about a quarter of the way through the book but already I am making connections to things that I think and that I have thought in the past. For example, in some ways it resembles essay-format Oblique Strategy cards and I wrote about the potential value of them to testers 12 years ago. This week I found the f
Post a Comment
Read more

Meet Me Halfway?

  The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "Stop answering my questions with questions." Sure, I can do that. In return, please stop asking me questions so open to interpretation that any answer would be almost meaningless and certa
Post a Comment
Read more

Test Now

The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "When is the best time to test?" Twenty posts in , I hope you're not expecting an answer without nuance? You are? Well, I'll do my best. For me, the best time to test is when there
Post a Comment
Read more

Rage Against the Machinery

  I often review and collaborate on unit tests at work. One of the patterns I see a lot is this: there are a handful of tests, each about a page long the tests share a lot of functionality, copy-pasted the test data is a complex object, created inside the test the test data varies little from test to test. In Kotlin-ish pseudocode, each unit test might look something like this: @Test fun `test input against response for endpoint` () { setupMocks() setupTestContext() ... val input = Object(a, OtherObject(b, c), AnotherObject(d)) ... val response = someHttpCall(endPoint, method, headers, createBodyFromInput(input) ) ... val expected = Object(w, OtherObject(x, y), AnotherObject (z)) val output = Object(process(response.getField()), otherProcess(response.getOtherField()), response.getLastField()) assertEquals(expected, output) } ... While these tests are generally functional, and I rarely have reason to doubt that they
Post a Comment
Read more

A Qualified Answer

The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn ,   Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "Whenever possible, you should hire testers with testing certifications"  Interesting. Which would you value more? (a) a candidate who was sent on loads of courses approved by some organisation you don't know and ru
Post a Comment
Read more

README

    This week at work my team attended a Myers Briggs Type Indicator workshop. Beforehand we each completed a questionnaire which assigned us a personality type based on our position on five behavioural preference axes. For what it's worth, this time I was labelled INFJ-A and roughly at the mid-point on every axis.  I am sceptical about the value of such labels . In my less charitable moments, I imagine that the MBTI exercise gives us each a box and, later when work shows up, we try to force the work into the box regardless of any compatiblity in size and shape. On the other hand, I am not sceptical about the value of having conversations with those I work with about how we each like to work or, if you prefer it, what shape our boxes are, how much they flex, and how eager we are to chop problems up so that they fit into our boxes. Wondering how to stretch the workshop's conversational value into something ongoing I decided to write a README for me and
Post a Comment
Read more