A funny little thing happened. A few days ago, I woke up after dreaming about a problem in our SSH Client. The dream called my attention to an issue I had never really thought about, or considered a problem. In currently released versions, when the client is run for the first time by the installer, it starts elevated - it runs with full administrative permissions of the installer, which means it runs in a slightly different security context than every next time it is run. I dreamt that this is causing problems, but after I woke up and thought about it, I couldn't quite put my finger on what these problems are. I wasn't even sure that it runs elevated in the first place. So at first, I didn't want to make a big deal about it. It seemed like a theoretical issue more than one with immediate impact, and we have other issues to deal with.
Still - later that day, before I went to bed, I remembered the dream again, and gave it the benefit of the doubt. Maybe I couldn't think of how it causes problems, but the behavior is incorrect. I opened a case about it, and Andrej fixed it soon after that. The fix isn't yet available in a released version, but it will be.
A few days later, we receive a follow up from a customer who had reported strange behavior with the SSH Client. He previously found that some of his network drives aren't visible from the SSH client, but now he found that the problem occurs when he uses the client after installation. The drives become visible if he closes the client and opens it from the shortcut again. I get a hunch, and ask the customer to try running the client from the shortcut, as Administrator, using elevation, and see if that reproduces the problem. Sure enough, it does.
So I dreamt about a problem that I didn't understand, and we fixed it a few days before recognizing an example of its impact. Cool. :)