I have a unique perspective on this, as I have had problems with cognitive clouding, have all my life, but have still managed to be a good data scientist. Firs

I have a unique perspective on this, as I have had problems with cognitive clouding, have all my life, but have still managed to be a good data scientist. First, do all of the responsible things listed below (estate attorney, eat healthy, etc.), and remember that real life comes first. For day-to-day with programming, start building in more of a buffer in your timeline for bad days. Sometimes, despite your best efforts, you might find yourself unable to grasp or find concepts mentally. It is frightening; if you can, work on coping skills with a therapist. Getting anxious will usually make things worse. Build a time buffer into more of your estimates so you can balance good days with bad days. You might not be able to be reliable every day, but you can achieve reliable results with the right planning. Realize that taking good notes and documenting well is going to help someone else take up a task on your behalf, but also help yourself if you're having a bad day. It takes discipline to take the time to document when you're on fire and having a good day. Work on doing it anyway. Work with your team to ensure you have new, exciting work for the good days, so you can keep your mental state fresh, as well as work that is in your wheelhouse for bad days. This is both a reasonable accommodation as well as a way for you to be more productive. Coincidentally, these are all best practices anyway. This is just a new application of them. I've gotten a lot more people on board by emphasizing these as best practices, not specifically reasonable accommodations. Please feel free to PM me if this was helpful.