Every tested testi. Testis of non-testee testi'd are not tested.
Okay, Yahoo and AskJeeves didn't have anything useful. Let's try this Google thing.
Slip them your number on a note on top of cash for your purchase?
This. I used to also keep a notebook with me and jot down the commands I used often. Eventually I learned other ways to jolt my memory and learned to use man. As time went by I used my notebook less and less.
We have strict data sovereignty requirements, so we do a lot of self hosting. We are also a kubernetes shop, so we've been using the Argo-CD / Argo Workflows combo. I quite like it, there's a lot of freedom to spin up a container and do anything you want in it while passing results to the next step, it might be too much freedom for some folks though. CD systems have some variety to them since there's so many ways to deploy code, but CI systems all feel pretty similar to me. The main differences are the format of the instructions you write for the system, and how much or how little it holds your hand.
It's a little hard to iterate and think when you're adding to a complicated codebase you might not have worked with in several months, or even just a portion of a project that's seemed stable for a long time. In that scenario, debuggers are able to shorten the getting up to speed process by quite a bit.
Yeah it's not too rare to store passwords in config files (e.g ~/.config/appname/config.json) usually at least base64 encoded to support special characters. It is usually better to try and store a token instead as they can be revoked or expired. If you have to store a password it might be fun to look into storing it in the system keychain, at least for macos or Linux, not sure if Windows has a keychain.