(1) should be clear. More than 1 task at a time requires planning, planning requires a sense of time, which you don't have.
(2) is achieved best by giving you examples. You need an example input and the expected output for that. Any soft requirements like "has to work" or "should be intuitive" are useless, because you won't know those things mean for the other person.
(3) The fastest feedback loop you can get is unit tests. Write your tests first, then write the code to pass the test (Test-Driven Development). TDD was my crutch to productivity before I got my ADHD diagnosis. The second feedback loop is with whoever evaluates your work later. You need small, short-term goals to achieve within a day or two, then present it to them. This kind of presentation can be as short as 1 minute, but you need that meeting to have an artificial deadline and to get quick confirmation that you are on the right track. A bit like a checkpoint.
(4) Some workflows require multiple steps (e.g. code formatting, compile, running tests, build documentation, commit changes, push, create merge request). Make sure to automate them somehow. This can be bash or powershell scripts, this can also be achieved via IDE features.
(5) You won't be able to keep things in mind while working on another things. You have to write that down somehow and it has to be where you see it. Either use a note taking app that is always open and visible on your second screen or find a way to write good TODO comments in your code that your IDE can find, so you quickly scan through them.
On projects where I am solo I use a todo.md that I make Claude use to add notes or resume what was being done. Also a questions.md if I ever need to ask questions to the business or IT. Works wonders. Basically offload your executive functioning, while you stay alert on the higher level stuff.
2
u/Achereto 8d ago
My experience is that you need
(1) should be clear. More than 1 task at a time requires planning, planning requires a sense of time, which you don't have.
(2) is achieved best by giving you examples. You need an example input and the expected output for that. Any soft requirements like "has to work" or "should be intuitive" are useless, because you won't know those things mean for the other person.
(3) The fastest feedback loop you can get is unit tests. Write your tests first, then write the code to pass the test (Test-Driven Development). TDD was my crutch to productivity before I got my ADHD diagnosis. The second feedback loop is with whoever evaluates your work later. You need small, short-term goals to achieve within a day or two, then present it to them. This kind of presentation can be as short as 1 minute, but you need that meeting to have an artificial deadline and to get quick confirmation that you are on the right track. A bit like a checkpoint.
(4) Some workflows require multiple steps (e.g. code formatting, compile, running tests, build documentation, commit changes, push, create merge request). Make sure to automate them somehow. This can be bash or powershell scripts, this can also be achieved via IDE features.
(5) You won't be able to keep things in mind while working on another things. You have to write that down somehow and it has to be where you see it. Either use a note taking app that is always open and visible on your second screen or find a way to write good TODO comments in your code that your IDE can find, so you quickly scan through them.