Firstly, fuck. That sucks. Here's my penny's worth, as someone with no actual experience of the disease: From a programming and work perspective, make sure th

Firstly, fuck. That sucks. Here's my penny's worth, as someone with no actual experience of the disease: From a programming and work perspective, make sure that other people have the knowledge and skills to take over. Little things that should be obvious (and ideally avoided up front), but only in hindsight, like write access to repos, third-party accounts linked to email addresses. Now is a good time to audit them. And the bigger things, like "so how is this library Charlie wrote supposed to work?" Now might be a good time to pair with someone unfamiliar with it to make sure documentation is up-to-date and encompasses what the intention behind the decisions was. Depending on what you're working on, there might be a point in the future at which you might be inadvertently capable of harm: accidently publishing secrets, etc. I don't know enough to know how best to mitigate this, or even if it needs worrying about at all in your work. If you've got any projects that have downstream users, you might want someone else to also have write access to the project. Managing their expectations on the future may be of use to them. Consider getting pictures/video of your favourite projects, people and places in the work environment; I've heard these sort of external memory cues can be helpful later on in sparking recall of memories. Best of luck in what is going to be a trying time for you and your loved ones.