Focusing on one ticket at a time: a guide for AuDHD

Picture the scene. Monday morning. You come in.

Emotions are flying high. Because why wouldn’t they be? They are always high.

There’s so much going on. 

A billion people have posted on slack and maybe one or two people have messaged me.

Maybe I have some other issues on my mind. Maybe there’s a performance issue I’ve been working on (hello, AuDHD) and I’m thinking about that. Maybe on Friday night I did a big rebase and it’s all on my mind. Maybe I am waiting on the review of a big PR. So how do I sit down and focus.

If this is just the baseline - where’s the room for my actual work. What do I focus on. 

It was probably hard for me to get out of bed today and I may or may not have had breakfast and if I haven’t there’s a battle between focus on work and grabbing some food - but there’s nothing I want to eat anyway around. So ladies and gentlemen and gentlefolk what do I do?

I have myself covered. I just focus on the next ticket. I just focus on the next ticket. I just focus on my current ticket, whatever it is, one ticket at a time.

One ticket at a time 

One ticket at a time. One ticket at a time. One ticket at a time. My new ticket is part 3 of a four part process. So what do I need to do? I need to make a branch coming off the last one. I need to wait for a review on a test by a colleague on branch two. Worst case I will rebase onto that branch with whatever changes I have made on branch 3. I need to grok the ticket anyway first and process it. I also might want to glace over and partly grok part four just in case there is any relevant info.

And when the test gets reviewed - then I can merge. Now I think about it I might not need to rebase as my branch as my test was already a revision.