Oh yeah, mine was only the straightforward math part, I didn't even look at the circuit itself; I kept it as simple as possible, and just wanted to show that the given equations do have a single real solution.
When I work on a problem, I create a directory for it, and put the "story" part in a README.txt file.
That is because I don't want to have to open wxMaxima to see it; I'm very, very lazy. (And "paranoid", I don't like being beholden to any single application; I much prefer copy-pasting the code, than using Maxima/Maple workbooks for long-term storage.)
Even my scripts and example programs show "usage" (summary of the "story") when run without parameters, or with -h or --help. That way I only need to run the likeliest executable in the problem/solution directory, to see what it is about. I have a few hundred of these, and if they're on the same machine (I recently archived most of them), I can find a specific one based on a vague memory in seconds.
The story, the context and background for the math, is invaluable in the long term. It takes only a few minutes to write down the context with the solution method. Even if you never end up needing the solution again, writing it up in a concise way (but descriptively enough so you'll re-understand it even after a long interval), also helps most people to better understand the problem at hand. It is not rare to realize the answer when one constructs an efficient way to ask the question.
When I have a complete solution on a math problem, I usually write it up in LibreOffice Writer, and save both that and a PDF "print" version (that I'll consult when necessary). I really should move to LaTeX, though.