1. No, but I had a significant part in getting Hubble up there. I wasn't shocked by the eye problems.
I wrote the requirements database for the Hubble. I didn't underSTAND the requirements, but that wasn't my job. I just had to provide the engine to track them. As fucked up as NASA was back then, I was shocked that it actually made it into the air, and not at all shocked that it had vision problems.
My boss then told me to create another database to track the requirements. I asked for specs and he said, "Just make it look like the other one." There was absolutely no connection in requirements here, but that was also shortly before I quit because I was working for morons.
I made a self-modifying database menu structure that could be filled in with routines as they became necessary. The Lockheed guys loved the base software. It fit their needs.
I called it the "Test Interface Tracking System" and used that title exclusively in all of my screens and documentation. As with everything DOD/Government, eventually all such terms end up as acronyms (I planned this). Two months later, I left for another job. Two months after I left, my boss burst into the office of one of my coworkers and yelled, "THAT SON OF A BITCH!" - four months later than I introduced the term. I feel sorry for the underling who had to inform him that she couldn't replace the well-publicized title with "TITS". I won.