One of the most brilliant and talented women I've ever known once shared a story with me that absolutely shocked me, a story that I think should be heard.
She was hired as a software engineer at NASA, her dream job. Honestly, a dream job for many- it would have bee a dream job for me, before I moved to security. Writing software for spacecraft has to be one of the coolest and yet most demanding jobs in the industry. Yet, her joy was quickly gone, and her spirit deflated.
She was consistently assigned menial, even pointless tasks. Mere busywork at times. Work far below her ability. Work that never gave her the opportunity to show what she was capable of. It didn't take long to find out why.
You see, not long after she was hired, her manager made it clear that he saw women's place as being at home and raising kids. If he was so against women working, why did he hire her? He had a problem, his male engineers had a habit of moving out of the area for higher paying jobs in the private sector. So he started hiring single women in hopes that they'd marry his male engine
... Show more...One of the most brilliant and talented women I've ever known once shared a story with me that absolutely shocked me, a story that I think should be heard.
She was hired as a software engineer at NASA, her dream job. Honestly, a dream job for many- it would have bee a dream job for me, before I moved to security. Writing software for spacecraft has to be one of the coolest and yet most demanding jobs in the industry. Yet, her joy was quickly gone, and her spirit deflated.
She was consistently assigned menial, even pointless tasks. Mere busywork at times. Work far below her ability. Work that never gave her the opportunity to show what she was capable of. It didn't take long to find out why.
You see, not long after she was hired, her manager made it clear that he saw women's place as being at home and raising kids. If he was so against women working, why did he hire her? He had a problem, his male engineers had a habit of moving out of the area for higher paying jobs in the private sector. So he started hiring single women in hopes that they'd marry his male engineers, and keep them from moving away.
She had put in a tremendous amount of effort to establish her technical skills, her ability to solve the hardest problems, to prove herself as worthy of one of the most coveted roles in the public sector, to be able to work on cutting edge science and exploration. To her manager, none of that mattered. She was young, single, and he wanted someone that would tie his other engineers to that city. That's all she was to him.
He stated all of that plainly and clearly. He didn't care how smart she was, he didn't care how talented she was. He didn't care what she was capable of. All he wanted was for her to was to meet one of his male engineers, get married, and quit to raise kids.
I was fortunate enough to work with her and see her talent unleashed. I was lucky enough to see what she was truly capable of, and it was a lot. She would have been that manager's best engineer, if he'd given her the chance - if he'd seen her as something other than a means to tie down one of the men he'd hired.
His demeaning and sexist views robbed her of the career at NASA that she dreamed of, and robbed NASA of a brilliant engineer.
At this point, you may be asking why I'm sharing her story, a story that I don't believe was ever shared publicly, instead of her sharing it. Because of one of the other places that women have to fight to be heard: the doctor's office.
She knew something was wrong, she knew something had changed, she was dealing with symptoms of something, but had no idea what it was. Her doctor said it was a minor infection. As treatments failed, she went to a different doctor for a second opinion. Same answer. As the symptoms got worse, she went to more doctors, all said the same thing, Finally, half a dozen doctors later, she found one that was willing to perform even the most basic of medical tests.
It took only a few days to confirm the diagnosis: cancer. It would have been easily treated if diagnosed early, but had already progressed to stage 4. There was no effective treatment.
Because of a sexist manager, NASA lost a fantastic engineer, though the security community gained one of the most brilliant minds in application security that I've ever encountered. Because of doctors that don't listen to women, we all lost her.
(I won't mention her name, as she greatly appreciated privacy in life, though this story should be told and remembered. If you knew her, you're well aware of what a truly amazing person she was, not only as a remarkable talent, but a fiercely loyal friend. I was truly lucky to have her as a friend, and while she's been gone for a few years now, I still mourn losing her.)
Ed Davies
in reply to Simon Tatham • • •Hugo Mills
Unknown parent • • •@amonakov I just tried zsh and got the same behaviour.
What shell are you using, Simon?
Tony Finch
in reply to Hugo Mills • • •@darkling @amonakov set -P (physical directory paths) changes the behaviour of cd pubs.opengroup.org/onlinepubs/β¦
which might be more pertinent than the choice of shell
i put set -P in my bashrc over 25 years ago because the default βlogicalβ behaviour makes no sense
cd
pubs.opengroup.orgschiermi
in reply to Simon Tatham • • •Jyrgen N
in reply to Simon Tatham • • •Ian Jackson
in reply to Simon Tatham • • •I often use cd `pwd` which (in bash at least) is pretty close to the effect of cd $PWD, but easier to type.
This is useful with tests that blow away and recreate a temporary workspace. You run the test, and in another shell cd there and inspect its files etc. The next iteration will delete your inspection shell's cwd - but cd `pwd` puts you in the same place in the new run's output.
For this, the test case must reuse the same temp path. But you wanted to avoid /tmp, anyway.
Moritz Dietz
in reply to Simon Tatham • • •kΓ¦t
Unknown parent • • •Diego Roversi
in reply to Simon Tatham • • •That's remind me something i found amusing some times ago:
While the error in creating the file looks legit, why can I list a directory that doesn't exist? And I think that a new directory with the same name, it's still a new directory, but looks like "cd ." somehow fix the cwd of the shell.
Just for reference tests were made on linux on a ext4 filesystem (but does it matters?).
Simon Tatham
in reply to Diego Roversi • • •@diegor 'why can I list a directory that doesn't exist?' β it does exist, it just isn't linked from anywhere. On Unix, directories as well as files have the property that the inode (containing the actual contents) persists even after there's no path to it from the filesystem root, if a process has it open. So your cwd can still be in a directory that's been deleted.
'looks like "cd ." somehow fix the cwd of the shell' β assuming the shell is bash, yes, by default "cd ." will do that. It _doesn't_ do what I claimed in the head of the thread, unless you have the non-default 'set -P' option, which I set long ago for myself and had forgotten was relevant. If _I_ had done "cd ." in that situation, I'd have stayed in the deleted directory.