RogerBW's Blog

The Tripartite Problem Report 22 June 2017

I think I have come up with a new and potentially useful paradigm for computer-related problem reports.

The report should consist of three parts:

  1. I am trying to achieve X.
  2. I am performing action Y.
  3. Unexpected thing Z happens.

The Y and the Z constitute a conventional report, at least one that's been written by someone who understands that computers are not magic, at least not in the way they think of magic: "When I press foo I get an error message that says bar". X is also helpful.

Sometimes the X can be derived from the Y, and even the Y from the Z: if the program crashes when you save a file, it's pretty clear how to break it down. But it's beneficial to the problem-solver to have it all laid out, and it can be beneficial for the reporter to think about it too (hmm, it doesn't happen every time, only for files with spaces in their names).

Some problems lie in the X rather than the Y/Z. Many times I've seen a technical forum get into intricate details of exactly how to make a particular program act in a particular way, when a far easier solution to what the user actually wanted – which had never been mentioned – was actually to use a different program. (This is in the non-corporate Linux world, where software is, to a first approximation, free, and where a task will typically involve using a chain of different small programs rather than one huge one – it's not as if one were saying "use LyX instead of LibreOffice" and disrupting someone's entire working practices.)

And sometimes action Y will work perfectly well, except for a few obscure edge cases, which one won't tickle until one knows more about the state of the rest of the system when Y happens.

Tags: computing

Comments on this post are now closed. If you have particular grounds for adding a late comment, comment on a more recent post quoting the URL of this one.

Tags 1920s 1930s 1940s 1950s 1960s 1970s 1980s 1990s 2000s 2010s 3d printing action advent of code aeronautics aikakirja anecdote animation anime army astronomy audio audio tech aviation base commerce battletech beer boardgaming book of the week bookmonth chain of command children chris chronicle church of no redeeming virtues cold war comedy computing contemporary cornish smuggler cosmic encounter coup covid-19 crime cthulhu eternal cycling dead of winter doctor who documentary drama driving drone ecchi economics en garde espionage essen 2015 essen 2016 essen 2017 essen 2018 essen 2019 essen 2022 essen 2023 existential risk falklands war fandom fanfic fantasy feminism film firefly first world war flash point flight simulation food garmin drive gazebo genesys geocaching geodata gin gkp gurps gurps 101 gus harpoon historical history horror hugo 2014 hugo 2015 hugo 2016 hugo 2017 hugo 2018 hugo 2019 hugo 2020 hugo 2022 hugo-nebula reread in brief avoid instrumented life javascript julian simpson julie enfield kickstarter kotlin learn to play leaving earth linux liquor lovecraftiana lua mecha men with beards mpd museum music mystery naval noir non-fiction one for the brow opera parody paul temple perl perl weekly challenge photography podcast politics postscript powers prediction privacy project woolsack pyracantha python quantum rail raku ranting raspberry pi reading reading boardgames social real life restaurant reviews romance rpg a day rpgs ruby rust scala science fiction scythe second world war security shipwreck simutrans smartphone south atlantic war squaddies stationery steampunk stuarts suburbia superheroes suspense television the resistance the weekly challenge thirsty meeples thriller tin soldier torg toys trailers travel type 26 type 31 type 45 vietnam war war wargaming weather wives and sweethearts writing about writing x-wing young adult
Special All book reviews, All film reviews
Produced by aikakirja v0.1