Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror

Comment: Re:Personally, I don't think he was talking to Goo (Score 1) 344

by Shados (#49544419) Attached to: Median Age At Google Is 29, Says Age Discrimination Lawsuit

My wife interviewed for Google around that time, and pretty much all of that happened. There was a local Google office, and we know who the interviewer was, and it was a Google engineer. And pretty much everything described happened. And it was VERY common at the time (the google docs link was given on the spot, though. No video conferencing).

Interviewer who barely spoke english on speaker phone who barely seemed interested. Check!

Comment: Re:That shouldn't surprise anyone (Score 1) 344

by Shados (#49544369) Attached to: Median Age At Google Is 29, Says Age Discrimination Lawsuit

"Brushing up" is not a solution as it takes precious family time away and perpetuates the fact that IT HR keeps relying on standardized interview loops to select established and employed senior industry hires. Why can't companies offer an easy to terminate 1 months trial period contract on a well matched technical background? A match can be easily established through documentation, interviews and presentations by the candidate - and after the trial period is over the hiring team can make a decision based on a minimum of 160h of actual work done by the candidate.

I brought that up at my current employer, because we're trying to hire a lot, and no interview process will be perfect. Make it too hard, you have too many false negative (and the smarter people even just walk straight out). Make it easier so you don't miss out on geniuses who are just bad at interviewing, and you suddenly find yourself with a ton of shitty people.

So yes, the solution is to hire fast, and to lay off faster (after a trial period). Netflix supposingly does this.

The problem: First, the trial needs to be longer. In the first month, a lot of issues will simply be attributed to ramping up. Depending on the problem space, you may need 3 months, or more (I worked somewhere once where the problem space was so large and the ramp up so long, you really wouldn't know until 6+ months in. Thats rare though).

Second, most people thought it was "immoral" to hire someone and then lay them off. "People have bills!". "The interview process should just be better!". "Don't make people pay for your mistakes! If you hired them, you keep them!".

So instead, all of the people who are begging to be given a chance, are just left in the cold.

Comment: Re:That shouldn't surprise anyone (Score 1) 344

by Shados (#49544349) Attached to: Median Age At Google Is 29, Says Age Discrimination Lawsuit

The average is still in the 20s. If most of your team was in the 40s+, it is a fluke.

Google's interview process is also incredibly inconsistent. So of course, some people will have a better experience than the majority. You can brush up all you want, but there's countless algorithms, and it just takes ones.

And I'm just talking about the on-sites... the phone screens (if you're not skipping it via references)?. God forbid you're a little slow typing out a A* in fucking google doc (use coderpad or something, please?)

Comment: That shouldn't surprise anyone (Score 5, Insightful) 344

by Shados (#49541721) Attached to: Median Age At Google Is 29, Says Age Discrimination Lawsuit

Google is a discrimination factory, but in this case, there's a deeper problem, and its, what I'll call, the "MIT culture".

You have a bunch of people who busted their ass off to go through MIT/CMU/CalTech/Whatever, to learn all those algorithms, the computer science core, etc, and are thrown in the real world where, while VERY useful, are only a small subsets of things that matter.

Then you ask these people, who spent 4 (or 6, or more) years being drilled that the only shit that matters was what they learnt in school, and worked REALLY hard to absorb that, to interview.

What do you think will happen?

You end up with an interview process that, regardless of the actual work, the further away from school you are (ie: the older you are), the less likely you are to pass the interview, give or take people who worked as data or algorithm scientists in the recent past.

Net result: you have a very high percentage of college hire, and your lateral hires will always lean toward the younger side. Any skill that come with experience is almost never tested in interviews to counterbalance it.

Comment: Re:Is it the Apps? (Score 0) 138

The marketing was good. The device sucked, and beyond the touch screen and including an actually adequate browser, was barely an incremental improvement over what was out there. Yeah, Pocket PC and Windows Mobile sucked, but the iPhone only sucked marginally less (and they had apps, the iPhone didn't).

The only thing Apple did aside the incremental technical improvement, was strike a deal for unlimited internet with a major carrier (which didn't last, btw), which got attention. More importantly, they managed to make it cool and hip, instead of being a geek toy. With those 2 things, Apple could have pushed out a white Pocket PC/Windows Mobile phone exactly like the ones that existed at the time, and ended with very similar results.

Comment: What happens... (Score 1) 599

When they ace it, end up in one of the ultra competitive CS schools (or work environment) and haven't been exposed to whatever it is that causes female students to not do well right now, all in one shot? It would even out eventually, but the first few batches will be in for a rude awakening.

Comment: Re:Lowest common denominator, to be expected (Score 1) 892

Yup, so here's the dirty secret that this ends up showing, assuming something like this became a lot more common.

Lower paying companies will end up with a higher percentage of women. The men will simply hold on offers and pick between multiple ones to get the higher paying ones. So you end up with lower paying companies full of women (who just took the job) and higher paying ones mostly with men who selected on that criteria (for better or worse).

Then in the news, the higher paying companies end up being called out for being sexist and not hiring enough women, even though it was basically self selecting by the candidates themselves.

End result: everybody loses.

Comment: Re:A modest proposal for equal pay for title... (Score 1) 892

Its so much more complicated than that. Roles and skill levels vary so much, along with the market itself, that the last rate previously negotiated may just not apply at all (right now, it would almost always be below unless you're hiring someone every other day).

Comment: Re:Tabs vs Spaces (Score 1) 428

by Shados (#49426471) Attached to: Stack Overflow 2015 Developer Survey Reveals Coder Stats

Pretty much. And the issue is that tabs gone wrong is only visible once its viewed by someone with different settings, which will be uncommon in homogeneous teams ("Whats your tab setting?" "2 space width" "Ok, cool, ill use that too!")

Then people brush it off in the code review or don't notice, and 6 weeks later its a mess.

Comment: Re:SQL (Score 1) 428

by Shados (#49426461) Attached to: Stack Overflow 2015 Developer Survey Reveals Coder Stats

This can be pretty trippy lately as the various "products" are diverging quite a bit.

I hadn't used MySQL in ages, and recently moved to a company that did for their smaller transnational dbs. It messed me up big time to see queries that had stuff in the select part that were not in the group by clause or aggregates.

Then someone asked me for help with a Vertica query...and that is pretty bizzare in itself, being a vertical store with fairly high postgresql compatibility. Some stuff you expect to work just plain don't for weird reason (if you're not used to it. They all make sense once you understand the product's limitations). Other things that are completely unthinkable on a normal relational dbs however work just fine there (doing a where clause on a column ran through a function on a 500gb column, which would cause an impossibly slow full table scan in a normal relational db, run nearly instantly...)

Its a big, big world out there...

Comment: Re:Like Coca Cola, git is the real thing (Score 1) 203

by Shados (#49419765) Attached to: 10 Years of Git: An Interview With Linus Torvalds

But once you really understand how Git works, you're ruined for every other version control system. When I'm forced to use TFS for a project, I use Git locally and Git-TFS to keep them in sync. Now I commit often, all day long, tracking all my changes and (relatively) easy rolling them back or reordering them if necessary.

Yup. I can deal with any language (ok, aside PHP...), any operating system (yeah, I don't mind developing on Windows), any framework, any technology...but source control has to be on git or I'm out.

No other tool affects my workflow so deeply at this point.

"Dump the condiments. If we are to be eaten, we don't need to taste good." -- "Visionaries" cartoon

Working...