Steps: How To Approach A Vague Ticket (Step 1)
Steps: How To Approach A Vague Ticket (Step 1)
Excuse the in hours blog post. My thought is that it's okay to write a blog post if it's 100% work related. And I am just writing up my notes from a meeting. (Which are safe to share). This is the way that I will
- phrase them coherently
- find them
- review them
So here we go. I have been struggling at work with tickets that feel vague to me. But these are the way tickets need to be written. To save the seniors time. Otherwise they might as well do the tickets themselves (sometimes). So how might I work with vague tickets? Here are a few proposed first steps. Step 1 is to find where in the code the problem is.
Step 1: Where is the problem in the code?
The very first step in solving the problem is to ask myself where is the code that needs to change. I'll repeat this a thousand times if I need to. Where is the code that needs to change? Where is the code that needs to change? Where is the code that needs to change? I need this on a post it on my screen.
I need this written out somewhere. Where is the code that needs to change?
So it's about finding that code. And if I can't find it then I can ask where it is but it's better than just going "Arrrgh." (P.S. I put about 20 seconds of effort into these images but it's a massive memory boost!). And then my wonderful mentor/colleague gave me some more steps
Can we see the problem in the code?
The first thing to do is to go: where is the problem in the code? And then: can we see the problem in the code? Can I see at least one place in the code where there is this problem? Can I see at least one place in the code where there is this problem? And then:
- Make a list of all of the places in the code where I can see this problem
- Use this list to define a solution; possibly seeing all the places in the code where the problem is will help me to come up with the best solution
- Possibly run the solution
Past a colleague if I need to so I don't waste time and work. I am going to redo a version of this blog post
- One more time so that it sinks in
- Possibly two more times (on different days so that it sinks in)
- I want to do one more version of the two posts I did last night on focusing on my goals.
And so for this ticket:
- I'm going to make a list
- I'm going to go through all the files
- And make a list of all of the places where I can see the problem
- Then I'm going to turn them into a to do list
- And add them into the comment on the asana ticket - so that I can show my process. 🏞

Comments
Post a Comment