The "/" was used in MS-DOS command lines to identify a "switch" (UNIX calls 'em "options" and uses a dash character). MS had a bunch of DEC & DG type coders there back when DOS was developed, and that's how they did it at DEC. Using the "\" as a pathname separator was a huge mistake because UNIX used "/" and all it did was to confuse a whole generation of college kids who grew up on UNIX.
"I'm wondering if others have experienced similar problems . .."
By "similar problems," I take it you mean, at least in part, pointless interviews conducted by H.R. weenies who don't know a USB port from a glass transistor?
They're robotic wind-ups, much the same as the typical third-world first-level "support" tech (you know--start with "A"--> If answer is "X" go to "B" else go to "C" unless "Y" is present). Same brain cells, different script.
You're after the hiring manager, not some dweeb with a B-school degree, so keep your eye on the ball. The trick is to get by the gatekeeper, so you sometimes gotta . . . lie a little.
You may find it's easier to leave the tech support stuff off the resume and just lean on the recent-grad-Comp Sci thing. You're also up against a shelf life problem in that if it takes too long to connect, you're no longer "recent." Now you know how people end up in grad school and even PhD's by the age of 27.
Never underestimate the value of a solid list of personal references. Any good or cool projects you did for anyone are worth mentioning.
The help-desk thing was just to pay the light bill, right? Forty years ago, some of us drove trucks or dug ditches or went military long enough to soak up whatever they were passing out. The military experience on my resume in the 1970s was there solely to show where I went to school, and fell off after 10 years. A college degree is good on a resume forever.
You busted your hump and did it the hard way. Why dilute that effort by mentioning what you did to pay the rent? Just a thought.
It's not going to make you feel any better, but things are a lot tougher now than in my day (1960s-1990s mini/micro computers). Sure, troubleshooting discreet circuits from a schematic and looking at an O'scope and little blinking lights was an entry level skill, but electronics isn't exactly a black art. The math is mostly high-school, and anything else you need to know you could dig out of a book. The coding was assembler, and you didn't have to deal with any really huge bunches of code.
About all I can do is wish you luck--It's a shame to see someone work so hard to get the paper only to be blown off by interviewers who obviously don't get it.
From a scientific point of view, I find this exciting and potentially beneficial to the race as a whole. As a US citizen, I find it scary. I have come to distrust anything where the decision regarding personal rights is left up to any government. A question we ask each other a lot is, "Should we do something just because we can?" My answer has always been "It depends . . . "
I have a personal interest in this and related subjects. My mother is 94, in good general health but shows signs of dementia. Her family is generally long-lived--several have made it to 100 in my lifetime--but the last decade or so isn't pretty. Am I looking at my own future, I wonder? I am 60 and feel fine, aside from a bit of joint pain that abates quickly once I start moving around. My doctors tell me I'm a "young guy." All my blood work and stress tests come back clean. Do the same genes that keep me healthy also doom me to losing my mind in 20 or 30 years? I wish I knew.
Slashdot Mirror
The "/" was used in MS-DOS command lines to identify a "switch" (UNIX calls 'em "options" and uses a dash character). MS had a bunch of DEC & DG type coders there back when DOS was developed, and that's how they did it at DEC. Using the "\" as a pathname separator was a huge mistake because UNIX used "/" and all it did was to confuse a whole generation of college kids who grew up on UNIX.
"I'm wondering if others have experienced similar problems . . ."
By "similar problems," I take it you mean, at least in part, pointless interviews conducted by H.R. weenies who don't know a USB port from a glass transistor?
They're robotic wind-ups, much the same as the typical third-world first-level "support" tech (you know--start with "A"--> If answer is "X" go to "B" else go to "C" unless "Y" is present). Same brain cells, different script.
You're after the hiring manager, not some dweeb with a B-school degree, so keep your eye on the ball. The trick is to get by the gatekeeper, so you sometimes gotta . . . lie a little.
You may find it's easier to leave the tech support stuff off the resume and just lean on the recent-grad-Comp Sci thing. You're also up against a shelf life problem in that if it takes too long to connect, you're no longer "recent." Now you know how people end up in grad school and even PhD's by the age of 27.
Never underestimate the value of a solid list of personal references. Any good or cool projects you did for anyone are worth mentioning.
The help-desk thing was just to pay the light bill, right? Forty years ago, some of us drove trucks or dug ditches or went military long enough to soak up whatever they were passing out. The military experience on my resume in the 1970s was there solely to show where I went to school, and fell off after 10 years. A college degree is good on a resume forever.
You busted your hump and did it the hard way. Why dilute that effort by mentioning what you did to pay the rent? Just a thought.
It's not going to make you feel any better, but things are a lot tougher now than in my day (1960s-1990s mini/micro computers). Sure, troubleshooting discreet circuits from a schematic and looking at an O'scope and little blinking lights was an entry level skill, but electronics isn't exactly a black art. The math is mostly high-school, and anything else you need to know you could dig out of a book. The coding was assembler, and you didn't have to deal with any really huge bunches of code.
About all I can do is wish you luck--It's a shame to see someone work so hard to get the paper only to be blown off by interviewers who obviously don't get it.
From a scientific point of view, I find this exciting and potentially beneficial to the race as a whole. As a US citizen, I find it scary. I have come to distrust anything where the decision regarding personal rights is left up to any government. A question we ask each other a lot is, "Should we do something just because we can?" My answer has always been "It depends . . . " I have a personal interest in this and related subjects. My mother is 94, in good general health but shows signs of dementia. Her family is generally long-lived--several have made it to 100 in my lifetime--but the last decade or so isn't pretty. Am I looking at my own future, I wonder? I am 60 and feel fine, aside from a bit of joint pain that abates quickly once I start moving around. My doctors tell me I'm a "young guy." All my blood work and stress tests come back clean. Do the same genes that keep me healthy also doom me to losing my mind in 20 or 30 years? I wish I knew.