Meanwhile in Europe work that was outsourced to Indian companies is being replaced by Eastern European outsourcing companies: sometimes cheaper with far better quality.
Which is about how long it would take to download everything offshore.
Electrician HAVE to actually be on site (until they design a robot that someone can telework with that is). To an overwhelming degree, IT does not. This is the difference, and why unionization of IT is a nonstarter.
Because every company has its own processes, production and test harnessed, release procedures...
You DO realize that for every line of code that goes into a software product there are several lines in testing, staging, release, and so on that the public never sees? (The ratio might no be accurate in all cases but you see my point I hope.)
"team building" -- silly meetings that are a waste of time but better then traditional meetings "Agile development" - every day a little meeting where you say what you did yesterday, and a couple of meetings every pay cycle where you plan what you are going to do that pay cycle "Synergy" - tell someone their idea is great, nothing will come of it anyway "open office" - sit where you want "ping pong" - pass, when someone starts playing there will be a complaint about the noise "free cokes" - what a horrible burden for you
Not my impression at all. The recruiter flat out told me that their hiring process was very much in favor of recent grads for one reason only: much of the material that pops up in many of the interviews is covered in an academic setting and theif you graduated long ago you had probably forgotten a lot of it.
Google was interested in me be extremely proficient in C, Java, or C++. At least for this position they didn't care about anything else. Flat out did not care.
Aside from that, it was algorithmic and data structure type questions. Sorting questions, stuff like that.
My screw up was that after 20 or so years I had forgotten the difference between theta and omega notation when analyzing the growth rate of my sort routine - I switched them. That did me in. Oh well.
It works well for us simply because we hire people who respect this freedom: we have core hours in which you are expected to respond to email, slack, phone calls. Missing meetings is not an option - you will attend over GTM. People are pretty professional. No gossiping or stuff like that.
We realistically scope our work - an Agile shop, our two week sprints are rarely ever slipped, our stories are are rarely ever 5 points (Fibonacci). We usually make the goals that management and engineering agree to. While of course they ALWAYS want more, they have tasted the sweetness of perfectly predictable product release dates... and they like it.
We also fire. Quickly. Not only is it a reminder to all that slackerdom is not tolerated... just one lazy apple can bring the whole thing down. So we end up working *very* solid 8 hour days. Rarely have to work overtime. It usually ends up feeling like a low grade constant crunch time, but is not so bad.
Slashdot Mirror
It's broke.
Much like the US finally switching over to metric - it makes too much sense and thus will never happen. Only in this case the insanity is global.
Tell that to Trump's wife.
To be fair, they didn't steal the job - it was given away by greedy American management.
Meanwhile in Europe work that was outsourced to Indian companies is being replaced by Eastern European outsourcing companies: sometimes cheaper with far better quality.
It really boils down to cost. That is it.
Virtually every sector is pays better, not just in the US but in the First World in general.
It is far more expensive to live here, reason number 1.
>> all of it will be fixed almost overnight
Which is about how long it would take to download everything offshore.
Electrician HAVE to actually be on site (until they design a robot that someone can telework with that is). To an overwhelming degree, IT does not. This is the difference, and why unionization of IT is a nonstarter.
Because every company has its own processes, production and test harnessed, release procedures...
You DO realize that for every line of code that goes into a software product there are several lines in testing, staging, release, and so on that the public never sees? (The ratio might no be accurate in all cases but you see my point I hope.)
I almost certainly would do this.... however I have money saved and a contingency plan, not to mention an employed spouse.
However I might just hang around and be useless, not to mention train my replacements with some anti-patterns and forget some lessons learned.
>> "... MBA from the Wharton School." Not a background of someone who understands computer technology.
HCSC is not a computer/technology company.
They'd throw all that shit in the dumpster if they could. To them, technology is simply an afterthought.
Well, if we are talking H-1B abuse, consider Trump's WIFE came in on an H-1B.
This, like every other "I was an intern who saved the world" story, has more than meets the eye.
Like, why didn't they simply revert to the previous stable build?
Don't forget dressing in a skimpy outfit.
Now you've done it - mentioned a personal accomplishment on /. which will then be denigrated by those who haven't so much as attempted such a thing.
"team building" -- silly meetings that are a waste of time but better then traditional meetings
"Agile development" - every day a little meeting where you say what you did yesterday, and a couple of meetings every pay cycle where you plan what you are going to do that pay cycle
"Synergy" - tell someone their idea is great, nothing will come of it anyway
"open office" - sit where you want
"ping pong" - pass, when someone starts playing there will be a complaint about the noise
"free cokes" - what a horrible burden for you
>> I'll give you feedback on how reasonable your desires are.
Lesson one: the customer is always right.
To be fair, those are your words not the poster's.
However in the US, that's what "minority" usually means. Unless the person saying it is black, in which case it means black.
The fact that you didn't include transgender programmers makes your post sexist.
Perhaps one of the most accurate visions of the future ever put onto the big screen.
Just experience the performance. That is the reason you are there, not to make a crappy recording of it.
They should be the center piece for any device lover.
Not my impression at all. The recruiter flat out told me that their hiring process was very much in favor of recent grads for one reason only: much of the material that pops up in many of the interviews is covered in an academic setting and theif you graduated long ago you had probably forgotten a lot of it.
Google was interested in me be extremely proficient in C, Java, or C++. At least for this position they didn't care about anything else. Flat out did not care.
Aside from that, it was algorithmic and data structure type questions. Sorting questions, stuff like that.
My screw up was that after 20 or so years I had forgotten the difference between theta and omega notation when analyzing the growth rate of my sort routine - I switched them. That did me in. Oh well.
I live 15 minutes away and rarely come in.
It works well for us simply because we hire people who respect this freedom: we have core hours in which you are expected to respond to email, slack, phone calls. Missing meetings is not an option - you will attend over GTM. People are pretty professional. No gossiping or stuff like that.
We realistically scope our work - an Agile shop, our two week sprints are rarely ever slipped, our stories are are rarely ever 5 points (Fibonacci). We usually make the goals that management and engineering agree to. While of course they ALWAYS want more, they have tasted the sweetness of perfectly predictable product release dates... and they like it.
We also fire. Quickly. Not only is it a reminder to all that slackerdom is not tolerated... just one lazy apple can bring the whole thing down. So we end up working *very* solid 8 hour days. Rarely have to work overtime. It usually ends up feeling like a low grade constant crunch time, but is not so bad.
For no other reason than I flubbed an easy problem during the interview.
Not sure that Brain Fart is grounds for a lawsuit.
Managing a 200 person team is a fucking nightmare.