I tend to use a simple txt, it is always open on my editor, and I put there the TODO, or any bug I found. If I have to persist this information I tend to use gi

I tend to use a simple txt, it is always open on my editor, and I put there the TODO, or any bug I found. If I have to persist this information I tend to use github issues and use a PR flows, but in general a txt is more than fine. I've been working like that for 6 months in a row, alone. And I have to tell you when I'm tired of backend programming I move to the frontend , doing some visual adjustments, just for fun and mental health, then I switch back to the backend and so on, also this cycles are switched by testing, design, programming, flow design etc...