Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror

Comment I've had issues with the Win10 NVIDIA drivers... (Score 3, Insightful) 316 316

Usually the problem is something like, "it isn't giving me the newest driver" or simply the poor quality of the drivers in the first place. (For awhile there, if I clicked on the start button, it would cause my screen to reset!) And a lot of "your driver stopped responding so we turned it off, then back on again."

In some ways, I like that the drivers are being pushed to me automatically, but at the same time, if I'm doing multiple reinstalls in a single day, I've already downloaded the drivers... I don't need them to be downloaded YET AGAIN, every install...

Comment Depends who you ask... (Score 4, Interesting) 217 217

At Facebook, it's memcached, with an HDD backup, eventually put onto tape...

At Google, it's a ramdisk, backed up to SSD/HDD, eventually put onto tape...

For anyone who can't afford half a petabyte of RAM with the commensurate number of computers? I have no good ideas... except maybe RAM cache of SSD, cache of HDD, backed up on tape...

Using something like HDFS to store your data in a Hadoop cluster of file requests, is likely the best F/OSS solution you're going to get for that...

Comment Re:Does indeed happen. (Score 1) 634 634

Yeah, I don't normally get feed back either. But it is kind of suspicious when I do get feedback...

I think it's a lot related to the xkcd comic: https://xkcd.com/385/

If I spend a bunch of time rewriting code (which everyone does), as a man they might think "oh, well, he's just refactoring, or having a bad day." But when I do it, they think "wow, women can't code..." and then reject me out of hand without attempting to rationalize an explanation for why it should be overlooked...

Not that I'm particularly complaining here... this is just life as a woman in the tech industry... that and "oh wow, what does your boyfriend do at Google?" Actually, he's a literature teacher, I'm the genius programmer troubleshooter who knows almost everything about computers...

Comment Re:Not acupuncture (Score 2) 159 159

Sticking needles in people at random locations around the body does not...

Actually, that's precisely the problem with acupuncture working better than placebo. Acupuncture works whether you're following their "rules" or just randomly sticking needles into people...

Basically, it turns out, that forcing a person to lay still for a long time has the same benefits of destressing as just laying on a sofa and chilling... or a massage, or any other relaxing activity...

Comment Re:Does indeed happen. (Score 1) 634 634

We don't really know what the facts of the case are, but I wonder what it is about people that lead them to believe they're being discriminated against based on a particular factor, like age, race, etc?

Because I've worked for Microsoft, Amazon (as consultant, i.e. well-paid "contractor) and Google, and I have been recognized by SourceForge in a Project of the Month.

And then they return answers like "we want someone with more experience programming". To which my 7 year friend at Google laughed and said, "are they looking for someone who's on the verge of retiring?!"

Seriously, when the answer they tell you doesn't make sense... it doesn't make sense.

Comment Re:Commission (Score 2) 634 634

Google intentionally recruits people multiple times. They understand sometimes a person has a bad day, and that they grow and develop. Unless you don't utterly fail the phone screen, you're very likely to get called in a few times, just to make sure that they're not turning you down for arbitrary decisions. (Chances are good that an arbitrary situation won't show up 4 times in a hiring committee")

Which brings me to the second point. It's highly unlikely these people will win, as Google hires by committee... so everything gets documented and recorded. There is no ability for a single bias person to interfere with a hiring decision.

N.B.: I worked a Google, I was "undecided" by my first hiring committee, but the second made an offer like immediately after being presented my packet.

Comment Re:No software solution? (Score 2) 634 634

Google actually INTENTIONALLY recruits people multiple times. Unlike many other companies, they realise that people grow, people develop, and sometimes people are just having a bad day.

In any case, they want to ensure that they haven't passed up any arbitrary candidate just because they failed one in-person interview.

N.B.: I worked for Google. I didn't get hired by the first committee, but was hired by the second committee...

Comment Re:Um, because this is a computer doing the work (Score 1) 167 167

Anyway, even if they automate some parts of your job, the part of your job that isn't automated will expand to fill that time.

Indeed, compilers already automate so much of our programming job. I remember having to avoid using multiplication by a constant if speed was important, and choosing all sorts of crazy things, just because they ran faster... now, the compiler automates this for me, and I can write code that is more legible and clear.

This is just yet, another form of optimization, which computers have been doing for us for like at least 10 years already...

Comment Re:Well... (Score 1) 377 377

I probably went "scp -r directory new_server:direcory/"

Yeah, the devs had full run of that place. In fact, a LOT of people at that place had root access. To the point where I would go around the place when I'd stay late and pull the damn post-its with the root password off peoples' cube walls.

And yeah, I remember it. Because, first, it WAS a defining moment. And second, I kinda remember a LOT of stuff.

Comment Re:Well... (Score 1) 377 377

> I'm gonna have to go against the chorus and lay the blame at your feet, honestly.

That pretty much HAS been the chorus.

And I never said I wasn't (at least) partially to blame - I definitely had a blind-spot.

Also, had a new sysadmin been hired, he'd have no reason to turn the old machine on. Other people WERE aware of what was going on, including the people who would've trained a new guy. What's more, that machine was leased and would have been returned within a week or two, so he couldn't have repurposed it. And he couldn't have pulled any storage from it because that was part of the lease. And even if he could, it was a Sun box and the new one was an AIX box, so stuff wouldn't just run.

And here's another thing... say the new guy gets hired, never touches that machine because he's been told it's being returned in a few days. And then one of the devs turns it on and a week's work gets erased. They would've still blamed the new sysadmin even though he had nothing to do with it.

If you want funny, I actually knew the guy who ended up replacing me through a local Linux user's group. I know he was plagued by the same kind of crap. He tried to update the remote connections to use ssh rather than telnet and almost got fired for THAT.

This was not a good SysAdmin environment.

Congratulations! You are the one-millionth user to log into our system. If there's anything special we can do for you, anything at all, don't hesitate to ask!

Working...