Use MyFitnessPal to track what you're eating and your goal weight. At the end of the day, it'll estimate your weight in 5 weeks if you ate like that every day for five weeks. (e.g., "If every day were like today... You'd weigh 158.9 lbs in 5 weeks")
It's a good incentive to avoid tempting, but unnecessary foods.
A C3 spinal cord injury has interfered multiple times, especially with finances and insurance.
My advice?
Automate as much as possible; Ansible, Docker, Kubernetes, and kubespray are great.
Build what you can, when you can. Try not to stress when you can't.
Learn to meditate by focusing on your breath. A calm mind is very helpful for productivity.
Establish a routine. Stick to it as best you can. (When my routine is thrown off, I'm very unproductive. Meditation helps reset my focus.)
Buy an Echo Dot. Use repeating reminders to remember the day-to-day stuff (e.g., meds) so you can stay in the zone without neglecting your health.
Keep well-named, well-organized bookmarks relevant to your illness; searching your browser history with a cloudy mind when sick is a PITA.
Learn systems biology. View it as a FSM initially so you can properly debug your body and communicate with doctors when it fails you.
Those are the tips I live by right now.
My coding work won a startup competition a few years back, but the terms of the deal weren't favorable to me due to my disability, so I turned it down.
One grand mal seizure a few months later, I forgot that I was a coder with ambitions. (The flip-side to that: I forgot that learning to code was so much fun, so I focused on languages I previously avoided.)
The project from the competition is almost completely rewritten to be nearly autonomous.
This happened to me after suffering seizure-induced memory loss last January. It was disheartening, but I'm back to normal now. (For reference, a few weeks post-seizure [mid-February], I thought the 2016 Trump/Clinton election was still 6-8 weeks away.)
Read the basics, implement them, understand their tradeoffs, then build cool side projects that require their use instead of worrying about the best way to implement a Red-Black tree.
The basics are tools you use. The projects you build with them dictate which tools will stay fresh in your mind.
If you don't need the tool, remain aware of them, but don't stress over not remembering the low-level details of something you haven't touched in years.
You have to use a vendoring tool like Glide[1] for now, but Go is actively testing official vendoring support with vgo[2], where you use git tags for versions.
let x = $x;
let buttons = $$('div#contents div#contents div#menu button');
let delay = 1000;
for (let i = 0; i < buttons.length; i++) {
};
...increase delay if needed.