Skip to main content

Feb 21, 2022 - 3 minute read - Racket

How far to investigate?

TLDR; Go as far as you can, while you are still adding value to the person who is following.

How Far To Go?

This content was originally created using Racket. Listen to the Audio on Racket.com

So when you find a defect, how far should you go in your investigation?

It varies depending on the application and the team you working with. So the general answer is… as far as you can while your investigation is still adding value.

You need to go at least as far as to confirm that it is a problem, to identify the reasons why this is a problem.

What Oracle does it violate?

  • Because it doesn’t match this requirement.
  • Because it violates this standard.

You need to go at least as far to know if it is repeatable or not. At least as far to try and isolate the scenario under which it is repeatable.

If that is within your control… be aware of the limits of your control. If you have to request permission to access some new system, so that you can then do an investigation, then it might be important, but it’s a step too far at the moment.

  • Raise the issue. And then explain, during the raising of it, what has constrained your investigation. Then stick those permissions on the back burner.

Should you fix it?

One of the questions people always have is “should you ever go so far as to write the solution?”

“Should you ever go so far as to fix it?”

And the answer is… well maybe, possibly:

  • if you can.
  • if that’s within the process.
  • If you can do it as fast and as well as The programmers, or whomever, is going to follow to actually do the work.

If you can’t do it as fast, or you can’t do as well, then you probably shouldn’t.

You should probably go as far as you need to provide the information that the next person needs to do their job.

Quiz Time

As a simple example.

If you find a broken link on the site, do you:

  • A) take a screenshot of the broken link? A screenshot of having clicked on the broken link and then write a defect that says, I found a broken link on this page.

or do you

  • B) figure out if the clickable link should be there in the page at all? And if so, where should it actually point to. Then raise a defect explaining, what page you found it on, the CSS query or search term you need to use in order to find it in the source, and what the actual URL it should point to?

or do you…

  • C) learn HTML, request admin privileges to access the production server, change the code, then release the new HTML file?

Drum Roll

You do B.

Or you go as far through B as you can.

You do the investigation to find the information to help the next person.

We follow the 80/20 rule as much as we can, 80% of the value comes from 20% of the effort. If you are having to expand more effort in the investigation process, than someone else would in the fixing process, then you’re going too far.

If your investigation process starts bypassing the fixing process, then you went too far.

If people have to ask a lot of questions about the defects raised in order to fix them then, you have not gone far enough.

Go as far as you can, while you are still adding value to the person who is following.

In other words, go as far as you can, to make it easy for the next person.

And sometimes that next person is you.

This was originally recorded on Racket in 202107


You will need a Github account to comment. Or you can contact me with your comment.

I reserve the right to delete spam comments e.g. if your comment adds no value and its purpose is simply to create a backlink to another site offering training, or courses, etc.