A study was done to pay people to build sand castles. In the experimental group, the people were told afterwards to knock down their sand castle (because the researchers said they wanted a different sand castle or something to that effect). In the control group, people were also told to build a new sand castle but in a different spot and so they would leave their other castle there. In the experimental group, people became very very demotivated and felt that their work was pointless and boring. It doesn't matter if you're ADHD or not, if your expectations are greater than reality and you have to kick your sandcastle over after building it, you're not going to do as well at your job.

As a code reviewer they should be giving you a compliment sandwich where the criticism or constructive feedback is placed in between two compliments. As a coder, I've found adding async and await to functions does a lot to make your code look sexier to code reviewers even if it doesn't have a perceptible performance impact on non-network calls.

If I were to comment on a new plan for you, I'd say let flow state be your friend and not your enemy. After all, you have a chair you probably have to sit in for ~8 hours a day while you stare at a computer screen full of code and that's hard for anyone to do for that long let alone someone with ADHD. Flow state will give you an advantage over others. Invariably, your flow state will break. Use that time to spend more time talking to the stakeholders in your group because sometimes stakeholders want what they want and nothing else. They'll appreciate the time you took to listen to them, they'll trust and believe in you more (instead of you being an unknown variable), they'll be more confident that they'll get what they want, and you'll benefit from the confirmation bias. If you deliver what they want, it's less likely that their sandcastle will get kicked over -- though still not unlikely.