Slashdot Mirror


If the Programmer Won't Go To Silicon Valley, Should SV Go To the Programmer?

theodp writes: "If 95% of great programmers aren't in the U.S.," Matt Mullenweg advises in How Paul Graham Is Wrong (a rejoinder to Graham's Let the Other 95% of Great Programmers In), "and an even higher percentage not in the Bay Area, set up your company to take advantage of that fact as a strength, not a weakness. Use WordPress and P2, use Slack, use G+ Hangouts, use Skype, use any of the amazing technology that allows us to collaborate as effectively online as previous generations of company did offline. Let people live someplace remarkable instead of paying $2,800 a month for a mediocre one bedroom rental in San Francisco. Or don't, and let companies like Automattic and Github hire the best and brightest and let them live and work wherever they like." Microsoft and Google — which hawk the very tools to facilitate remote work that Mullenweg cites — have shuttered remote offices filled with top talent even as they cry the talent sky is falling. So, is "being stubborn on keeping a company culture that requires people to be physically co-located," as Mullenweg puts it, a big part of tech's 'talent shortage' problem?" Chris Pepper also recently posted another reasoned rebuttal to Graham's post.

176 of 294 comments (clear)

  1. Exactly this. by fyngyrz · · Score: 5, Interesting

    Also, stop being anal about degrees, credit scores, old convictions, age, and health.

    There's no programmer shortage. That's utter BS.

    There's just a hiring pathology.

    --
    I've fallen off your lawn, and I can't get up.
    1. Re: Exactly this. by Anonymous Coward · · Score: 5, Interesting

      If these companies were hiring a cook they would require 3 years experience working on an Ace cooktop, 5-years experience with Acme Food Supply, and be able to demonstrate the restaurant's recipe for their signature meat dish before being considered.

      Companies didn't come into existence with their particular toolsets: they learned them, and quickly. Then they refuse to consider hiring anyone who doesn't already know them in depth.

    2. Re:Exactly this. by beelsebob · · Score: 1

      No, definitely not exactly this. Remote working really doesn't work well. Especially remote working across 8 time zones (i.e. you only actually get to chat to each other for 1-2 hours a day)

    3. Re: Exactly this. by westlake · · Score: 1

      If these companies were hiring a cook they would require 3 years experience working on an Ace cooktop...

      Worst analogy ever.

      When the culinary staff screws up, they can set fire to the kitchens or put employees in the hospital. Experience and credentials matter here.

    4. Re: Exactly this. by Fwipp · · Score: 1

      And yet, we trust that the chefs will be able to learn a new stove.

    5. Re:Exactly this. by AK+Marc · · Score: 4, Insightful

      There is a shortage of programmers in the US. There aren't enough of them, in my locality, that will work for what I'm willing to pay. That's a national emergency.

    6. Re:Exactly this. by Kohath · · Score: 1

      All of these things have pluses and minuses. Rather than picking a side and defending it, companies should regularly weigh the benefits versus the costs of these choices and watch for opportunities that might tip the scales away from the current policy.

    7. Re:Exactly this. by cshotton · · Score: 2

      To put a finer point on it, Graham is willfully blind to the simple fact that H-1B engineering talent is viewed as a pure commodity to be consumed, discarded, and replaced by investors. VC-backed management teams are actively encouraged to keep wage pressures down by acquiring good talent at rates that are far below what they'd be if they weren't kept artificially depressed by the pool of non-US workers. The real truth is that "great" programmers are not scattered randomly throughout the human population. They are created by an intersection of opportunity, need, education, and immersion in a technology-focused culture. The great programmers are here. VCs like Graham just don't want to pay for them and fabricate disingenuous math problems to justify not paying them what the market should afford.

      Bottom line is that domestically created programmers should be vigorously opposed to what Graham proposes. Their very livelihoods depend on it.

      --

      Shut up and eat your vegetables!!!
    8. Re:Exactly this. by bondsbw · · Score: 1

      you only actually get to chat to each other for 1-2 hours a day

      You act as if this is a bad thing.

      Remote working really doesn't work well.

      Actually it can, assuming everyone doesn't need hours of direct supervision. Of course, I don't really want to work with many of those types anyway.

      I telework and everyone else is an hour ahead of me. It works out fine. One of the reasons is because my bosses aren't douchebags and they allow for flex scheduling. And they don't schedule too many meetings, meaning I actually have time to work on the things that they pay me to do.

      Especially remote working across 8 time zones

      Of course 8 time zones can be problematic, but probably not any more so than if everyone was in 2 time zones 8 hours apart.

      --
      All my liberal friends think I'm a conservative, all my conservative friends think I'm a liberal.
    9. Re:Exactly this. by __aaclcg7560 · · Score: 1

      Also in practice, the less-than-1% of the US in Alaska/HI can be ignored,

      For my current job I do remote work for users in Alaska, Hawaii AND Manila from Silicon Valley. Manila is the most vexing because the Internet link is slower than a 56K modem, but most users are logged off their systems for the night and I can take the extra time to get the work done.

    10. Re: Exactly this. by Stewie241 · · Score: 4, Informative

      I assume he wasn't being us specific as the article sure wasn't. I work on a remote team that spanned, at one point six timezones - a guy in Australia, a team in China, a team in SV and a few others scattered among the other three north american timezones. It certainly had its challenges.

      I think it is especially difficult for a preexisting company to start thinking remote, and that is probably the real problem. The org is very head office centric and so many meetings start in a room and remote people get added in either part way through or after the pleasantries have taken place. They don't think to introduce people in the room so on the remote end all you hear is voices going back and forth at varying volumes depending on how far away the person is from the mic. If a couple of people in the room start having a person to person chat amongst themselves (not private but where the in room attendees are spectators and can listen in) then you are almost guaranteed to be SOL because they end up speaking quickly and don't enunciate as much and they don't speak as loud. If you are in the room you can jump in if you have something to add (probably using body language to indicate you want to add something) but you're lost very quickly if you are in the phone.

    11. Re:Exactly this. by Shados · · Score: 1

      I'm pretty sure they were given an example of an international company...

    12. Re:Exactly this. by ranton · · Score: 2

      8 time zones? Counting only US states (not Guam and such) there are only 6 time zones.

      Last time I checked, there are places in this world which are outside of the US. They even have humans living there, and some of them have electricity and computers.

      Plenty of people work with coworkers who live 8-12 time zones away.

      --
      -- All that is necessary for the triumph of evil is that good men do nothing. -- Edmund Burke
    13. Re: Exactly this. by Shados · · Score: 5, Insightful

      Because it doesn't take very long, and the chef is likely to still be working there in 2 years.

      In software engineering, the average time you can reasonably expect someone to stay working for you, regardless of salary or conditions/perks, is about 2~ years. Much less in startup hotbeds like SF.

      Now, let say you have some reasonably complex stuff, not too crazy, but not trivial either...maybe you use slightly less common languages (let say Scala over Java...not obscure, but not everyone learns Scala in school), and it takes 4 months for someone to be able to be left alone and do their thing (I'm making numbers up) They still won't be amazingly familiar with your particular business/domain and the ins and outs for a year, and because humans generally always improve with time, they'll be at their peek at the end of the 2 year.

      If you hire someone who already knows your technologies, you might be able to reduce that 4 months to 2 months instead. That's 2 more months of peek productivity at the tail end when your engineer is at their best. That could translate in hundreds of thousands, of even millions of dollars depending on the size of your business.

      And that is why everyone's hunting down pre-trained people. Of course, then you have to weight that with the cost of not hiring anyone at all, and decide whats best.

    14. Re:Exactly this. by GNious · · Score: 2

      Reading The Fine Excerpt, it even seems 95% of relevant workers live outside of the US

    15. Re:Exactly this. by rainmaestro · · Score: 3

      Impressive. I know we have a tradition of not reading the article before commenting, but you didn't even read the first sentence of the summary:
      "If 95% of great programmers aren't in the U.S. [...]"

      The whole point is how to get the best talent regardless of where they live. The number of time zones in the mainland US is irrelevant.

      FYI, I'm currently working on a project with two other teams: one on the west coast and one in London. They are 8 time zones apart.....

    16. Re: Exactly this. by Hognoxious · · Score: 1

      because humans generally always improve with time, they'll be at their peek at the end of the 2 year.

      Not wishing to poke fun, but do you have any references for that? I'm not sure what you're trying to address.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    17. Re:Exactly this. by sjames · · Score: 1

      On the other hand, if you want him to work on the AI for the next version of Grand Theft Auto, why do you care what his credit score is?

      Are you sure that 20 year old conviction for grand theft auto isn't in the plus column?

      Why insist on a 20-something for that SCADA system? He'll have job hopped to the competition long before that 50 year old candidate is ready to retire.

      And the guy who wrote the code for a CT machine? Do you really think his lack of 5+ years experience with (obscure java library) means he can't write safe database code?

    18. Re: Exactly this. by Shados · · Score: 1

      hmm? maybe I worded it wrong? All I mean is that if you assume people are always getting better at things they do 40 hours a week, the day they decide to leave your company, is always the day they're the best at what they do (within the context of their employment for you).

      I didn't mean people peek after 2 years specifically.

    19. Re:Exactly this. by Hognoxious · · Score: 1

      I'd take him over someone who can barely string a correct sentence together.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    20. Re:Exactly this. by Anonymous Coward · · Score: 2, Informative

      If Graham really wants the exceptional programmers, you don't bring then over on the H-1B, you use use the O visa and there is no quota for that program. Of course, that is not want he wants. The fact of the matter is there are not that many exceptional people in the world. The ones that have been identified and convinced to come over to the United States, have done so.

      The H-1B was created as a stop gap measure, to fill actual shortages for 3-6 years while America trains its residents to meet its own needs. This is why this visa does not confer residency on its recipients. They were to come over, work the gap, and go home when they were no longer needed.

    21. Re:Exactly this. by Hognoxious · · Score: 1

      8 time zones? Counting only US states there are only 6 time zones

      Asshole, let me introduce the other 18. World, meet asshole.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    22. Re:Exactly this. by Jane+Q.+Public · · Score: 2

      No, definitely not exactly this. Remote working really doesn't work well. Especially remote working across 8 time zones (i.e. you only actually get to chat to each other for 1-2 hours a day)

      Remote work CAN work great, if you're doing it right.

      I've worked with people who did it right. Everybody had a grand time and produced a great product.

      When it doesn't work well, it can be awful. But don't blame the process, blame the people who don't implement it well.

    23. Re:Exactly this. by Jane+Q.+Public · · Score: 1

      I have also worked at times for firms in Hawaii (meaning their timezone could NOT be ignored).

      I have also worked in situations in which various workers were 12 hours apart. It can work.

    24. Re:Exactly this. by Earthquake+Retrofit · · Score: 1

      Why would anyone in their right mind go into STEM when an MBA gets you twice the money for less work?

      Why would anyone marry a poor man when a wealthy one is worth more money?

      --
      Fifty years of Yippie! 1968-2018
    25. Re:Exactly this. by lister+king+of+smeg · · Score: 1

      Remote work is great for competent people. That last part is what's missing.

      Why would anyone in their right mind go into STEM when an MBA gets you twice the money for less work?

      Because they would rather not sell their soul and work in HR and don't want to have the prerequisite lobotomy for management and sales requires you to be a reptilian?

      --
      ---Saying gnome 3 is better than windows 8 not so much a compliment as it is damning with light praise.
    26. Re: Exactly this. by Provocateur · · Score: 1

      it's peak as in 'top of a mountain'. Point taken, nonetheless

      --
      WARNING: Smartphones have side effects--most of them undocumented.
    27. Re:Exactly this. by AK+Marc · · Score: 1

      Yeah, between the people talking about getting more US workers working on SV projects, and this guy talking about 8 zones (not 12 or 24), I had in my mind that he was referencing the US, not that SV would only deal with places 4 hours ahead, and 4 hours behind.

    28. Re: Exactly this. by ATMAvatar · · Score: 5, Insightful

      Because it doesn't take very long, and the chef is likely to still be working there in 2 years.

      In software engineering, the average time you can reasonably expect someone to stay working for you, regardless of salary or conditions/perks, is about 2~ years. Much less in startup hotbeds like SF.

      ...

      And that is why everyone's hunting down pre-trained people. Of course, then you have to weight that with the cost of not hiring anyone at all, and decide whats best.

      That's largely of the tech industry's own doing.

      It is well-known amongst programmers (and anyone else who cares) that the only way to be paid the prevailing wage is to job hop. Employers refuse to give regular raises to keep their coders in step with market salaries. Furthermore, employers do not invest in their employees - training must be done on a person's own dime and their own time. In a worst case, the tools and technologies used in a workplace will stagnate, causing people to leave just so they're not left behind in the industry as a whole.

      This would quickly change if the tech industry executives put more effort into retaining good people and less time into screwing them.

      --
      "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety."
    29. Re:Exactly this. by jmcvetta · · Score: 1

      I worked on a project for several years where the team was split between Boston, Sydney, and San Francisco. It actually wasn't all that hard for us to communicate and keep in sync. It probably helped that the SF and Sydney folks were on flexible schedule, while only the Boston team were cubicle slaves chained to their desks 9-6.

      FWIW, scheduling wasn't really any harder with SYD included than it was for just SFO and BOS.

    30. Re:Exactly this. by MillionthMonkey · · Score: 1

      Time zones aren't even the major issue. I had a job where I had to be on site during the AM hours and telecommute during the PM hours (long story). It was MUCH more difficult to get anything done at home. When you can't shout minor little questions out to anyone who might be in earshot, you have to communicate them electronically, which is more awkward and time-consuming, so you naturally try to figure stuff out for yourself first before bothering people that way. Some of the ordinary snags and obstacles you encounter during a workday will then balloon into frustrating barriers that trick you into wasting hours going down blind alleys without realizing it. It made me realize how much information you get just from overhearing casual chats around coffee machines.

    31. Re:Exactly this. by jmcvetta · · Score: 1

      Yup. I made the mistake of getting into software development, because it a) was accessible to a liberal arts drop out and b) it seemed to pay well (for a kid just out of college in the early 2000s). Now I realize that a not-very-successful real estate agent makes double a successful programmer's salary, while doing way less miserable work. Time for career change.

    32. Re: Exactly this. by melchoir55 · · Score: 5, Insightful

      This is the point of view of PHBs who don't understand human behavior at even basic levels. Humans have things like trust, loyalty, nesting instincts, and all the other things that make staying at a company for many years a reasonable expectation. There are software development shops *in the bay area* which have low turnover rates for their staff. Of course, in order to take advantage of those characteristics, you need to the prime them.

      You cannot treat people like cogs in a machine and expect them to treat your organization like anything but a machine to draw resources out of until they can find something better. There is a prevailing attitude among people who run software shops that their people are there to be abused and taken advantage of as much as possible. I left one of those organizations early in my career for something much better, and the difference in my own sustained productivity levels really astonished me. I didn't realize how hard I was dragging my feet out of spite, apathy, and god knows what other negative emotions fostered by maximizing the alienation of your workforce.

      PHBs think they're killin' it when they hire someone they know is worth 90k and pay them 60k. In fact, that person is probably hanging out until they can find a better job, and because they know they are doing that, they are contributing at the bare minimum level they think is necessary. Since it is impossible to quantify the productivity of an engineer (no matter how much you try to micromanage), this is NEVER a win for the company. And, no, seeing them in their chair for 50 hours a week doesn't mean they're doing more than 20 minutes of work.

    33. Re:Exactly this. by melchoir55 · · Score: 1

      You "Only" get to chat 1-2 hours a day? If you are chatting for more than 2 hours a day, you aren't working.

    34. Re:Exactly this. by Grishnakh · · Score: 2

      Also in practice, the less-than-1% of the US in Alaska/HI can be ignored, leaving us with 4 time zones with more than 99% of the population.

      You're correct, but only for a while. The people of Massachusetts are thinking of switching to the Atlantic time zone, so the US might span 5 time zones pretty soon.

      http://www.bostonmagazine.com/...
      http://www.bostonglobe.com/ide...

    35. Re:Exactly this. by Grishnakh · · Score: 1

      Why would anyone marry a poor man when a wealthy one is worth more money?

      Women marry poor men because they can't snag a rich one if they don't have enough to offer: not pretty enough, not smart enough, too crazy, etc. If a woman has a lot to offer, she doesn't marry a poor man. So poor men get whatever's left over: women with no education, women missing teeth, women with 5 kids by 5 different fathers who are 29 years old and look like they're 49, etc. If you see a poor man with a gorgeous woman, unless there's some other factors at play, most likely what happened is that she's such a psycho nutcase that other men wouldn't have anything to do with her so she got desperate and had to marry whoever she could get.

      The problem with STEM vs. MBA is that dumb people can't get STEM degrees (from any decent institution at least), and can't perform in a serious STEM job. It's not like the smartest people can go get MBAs and the dumb people can go into STEM and work for them; such companies won't survive. You can't just go get a bunch of average people and get any kind of quality STEM work out of them.

    36. Re:Exactly this. by Grishnakh · · Score: 3, Funny

      Exactly. And it's not just programmers, it's other laborers too. I have a small business and I really need to hire some competent employees. I'm willing to pay them $0.50 per hour. Why can't I find anyone willing to work for that???? We need to eliminate these minimum-wage laws and let me import workers willing to work for that!

    37. Re:Exactly this. by beelsebob · · Score: 1

      Given that the premise of the article is "in order to get hold of the other 95% of programmers who are NOT in america" only counting US states is somewhat disingenuous.

    38. Re: Exactly this. by Hognoxious · · Score: 1

      ... let alone whether the work they're doing is any good.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    39. Re: Exactly this. by Hognoxious · · Score: 1

      hmm? maybe I worded it wrong?

      Don't flatter yourself. You're much more fucking ignorant than that.

      http://en.wikipedia.org/wiki/P...

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    40. Re: Exactly this. by Shados · · Score: 2

      Except the reason people are jump hopping has nothing to do with money. It used to be that way during the dotcom recovery, but today? Its been quite a few years since I honestly heard someone hop for money reason. And yes, there's always the occasional exception... Oracle has a low turnover rate in some of their offices. Mainly because its the only big name company that will hire some of these people, so they don't dare leaving.

      But in the bay area? Most people hopping are doing it from startup to startup. Not for money reasons, but because they got bored of their previous job, and because honestly, they can. Lately, its almost a given for a lot of people that they'll hop after 1-3 years, regardless of how things are going, just for some change. Loyalty? Its a lot more personal now. Devs are not loyal to their company, they're loyal to the people they work with. These people hop, they hop with one of them.

      Now thats not everyone, so of course you'll find exceptions...but even the best places to work for still see the same turnover rate. Most of the ones with low turnover are the places you DONT want to work at.

    41. Re: Exactly this. by m00sh · · Score: 3, Interesting

      If these companies were hiring a cook they would require 3 years experience working on an Ace cooktop, 5-years experience with Acme Food Supply, and be able to demonstrate the restaurant's recipe for their signature meat dish before being considered.

      Companies didn't come into existence with their particular toolsets: they learned them, and quickly. Then they refuse to consider hiring anyone who doesn't already know them in depth.

      I've seen certain fortune 500 companies advertise software engineering job positions that do not require any experience, do not list any requirements (except high school) and job description is as vague and all-encompassing as desire and ability to write software. That does not make getting that position easier to get.

      The biggest unwritten requirement is if you'd want to spend and interact 40+ hours a week with that person. That is why most women programmers no matter how inexperienced will always get hired very easily. Programming ability matters very little when the guy is a weirdo and awkward to deal with.

      Not that I'm implying you're a weird or anything, but when a guy walks in the door, people fear for the worst. Until you get to know someone, guys think other guys are creepy or bad. Thus, it is very easy to get a friend hired in your company but if a friend doesn't want to give you the recommendation in his company, that probably means your friend doesn't like you and wouldn't care to work with you.

      Despite what Slashdot and their parent Dice would like you to believe, job hunting is largely done through connections. If you are reading job requirements and fuming over not enough experience and what not, you're probably exhausted your contacts. Employers also fear the worst of the applicants coming through random job searchers and will scrutinize them more than if they came through connections.

      It is blatantly false that companies will not consider hiring anyone who already doesn't know the tool in depth. The biggest tool to learn is the company software repo, the business and culture of the company which is the least documented. Any commercial tool can be learned in weeks or months since there are thousands of resources on it. Learning the company source code base and all the ways the company works is the hardest part.

      My psychology book said that in most cases people make up their minds unconsciously and then go find reasons to justify it. I read somewhere (and it could be completely false) that an interviewer decides to offer a job or not very quickly and spends the rest of the time confirming it. I have found that it's the weird things that get people hired. If they were in the same fraternity, attended the same university or some other commonality. I hate to say it but if a team leader is Chinese, you will find that a lot of junior Chinese developers and this is because ethnicity is a super-obvious observation. Sometimes, entire teams have hidden commonality like an fraternity, an ex-employer or a university.

      Anyway, I've been turned away from many jobs that I was qualified for and had the technical skills for. But, if I want to land that job right after an interview, I have to have connections or be a super-charming person. Everyone thinks they are geniuses in their own right but others think differently. The most qualified candidate isn't the one who always gets hired. In the end, in software development, it is the team effort than the individual that matters.

    42. Re: Exactly this. by s.petry · · Score: 1

      Not quite. The better a analogy is that if they were hiring a chef that wanted to be paid as a chef, they would claim no chefs exist in the U.S. market and petition for more minimum (or less) workers. Time to reinvent poison?

      --

      -The wise argue that there are few absolutes, the fool argues that there are no probabilities.

    43. Re:Exactly this. by Cammi · · Score: 2

      I am in Alaska as well, AK Marc. I am in Juneau, to be precise. We have no shortage of programmers in this town. We do have a shortage of companies that want decades of experience and degrees. Both which are not needed to do the job they are hiring for. Then we have the public sector ... State of Alaska for example. They pay 1/4 the average wage for a programmer, shoddy benefits (the new federal health care is cheaper for much better coverage, but we can't get it due to the union (thanks union!))... Raises? What raises... 1% if you are lucky every year. And let's not talk about how they scam people out of their puny raise when you hit longevity. They are literally trying to get rid of employees then turn around and complain that there are no programmers ...

    44. Re:Exactly this. by Pseudonym · · Score: 1

      Are you one of those idiots who thinks programming is harder than philosophy?

      I am not the OP, and I don't think this, but someone with a high qualification in one field may, thanks to the Dunning-Kruger effect, overestimate their aptitude for a different field. Plus, "self-taught java guru" is a red flag by any measure.

      Yeah, I'd consider them if they had a relevant referee or a portfolio, like a github repository that I could inspect. A smart person is a smart person and formal qualifications aren't everything. Besides, their PhD might have been in logic.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    45. Re:Exactly this. by Ksevio · · Score: 1

      . The people of Massachusetts are thinking of switching to the Atlantic time zone

      As a resident of Massachusetts, that's news to me! Looks more like a couple op eds discussing it than any serious debate.

    46. Re:Exactly this. by Grishnakh · · Score: 1

      Looks like a good idea to me. Why bother being on Eastern time only 4 months out of the year and Atlantic time (effectively) the other 8; why not just stay on Atlantic time year-round?

    47. Re: Exactly this. by Immerman · · Score: 1

      You wield that citation as though you think that one specialty definition is the definitive meaning of the word "peek" - I'm not sure you should be the one to call other's ignorant.

      --
      --- Most topics have many sides worth arguing, allow me to take one opposite you.
    48. Re:Exactly this. by laird · · Score: 1

      "But don't blame the process, blame the people who don't implement it well."

      There's some truth to this, in that working remotely can work well, but there's a lot that you lose by not being co-located with the people you work with. That can be fine if you're working relatively independently, but if you're functioning as a part of a team and need to interact with them regularly, there's more friction involved if you're not co-located. It's not insurmountable, of course. But it's a lot easier for someone working remotely to "disconnect", because you can't see each other as casually, just in scheduled meetings, so you lose all of the informal lunch/hallway discussions, which have a lot of value. And, of course, when someone is remote they have less direct oversight, which can, if they lack discipline, lead to them spending a lot of time not getting work done. There are tools that help - IM, video (Skype, FaceTime, Hangouts), etc. But it's pretty consistent that, all things being equal, a team of people all in one room will generally work more effectively than a geographically dispersed team, because there's an energy and momentum that a team builds in their space, and a team bonding and commitment, which is hard to make work remotely. Because people aren't just "skills on legs" they are social creatures, and being in the same places works better for most people.

      Of course, things aren't always equal. If the perfect developer that fills needed skills is remote, and won't move for the job, and you can't find anyone local who can do the work, you're certainly better off with him remote than not having the skills on the team at all (and failing).

    49. Re:Exactly this. by laird · · Score: 1

      Don't bet on it. The large majority of real estate agents make very little money most of the time - big deals that pay well are relatively rare, so the cash flow is erratic. There's a small number of agents who are making huge money doing huge deals, of course.

      Being a programmer gives you pretty good job security, and a consistent income, unless you've stayed current with mainstream technologies.

    50. Re: Exactly this. by gregmac · · Score: 1

      The biggest unwritten requirement is if you'd want to spend and interact 40+ hours a week with that person.

      This is certainly an important point, and ties into one of the things that really turns me off potential hires: admitting limitations.

      I can't tell you how many times I've asked a question like "I see you've listed X, Y and Z as languages you are an expert in, but I don't see anything explaining where you have experience in language Y -- where did you use Y and what did you do with it?" and gotten answers anywhere from "Well, I used it for this one assignment in school" to "Part of the code I worked on talked to the piece written in Y, though I didn't actually work on that myself" to "Oh really? That's not supposed to be there".

      Personally, I give absolutely zero craps about the specific languages and whether the job they are being considered for uses them or not: my philosophy is that any reasonable developer can learn any language / toolset necessary. But I do care very deeply that the people I work with are honest. I'd rather someone admit they don't know something than muddle through and not make any progress.

      So when someone misrepresents themselves during the interview, this tells me a lot about their character and what it would be like working with them, and someone that doesn't admit their limitations is not someone I enjoy working with.

      Seriously, no one knows everything. No one expects everyone to know everything. It's okay to say "I don't know" in an interview. One of two things will happen: The interviewee will get the job anyway, and the company will know they'll either have to invest in training them in the things they don't know or not have them do those things; or the interviewee won't get the job because they aren't qualified and the employer can't train them.

      By the way, I've had the opposite response once, from a very junior developer: "Well I did it in school, and then also used it for this personal project, but didn't really think it was relevant for my resume since I didn't get paid". That person got the job (and some resume tips).

      --
      Speak before you think
    51. Re: Exactly this. by serviscope_minor · · Score: 1

      That's 2 more months of peek productivity at the tail end when your engineer is at their best. That could translate in hundreds of thousands, of even millions of dollars depending on the size of your business.

      If the programmer staying at the business is generating hundreds of thousands or even millions in TWO MONTHS, then why isn't the company paying a salary of a 50 thousand dollars a month?

      That would solve the problem of the programmer disappearing and they'd be very well into the black.

      --
      SJW n. One who posts facts.
    52. Re:Exactly this. by jmcvetta · · Score: 1

      I've been freelance for a long time, so I'm no stranger to uncertainty, erratic cash flows, and the hustle to find new clients. Seems like it might be a tad nicer with bigger paydays for less laborious work.

    53. Re: Exactly this. by Hognoxious · · Score: 1

      You wield that citation as though you think that one specialty definition is the definitive meaning of the word "peek"

      It's the only one associated with "poke" and "address". Did you ever touch a computer before 2011?

      I'm not sure you should be the one to call other's ignorant.

      Clarify please - what thing belongs to the other?

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    54. Re: Exactly this. by Immerman · · Score: 1

      Ah, a lame deadpan joke delivered by a pedant with a bad attitude. And here both Shados and I read your comment as though you had something to say.

      --
      --- Most topics have many sides worth arguing, allow me to take one opposite you.
    55. Re:Exactly this. by Ksevio · · Score: 1

      It does sound like a good idea, but there's no serious discussion about it.

    56. Re:Exactly this. by Grishnakh · · Score: 1

      We need to pass another amendment to repeal the 13th. That amendment isn't "business friendly". We need to just let the Free Market work without any of this government interference!

    57. Re: Exactly this. by cthulhu11 · · Score: 1

      In my last job search I was stunned to find that time and again I was down rated for having been in place for 15+ years. So tired of every person at a given company harassing me about it. When I restructured my resume so that through the acquisitions I listed 2-3 positions instead of one the situation improved dramatically.

    58. Re: Exactly this. by pnutjam · · Score: 2

      How is it hard to leave a job? The only job that's hard to leave is the one that's paying you well and providing a good environment.

    59. Re:Exactly this. by Jane+Q.+Public · · Score: 1

      That can be fine if you're working relatively independently, but if you're functioning as a part of a team and need to interact with them regularly, there's more friction involved if you're not co-located

      Nonsense. I repeat: only if you're not doing it right.

      I worked as part of a team who mostly worked remotely and we actually worked BETTER that way. We actually communicated BETTER and more often remotely, via IM, Campfire, and telephone, than when we were working in the same office, in the same building. Just truth, no exaggeration.

      Management has to be willing to set things up properly so you can do that. But as much as I hate to keep repeating myself, it can work BETTER than the other way.

      By the way: our product turned out great and was acquired by a multi-Billiion $$ corporation.

      I have worked that way ever since and it has usually turned out okay. There have been a couple of exceptions. I worked for one outfit that claimed to be Agile but that actually turned out to mean they tried to use Pivotal Tracker to micro-manage anyway. That isn't Doing It Right.

    60. Re:Exactly this. by MachineShedFred · · Score: 1

      I work on a team that is 50% remote, 50% local. I'm in the remote bit.

      We have a 3-per-week video standup, and we use Slack to stay in touch. Our development infrastructure is in an Amazon VPC with VPN access, so everyone can connect and check in code and documentation, as well as test on the dev and stage servers.

      Part of the team is in Silicon Valley / San Francisco, and then the rest are in Colorado, Indiana, Ohio, and a contractor in Europe.

      We've never missed a date, and our team outperforms every other team in the IT shop in the company to the point where we are taking over their systems in 2015.

      Remote can work, if you have motivated employees and good management. And, it allows us to recruit from outside of the echo chamber that is Silicon Valley to get quality people that aren't compulsive job-hoppers. There is talent to be had in the midwest, and throwing California salaries at them is a good way to get them and keep them.

      --
      Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
    61. Re:Exactly this. by MachineShedFred · · Score: 1

      Yeah, just like house flipping seemed like a great way to make money 6 years ago. Then the bottom fell out and everyone lost their shit.

      Grass is always greener, and all that. Get good at what you do, and leverage it. If you're only mediocre at what you do, either get better or find something else that you are good at.

      Nobody pays well for mediocre.

      --
      Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
    62. Re:Exactly this. by Andy+Dodd · · Score: 1

      I think this is why many open source projects use IRC for communication, and good ones usually discourage people from taking things to PM.

      Even if it doesn't directly pertain to someone immediately, someone will often think, "oh, I remember X and Y talking about this a few weeks ago" - at least for OSS projects, IRC replaces the "office chat"

      --
      retrorocket.o not found, launch anyway?
    63. Re:Exactly this. by jmcvetta · · Score: 1

      Sure, the best workers in a given profession usually earn more than the average worker. Duhhh.

      More interesting, when comparing different professions, is to look at typical earnings for the average worker. In that regard software development beats the pants off food service and menial labor. But it falls far short of occupations such as finance, real estate, and some guild-restricted professions like law and medicine.

    64. Re:Exactly this. by sribe · · Score: 1

      There's just a hiring pathology.

      Yep. Dealing with it right now. Definitely worse now than the last time (10 years ago) I needed some new work to fill my schedule.

  2. They want you there... by TWX · · Score: 1

    ...so they can keep an eye on you, so they can 'manage' you.

    There's a whole lot of BS in this world, and many of the people that sling the BS best can't really do much else. They talk a great game, but they produce little to nothing. The problem with this is some endeavors, like writing software in a collaborative setting, make it difficult to measure the contributions of the individuals that are supposed to be applying themselves. It's not so easy as simply counting lines of code or commits or functions written when there's distinct possibility that flaws in those contributions will require extensive rewriting or will end up being orphaned code, and further complicating matters, there's no good way to measure how only slightly flawed code, easily corrected by another, contributes to the project. Either a project maintainer must keep on top of all of the code all of the time, which is a daunting task, or they must keep on top of the people, to see what they're doing, to measure how much they're applying themselves and how much time they actually spend working.

    I'm sure I'll be flamed for this perspective, but given the sheer number of distractions around us these days, it's very easy for someone to do anything besides their paid job.

    --
    Do not look into laser with remaining eye.
    1. Re:They want you there... by wierd_w · · Score: 4, Insightful

      The problem with the latter approach, is that programmers spend time when they arent working, thinking about the problem they are being paid to work on when they are working.

      EG, they may have the sudden epiphany while playing super mario brothers, that they have failed to have while sititng in their cublcle, trying so very hard to push that solution out under great duress from their manager.

      Or, as archimedes had his epiphanies-- In the tub.

      This is not a new thing, and creative problem solving REQUIRES downtime to be effective. The people that insist "You arent applying yourself all the way, therefor I will ding you on your reviews!" are a problem, not a solution.

    2. Re:They want you there... by rmdingler · · Score: 1

      They talk a great game, but they produce little to nothing.

      I wonder if the two skills are generally mutually exclusive.

      Any thoughts?

      --
      Happiness in intelligent people is the rarest thing I know.

      Ernest Hemingway

    3. Re:They want you there... by beelsebob · · Score: 2

      No, they want you there so that they can talk to you, have face to face meetings with you, and have casual chats. Because all of these things are where actual decisions get made. Having one half hour Skype chat a day, in the 1-2 hours that you're online at the same time just does not cut it for getting everyone pulling in the same direction.

    4. Re:They want you there... by BarbaraHudson · · Score: 3, Interesting

      No, they want you there because they are incompetent at managing, so they've got to have endless meetings and interrupt you all the time to justify their existence. The whole "management is giving people a task, the tools they need to solve it, and making sure nobody else gets in the way" mentality is GONE.

      We complain about "hover parents", but micromanagers (or "hovermanagers) are just as toxic.

      --
      "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
    5. Re:They want you there... by AK+Marc · · Score: 2
      Management is hard remotely. Management is more than telling someone what they need to do by the end of the day. Having the ability to have more frequent casual conversations easily allows managers to better plan deadlines (Bob hasn't asked for time off, but is talking about a planned trip 6 months from now, so don't schedule anything then that Bob is required for - the corporate answer is deny Bob's leave request when it comes time, as he didn't place it early enough for anyone to plan around, but he didn't want to place it then because the plans weren't firm). And personal development. Workers are loathe to tell their boss "I don't do XXX well". In an office, it's easier to see that for ones self, then try to make training for XXX available to those who wish to take it (no need to even name Chris, if he wants it, let him take it, if not, then know he'll never be good at it and plan accordingly).

      Light-touch bossing (the best kind, based on employee reports) is harder with distance.

      Technical supervision is easy. "I need a bubble sort added to the library by Tuesday. Bob, that's yours." Tuesday comes. It's there or it's not. Then look at the code. The merge sort used didn't match the requirements, or the bubble sort is recursive in an unstable way, or other problems. Whether the person is next to you or 10,000 miles away, you can evaluate the objective results of most tasks, and then take action.

      measure how much they're applying themselves and how much time they actually spend working.

      If your main concern is keeping your employees "busy" rather than productive, then you are doing it wrong. I don't care whether someone is spending 8 hours a day sitting at their computer staring at it, or 2 hours. If they do the same work, it's all good. The corporate mentality these days punishes fast workers. Do 8 hours in two? Then you either need to get another 24 hours worth of work to keep you busy, or spend more time trying to look busy than being busy. Both of those are bad (as implemented by most corporations).

    6. Re:They want you there... by sjames · · Score: 1

      A manager that CAN'T look at those things in a telework setting isn't looking at those things locally either. All he does is look at whose butt is in the chair and whose isn't. In other words, telework presents a problem for a manager that doesn't know how to do his job in the first place.

      Consider, two guys sitting at their respective desks. Both in the same posture, both have their fingers flying across the keyboard. Both participate equally in the weekly post-pre-meeting meeting. One of them asked dumb questions and totally screwed up 3 important modules badly enough that they had to back his week's work out. The other got module x back on schedule. However, a third employee sipped coffee in the break room all week, then spent 5 minutes on Friday afternoon committing the fix for that bug that cost a million in sales last year and was on track to cost 2 million this year.

      Guess who the poor manager who can't evaluate the quality of a commit gives the old heave ho to? Guess which two get the full 3% annual pay raise?

    7. Re:They want you there... by unimacs · · Score: 1

      As a programmer and now a manager I want people in close proximity to each other to facilitate communication with each other, project sponsors, and end users. I also want staff that communicate well. This often leads to better results in less time. It's not that projects can't be successful any other way, I just consider it more ideal. No situation is perfect. I also recognize that staff may also need the opportunity to be free from office distractions so I support working from home as needed. Hopefully next year I will be able to push through a policy that will allow staff to work from home up to a couple of days a week on a regular basis.

      Wanting the staff in the same location isn't really about managing them in my case.

      There are multiple paths to a long and successful career in IT (or anything else), but there seems to be a large number of programmers that just want to sit in front of a computer, grind out code, and avoid everything else. Lots of other things that need to happen for a project to be a success and getting good at some of the soft skills is more important than a lot of IT people seem to realize.

    8. Re:They want you there... by BarbaraHudson · · Score: 1

      I want people in close proximity to each other to facilitate communication with each other, project sponsors, and end users

      Telephone, email, text, chat, I'm sure they know how to use at least one of these ...

      --
      "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
    9. Re:They want you there... by TWX · · Score: 1

      More people talk a great game without producing than talk a great game and actually produce.

      --
      Do not look into laser with remaining eye.
    10. Re:They want you there... by unimacs · · Score: 1

      Workable but not as good as face to face communications. It's just not. Also does not facilitate the add hoc conversations that take place or allow for simple things like going out to lunch.

      Telephone, chat, text, email all have their place and have their own advantages. I use all of them. But exchanging information over chat or email is like having a crappy dialup connection vs. Gigabit ethernet. Sometimes it's good enough but a lot of time you can accomplish more in a 2 minute face to face conversation than you can in several email exchanges or texts. There is simply more bandwidth, - more information is exchanged more quickly face to face.

      If you don't like that analogy, think about working on a 13" laptop screen vs a large dual monitor setup. It's not that it can't be done, - but which is more productive?

      Just sharing a space can have advantages. Have you heard the term "information radiators"? Much harder to do well on-line.

    11. Re:They want you there... by TWX · · Score: 1

      Except that it's easy to ignore the telephone, e-mail, text messaging, and software-based chats, especially when one is out shopping or playing video games or working on personal stuff out in the workshop.

      I'm starting to wonder if maybe more employees, rather than less, need to be made hourly and not exempt from receiving overtime. Employees that do not supervise less than four other employees, for example, regardless of what they actually do for a living, that personally own, not as a retirement fund, less than 10% of the company. If the point of being salaried originally was that the salaried employee had a stake in the company itself and could write their own hours as they managed how the company operated, then the entire point of being salaried is shot to hell nowadays.

      --
      Do not look into laser with remaining eye.
    12. Re:They want you there... by jmcvetta · · Score: 4, Insightful

      While ago I worked for a venture-backed company. The code was an awful steaming pile of dog shit. But a few modules were much higher quality than the rest. Logical design, solid implementation, good comments, full test coverage, etc. The programmer who wrote them had only worked for the company a few months before he was canned - apparently management thought he sucked balls.

    13. Re:They want you there... by beelsebob · · Score: 1

      No, it's not manager to engineer communication that's the problem. It's engineer to engineer communication. That is far far more important, and the thing that gets lost.

    14. Re:They want you there... by BarbaraHudson · · Score: 1
      If you want face-to-face, use skype or another video chat program. It's been shown that takes about 15 minutes to "recover" from an interruption . Now when you personally wander over to a developer and interrupt him/her "just to see how it's going", you've burned 15 minutes. It's why so many devs find themselves at their most productive at night, when nobody is interrupting them.

      An interrupt is defined as "any distraction that makes a developer stop his planned activity to respond to the interrupt’s initiator". There were three types of interrupts defined: personal visits, telephone calls and emails. Personal visits and telephone calls caused 90 percent of all interrupts and email caused the rest. The results showed the effort spent on interrupts required approximately 20 minutes for each occurrence, including the time spent handling the interrupt, and that the average developer receives three to five interrupts per day. This consumes roughly 1 to 1.5 hours per day of the developer’s time.

      --
      "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
    15. Re:They want you there... by BarbaraHudson · · Score: 2

      Bosses would never go for it, because it will mean paying overtime - LOTS of overtime. They keep their jobs only as long as they can get the maximum effort from their underlings for the minimum expense.

      --
      "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
    16. Re:They want you there... by BarbaraHudson · · Score: 1

      No, it's not manager to engineer communication that's the problem. It's engineer to engineer communication. That is far far more important, and the thing that gets lost.

      It doesn't get lost if you've got good people. But you know the saying - 1st-rate people hire 1st-rate people, 2nd-rate people hire 3rd-rate people. If you're not hiring people who can communicate with each other, you haven't hired 1st-rate people, so maybe the root of the problem is the hiring process?

      --
      "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
    17. Re:They want you there... by Shados · · Score: 1

      Devs (like a lot of people in any profession) are pretty damn good at interrupting themselves. People checking their personal email, sport team result, some unrelated chat room, etc. If you watched most devs without them knowing you're looking, without office related interruption, I'd be surprised if half of them went for 30 minutes without interrupting themselves.

    18. Re:They want you there... by unimacs · · Score: 1

      You should really read one of Alistair Cockburn's books. Skype, video chats, video conferencing are poor substitutes for face to face communication. You only see and hear part of what's going on and that's under ideal circumstances (assuming no technical issues, audio, or video quality problems). It's difficult to see them while looking at some other document/interface at the same time.

      You also miss the conversations that you aren't specifically invited too that you may benefit from or have valuable insight for.

      I agree that unnecessary interruptions and distractions can cut into productivity but sometimes an interruption can save you or somebody else valuable time. Nevertheless a good work environment allows people to escape interruption when needed.

    19. Re:They want you there... by unimacs · · Score: 1

      I'll restate it more accurately. A well functioning collocated team can communicate more effectively than is possible for a team of remotely located members. But co-location is not a guarantee of anything. It's not impossible for a remote team to communicate better than a collocated one.

    20. Re:They want you there... by BarbaraHudson · · Score: 3, Insightful

      There's a huge difference between "interrupting yourself" after you've completed a section of code, and someone else interrupting you while you're in the middle of it. Taking a break helps.

      --
      "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
    21. Re:They want you there... by R3d+M3rcury · · Score: 1

      EG, they may have the sudden epiphany while playing super mario brothers, that they have failed to have while sititng in their cublcle [...]

      Or they may not.

      If you're counting on "the truth" to somehow come to you in order to accomplish your task, I'm not sure I'm going to really trust you on a schedule.

    22. Re:They want you there... by BarbaraHudson · · Score: 1

      Each of those is still not as efficient as just say "hey" over the wall. Each has a pro and con. You don't need everyone to be physically at work, and excluding people who work best remotely would be bad, but don't think electronic communications is an actual perfect replacement for being in a close proximity of each other.

      I hate it when people do that. If it were harder to communicate (say, in different buildings) they'd think things through more before asking questions; those that they didn't solve on their own, they'd at least have thought it through, be able to explain the problem much more clearly, and understand the solution when it's shown to them.

      --
      "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
    23. Re:They want you there... by laird · · Score: 1

      Exactly! The rule was supposed to be that managers didn't get overtime, but workers did. But the salary number stayed fixed for many decades, while inflation pushed 90% of workers above the line, so they're treated as if they were managers, who would be getting bonuses, etc., based on company performance. But they're (typically) not.

    24. Re:They want you there... by RabidReindeer · · Score: 1

      You can very easily skive off while sitting in an office in an open cubicle next to the boss. Been there, done that.

      The boss cannot discern anything more about the productivity/quality of a programmer's work by looming over him/her/it, than he/she/whatever can do when the programmer is on the other side of the planet.

      That's because the programmer's quality and productivity have nothing whatsoever to do with what they're physically doing. You could sink the Titanic with stories of people who got their breakthrough insight in the shower, sleeping or even playing "Pong".

      Furthernore, no decent manager is going to be scanning every line of code from every employee. There are better things to be doing.

      There are ways to determine whether a programmer is doing good work and they don't require physsical oversight. First, by the rate of development of the project and the parts of the project assigned to the programmer and the number of times it needs emergency fixes. That, after all, is what you're REALLY supposed to be paying for, not a chair ornament. It's not overnight, but then, if you're not running a revolving-door shop, things add up over time. You want full chairs, invest in inflatable Bozo dolls. If you want "busy" attach clockwork to make them rock back and forth.

      The second way is by listening to ones employees. The programmer's peers are the ones who know the actual code and they'll complain or praise it, whether it's relatively innocuous stuff like the guy I know who never wrote a subroutine if he could cut-and-paste to the person who always delivered overnight but never checked for null pointers.

    25. Re:They want you there... by RabidReindeer · · Score: 1

      What you DON'T want is me.

      I'm not a social person. Put me in a room full of people and I'll no more spontaneously talk to them than if I was on the moon. I can communicate, but I can be at least as confusing face-to-face as I can via email.

      I have a reputation for doing good stuff, but when I work, I work in my own little world and I don't want to be interrupted while I do it. I have a reputation for adapting to user's needs and even suggesting things that the users didn't realize could make their jobs easier, but I need time in between to think things through and to prototype solutions. Not a lot of time - I did Agile years before Agile was "invented", but nevertheless, time. Uninterrupted time.

      Shoving me in a cage of twittering birds is going to reduce my productivity, not enhance it.

    26. Re:They want you there... by Lserevi · · Score: 1

      I've often wondered if pair programming, coupled with an appropriate voting system, would allow compensation to be distributed more fairly. The developers would all experience their relative levels of expertise and could rate themselves accordingly. Naturally, the voting system would have to be carefully chosen.

    27. Re:They want you there... by beelsebob · · Score: 1

      It absolutely does get lost.

      A typical day involving a group of, lets say 4 for arguments sake, engineers in the same room:
      1) 7:30 one of the engineers is an early bird, and likes to get some stuff done in private before the office gets noisy, he gets a couple of productive hours of coding done
      2) 9:30 two more engineers wander in, they have a quick discussion (including the first) about how the widgets aren't quite fitting in well with the bargles.
      3) Inspired by the conversation, one of the engineers realises what the solution, and spends half an hour hacking out a prototype solution.
      4) 10:00 the fourth engineer arrives, and suggests coffee. While standing around the coffee machine, the engineers discuss how frustrated with their manager they are. One of them suggests a reason for his apparently strange actions. This gets shot down, but all 4 begin to understand the situation they're in a bit better.
      5) 12:00 the early bird engineer is getting hungry. He suggests lunch, they grab their manager on the way out. They spend lunch discussing how best to design a rocket to reach LKO in KSP. It's not particularly productive in terms of their project, but they're now closer to each other.
      6) Come 14:00 one of the engineers is getting frustrated, he calls his colleague over to rubber duck an idea off. The two figure out a good solution.
      7) The engineer who prototyped out the solution earlier in the day has come up with a better, more concrete solution, he sends out a patch for review.
      8) At 5 in the evening, the early bird is about to head home. The afore mentioned engineer quickly notes "hey, I have that patch out, and you're kinda best positioned to review it, could you take a quick stare, it should only take 10 minutes". They have a quick sit down discussion, and go over the patch.
      9) Come the evening the patch is landed, as are several others. Everyone heads home

      Now lets say one is in Belgium, one in SV, one in NY, and one is in australia:
      1) The engineer in Australia gets up at 11:00 knowing that he stands a chance of talking to his colleagues if he gets up late. He gets to work at 12:00.
      2) He spends 5 hours working on why the widgets aren't fitting with the bargles.
      3) He Skype calls the engineer in Belgium, who's just got up. He chats about his frustration, and annoyance that the engineer in NY hasn't solved this yet. He goes to bed frustrated with a colleague who he rarely speaks to.
      4) The engineer in Belgium doesn't really consider this his problem, he's too busy working on the Flailing module. He submits a couple of patches, and eventually calls the guys in america.
      5) They have a brief discussion about how the Flailing module is working, and how it fits in.
      6) The NY engineer works on integrating the Flailing module, not realising that his design for the widgets isn't fitting well with the bargles. He expresses frustration at the Australian engineer for not getting the bargle module to work well.
      7) The SV engineer sympathises, but is too frustrated with a problem that's at the back of his mind. He's been staring at a screen for several hours now, and his brain isn't working so well.

      Basically, the problem is not anything to do with "good people" or not. It's to do with whether they communicate effectively. Giving each other screen breaks. Allowing each other to bounce ideas off each other. Thinking as a group, and coming up with silly plans that turn out to work well. Just general group cohesion... All of this is lost by having people spread across different buildings, let alone different time zones.

      Remote working is simply less effective, there's no way to recover this lost work.

    28. Re:They want you there... by BarbaraHudson · · Score: 1

      Except that good people CAN communicate via any medium. We do it all the time on /.

      They'll have more than one aspect of a problem to work on, or one problem to work on, and they'll just fire off an email about the current impasse, and go work on the other parts. If the project is so tightly coupled that's not possible, then the design is flawed - seriously flawed. Or if you have people only working on one tiny aspect and it becomes a roadblock to their productivity, you're not giving your people enough latitude or using them to the best efficiency - nobody likes working on just one little bit to the exclusion of all else, especially when working on various parts gives a better view of the problem domain and more informed decision-making.

      In other words, if they need face-to-face communications, fire the manager and the person who hired them.

      --
      "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
  3. LOL Okay by Njorthbiatr · · Score: 1

    It's funny because you can't just mash some numbers together and be like, "FACTUAL STATISTICS!"

    1. Re:LOL Okay by edmudama · · Score: 1

      A newer study just came out saying it was only 77.4%.

      --
      More data, damnit!
  4. Huh??? by bhcompy · · Score: 3, Insightful

    SV makes up only a small percentage of software dev firms. They're located all over the place. Instead of going to work in SV, why not work in Irvine? Santa Monica? Denver? Seattle? Phoenix? Huntsville? Hoffman Estates? etc etc etc?

    And that's not even getting into the fact that many software dev firms allow you to work remotely. Who cares about working at Microsoft or Google if you can work at ADP or Northrop and live much cheaper?

    1. Re:Huh??? by Anonymous Coward · · Score: 1

      Or even outside the US?

      In this day and age, it shouldn't matter where the devs live if they are good enough.

      But using Skype and Google Hangouts? You can't be serious.

      These are NOT for highly confidential team comms especially where unannounced products might be involved.
      How do you know that Microsoft and Google (and naturally, the NSA) aren't monitoring what goes over the links you know just to make sure you are not terrorists/bank robbers/Paedo's etc etc

    2. Re:Huh??? by phantomfive · · Score: 2

      Who cares about working at Microsoft or Google if you can work at ADP or Northrop and live much cheaper?

      The problem there is that then I'd have to work for ADP or Northrop.

      --
      "First they came for the slanderers and i said nothing."
    3. Re:Huh??? by Shados · · Score: 3, Informative

      For scaling teams.

      The vast majority of people won't relocate. People in the tech world are more likely to want to, and people in 3rd world countries are very likely to want to, but in general, people won't.

      So if you need to hire 50 great engineers, your best bet is to go where the highest concentration of them are. Even having to compete with hundreds of other companies, its still better (the ones you lose to others can be made up by poaching). If you go and open up shop in the middle of nowhere, you'll never fill up a large team. Now some of the cities you mentionned are ok (ie: Seattle) too. SV isn't the only spot, of course.

      Telecommuting only works for a small percentage of top of the top, because phones suck, there's no great videoconference solution out there (No, i know which one you're talking about, it sucks. No, that other one sucks too), and text-only communication makes you lose all the non-verbal, making such communication inefficient for complex matters (it works great as a complement though).

      End result: companies need to open up shop in hot spots, and pay the insane amount of $$$ for both real estate and inflated engineer salaries. A few positions can still be filled by remote workers of course, but not the whole thing. Hell, even companies with international offices in the same timezone (ie: a NYC financial with an office in Montreal) have issues with those. It works to some extent, which is why they do it, but its far from ideal.

    4. Re:Huh??? by kamapuaa · · Score: 1

      Because basically all the top tech firms are either based in SV or have a very large presence there? And in a industry where changing jobs and job instability is just the name of the game, having the ability to easily find other work opportunities is basically a necessity?

      While we're at it, why not make your film studio in Montana? Why not open a car factory in Bora Bora?

      --
      Slashdot: providing anti-social weirdos a soapbox, since 1997.
    5. Re:Huh??? by bhcompy · · Score: 1

      Basically all the top tech firms have offices outside of SV as well, as well as all the top Fortune 500 firms, all of which need software developers, all the top biotech firms, financial firms, aerospace firms, etc etc. All of them need software developers in one capacity or another. They're located all over the place.

    6. Re:Huh??? by RabidReindeer · · Score: 1

      Why not open a car factory in Bora Bora?

      Or Spring Hill, TN?

    7. Re:Huh??? by RabidReindeer · · Score: 1

      Companies WebEx all the time these days. Business travel is an expense many attempt to keep to a bare minumum.

      I could care less if I can physically see the people I'm talking to. I can do pretty much anything necessary via Skype, IM, and email.

  5. Physical security as information security layer by tepples · · Score: 4, Interesting

    I can think of a few reasons why some software development companies oppose telecommuting.

    Sometimes, an air gap can be the most effective form of information security. By 1985, Atari was already adding electronically locked doors; see posts about "building access" in Jed Margolin's inter-office memos from 1985. And for years, Nintendo required that authorized game developers operate out of a "secure office facility", explicitly excluding a home office. (Source: WarioWorld.com, the home of Nintendo's software development support group) This caused a bit of drama when Nintendo refused to sell a DS devkit to Robert Pelloni's home-based studio and Pelloni ran to the news media. (Nintendo relaxed this a bit in 2011, possibly to meet a threat of competition from iOS, Android, and OUYA.)

    In addition, a lot of people still live in areas where affordable, reliable, high-speed, low-latency Internet access needed for telecommuting is unavailable.

    Finally, the dynamics of interrupting another team member for a quick answer to a quick question differ between working in person and working remotely.

    1. Re:Physical security as information security layer by BarbaraHudson · · Score: 1

      Finally, the dynamics of interrupting another team member for a quick answer to a quick question differ between working in person and working remotely.

      If they can't bug you right away,
      That's a good thing, I would say.
      Don't let them interrupt you 10x a day.
      They'll try to solve problems themselves.
      Do some research, hit the bookshelves,
      Think things through, stretch themselves.
      In the process they'll pick up their game
      Not wait like zombies, which is a shame,
      Or crying "I don't know," which is lame.

      Burma Shave

      --
      "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
    2. Re:Physical security as information security layer by tepples · · Score: 1

      Those people are not living near a tech-hub, college town, or civilization in general either, and so are not in tech at all, so they shouldn't even be mentioned here.

      The headline is about Silicon Valley going to programmers. This would appear to apply even to those programmers who happen not to have family who are "living near a tech-hub, college town, or [what you call] civilization". So unless the employer is willing to cover relocation costs with a salary advance, that's exactly why they should be mentioned here. Besides, I seem to remember reading that a lot of greater Seattle can't get broadband due to municipal politics.

    3. Re:Physical security as information security layer by tepples · · Score: 1

      One can't seek clarification of a product's requirements from "bookshelves".

  6. Micro-management kills this idea every time by PhrostyMcByte · · Score: 3, Insightful

    No matter what your industry is, some PHB is going to get into a position where they feel out of control and unproductive if they can't get instant gratification popping in on their people to micro-manage them. In-person meetings are a must for these people.

    1. Re:Micro-management kills this idea every time by hot+soldering+iron · · Score: 2

      That's partly what killed our office. Unfortunately, the PHB that did the deed was the owner of the company, and we eventually found him to be a lying ass hat. Tip: don't lie to database analysts, they are used to digging for data and finding inconsistencies.

      --
      When you want something built, come see me. If you want correct grammar and spelling, get a F*ing liberal arts student.
  7. The best and the brightest... by Anonymous Coward · · Score: 1

    ...are the ones with imagination, foresight and creativity - not the ones who can pass the silly college-quiz-style interviews and look appropriately hipster, as the big companies require.

    Frankly, commercial software development for its own sake is not a place you'll find very bright people. If you want to look for them, go into more traditional engineering or scientific fields or finance (alas). And the best minds, i.e. the ones directed entirely to scholarship rather than the least work for the most income, will be found in academia.

    1. Re:The best and the brightest... by peragrin · · Score: 1

      While not untrue the problem with acdemia is twofold. A failure to deliver on projects and a desire to do only prone ts that interest them. A designer of garbage cans isn't very interesting but it still has to be done. Some one has to design the toliet paper hanger,and shower curtain rod.

      Software is no different the really good pieces are tiny. The number of nuts,bolts hanger rods and misc crap is just if not more so important. Mainly because it isn't the interesting part that develops problems but the boring bits. Without the boring bits the rest of it isn't usable.

      Think how often you use the delete function or real world trashcan.

      --
      i thought once I was found, but it was only a dream.
  8. Re:If 95% of great programmers aren't in the U.S. by rmdingler · · Score: 1
    It doesn't matter how high a duck flies,

    you can always break a window with a hammer.

    --
    Happiness in intelligent people is the rarest thing I know.

    Ernest Hemingway

  9. business logic in your website theme, wtf.

  10. IMO, it trends whichever way the wind blows.... by King_TJ · · Score: 2

    I was just talking to some people yesterday about the popular trend in offices to build open floor-plans in lieu of the traditional cubicles and dividers.
    Even Google embraced the open floor-plan concept, yet I can't find much evidence from people working in such an environment that they find it an improvement?

    Basically, people are remodeling in this style because it's viewed as more trendy and insightful. Never mind the fact that the old way was probably done for good reasons and to solve real problems. (Open floor-plan offices have serious problems with noises, distractions and a lack of appropriate places to go make a phone call with a client or vendor. They remove the privacy of the individual worker, causing everyone around to see every little thing you do. Duck out for a smoke break or to use the rest-room? Everyone immediately sees how long you're not occupying your seat and can make judgements on your behavior.

    Same thing with this argument of using remote, "work from home" employees vs. making people come in to a central office. There are, IMO, many good reasons to expect your employees to be physically present in a central workplace each day. (Companies like Yahoo, who tried letting people work from home, decided to ban the practice when it turned out to be a failure for them.) Truthfully, I love having the ability to work from home in my own job - but I do computer support and systems administration work. Realistically, I usually wind up coming in to the office and only working from home about one day each week. In my situation, I'm (thankfully) given permission to make judgement calls about when it's most sensible for me to come in, vs. stay home. If I expect it will be a day of nothing but phone calls, helping users via remote access to their machine, and working with cloud based services we use? Then sure, I can do it from home. Many other times though, I'm expecting a package to arrive with a part to replace for somebody, or I'm just able to provide people a better level of service if I can look at an issue hands-on with them. (Remote control software is all but useless if you're trying to figure out why they're having monitor issues, for example. It may look fine on YOUR remote session screen even if their display is going bad.)

    I know a number of our creative workers putting together marketing proposals and the like do better work when they're in a group together, in-person. We've given them plenty of tools to collaborate remotely, and sometimes they do. But there are still lots of limitations with the technology, including internet bandwidth issues for some people, meaning their video keeps breaking up or their audio gets choppy on a conference call. And ultimately, you can't celebrate with co-workers for a job well done by remotely taking them out for dinner or a few drinks, either.

    I've become more and more convinced that the best solution is a mix of allowing SOME work from home or remote, and SOME expectation of coming in, in person. You won't be able to keep "best in breed" software development going with a scattered workforce who only collaborates video video chat, IM, email or phone calls.

    1. Re:IMO, it trends whichever way the wind blows.... by xSquaredAdmin · · Score: 1

      Even Google embraced the open floor-plan concept,

      I think that the difference is that Google seems to do it correctly. I've worked in both Google offices and in other companies that did "open floor-plan", and I noticed a few things that Google does right:

      • It's open within small groups (~12-15) of desks with higher walls separating the groups. This generally means that you have a team sitting together with open communication and you don't have to worry about noise/distractions from other teams.
      • They have meeting rooms of various sizes, from non-bookable phone rooms (often used for personal calls) up to larger meeting rooms. People are encouraged to grab a meeting room if they're having an in-depth discussion with multiple folks.
      • Common areas (kitchen, cafeteria) are separated from work areas. This means that visual/auditory/olfactory distractions from those areas are minimized, while still providing a place for people to get together and chat informally.
      • There are quiet areas for people to focus. Most office have quieter "library" style areas, as well as "wellness" rooms with comfortable chairs/dimmable lighting. I have migraine issues, so the wellness areas were invaluable to me.
      --
      Crushing dreams at the speed of sarcasm
    2. Re:IMO, it trends whichever way the wind blows.... by Maxo-Texas · · Score: 1

      In my experience as a manager, some employees abuse working from home.

      More importantly, they become less productive and fail to meet deadlines and requirements that others make.

      And finally, some people get very hard to reach when there is an emergency (when they are supposedly at home within 50' of their phone at all times except lunch).

      The second and third parts are what matters. The real way to manage them is to write people up, document, and either withdraw the wfh privileges or let them go if the situation is bad enough.

      It's partially a problem with management not being willing to enforce the rules on people wfh. It's partially a problem with wfh people being able to hind and rationalize their abuse of their privileges.

      If it is just about seeing people, you could put in a skype solution.

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    3. Re:IMO, it trends whichever way the wind blows.... by cascadingstylesheet · · Score: 1

      I was just talking to some people yesterday about the popular trend in offices to build open floor-plans in lieu of the traditional cubicles and dividers.

      Actually, it's the open plan offices that are "traditional'. Watch an episode of, say, Barney Miller. Cubicles were this new-fangled innovation, etc.

      Now it's coming full circle ... meh.

      Notice that the bigwigs always had their own offices, either way. With doors even.

    4. Re:IMO, it trends whichever way the wind blows.... by Anonymous Coward · · Score: 1

      I would love to work from home, except my Wife doesn't understand that when I'm working from home, I'm trying to actually WORK. Even though the option exists, most of the time I still go into the office because if it's not my Wife wandering in to pester me with small questions all day long, it's the kids wanting to see Dad or the dogs freaking out because there's a deer in the yard.
      Granted, my wife pesters me at work too, but I can ignore text messages until I take a short break, and my direct line has voicemail. If there's an actual emergency, she has the number for the front desk and the Receptionist will let me know it's urgent.

    5. Re:IMO, it trends whichever way the wind blows.... by jmcvetta · · Score: 1

      Open floor plans and cubicles alike indicate that a company doesn't really value the employees who work therein. If a company truly values a worker, they put their money where their mouth is and give that worker a real office. But talk is cheap, whereas real estate is expensive.

    6. Re:IMO, it trends whichever way the wind blows.... by Anonymous Coward · · Score: 1

      some people get very hard to reach when there is an emergency (when they are supposedly at home within 50' of their phone at all times except lunch).

      How often do you have these "emergencies"? Lotta companies are in a more or less permanent, contrived state of crisis - as a management technique.

    7. Re:IMO, it trends whichever way the wind blows.... by Maxo-Texas · · Score: 1

      We had a rotating on call. When you were on call you were expected to respond quickly.
      As we were going thru a conversion to SAP there were constant issues.
      During non SAP periods the load was pretty light. You might not get a call for 3-4 weeks at a time.

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    8. Re:IMO, it trends whichever way the wind blows.... by Maxo-Texas · · Score: 1

      And besides, I don't see how your point matters.

      If you can't do your job, the company should let you go.
      If the company is abusing you, you should let the company go.

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
  11. Living in the US by ofranja · · Score: 1

    Also, a lot of programmers might be willing to relocate if needed, but would never relocate to the US. Which is exactly my case, BTW.

    --
    EOF
  12. Timezones are important by davecb · · Score: 2

    It's easy to cooperate with people who are awake and working at the same time as you. Managing projects up and down the US east coast was easy from Toronto.

    If you have people in San Francisco that start 3 hours later, you have to intentionally organize for that time difference. Some people here worked late hours (including at least one night-owl friend who liked to come in at noon), while others cursed the absence of their colleagues. Still other gloried in the absence, and said things like "I get three uninterrupted hours of work!"

    If QA was in Ireland (or India, or both) then people learned to hand off discrete chunks, and get the results in the morning. With people across either the Atlantic or Pacific, you get one meeting a day, so make the best of it!

    One group did time-critical diagnoses, and had three shifts running: Singapore, Grenoble and San Francisco. They passed the same bug around the world, working continually on it until they got done.

    Working in multiple timezones can work well, but only if you plan for it.
    If you don't plan for it, you'd better keep your business in the zone you're in.

    --
    davecb@spamcop.net
  13. Management will support this kicking and screaming by erp_consultant · · Score: 1

    It is quite easy to make logical arguments for why it makes sense to work remotely. The problem is that the buck stops at your managers desk. If you are fortunate enough to have an enlightened manager that trusts you to get things done then you will likely both benefit.

    Unfortunately there are still a lot of managers that have this rigid, old-school mentality that dictates that they must watch your every move, every day. They are more concerned with what time you come in to work and how long you take for lunch and how long your coffee break is than what you actually do all day. Sadly, some of them have no idea what you do. And they don't care. These are typically the people with no real skills. The type of people that see everything as some sort of power grab. The ones destined for middle management purgatory.

    The good news is that it will change, whether they like it or not. I am seeing this already in my line of work. I used to have to travel every week. Now it's about twice a month, if that. On my end, I just need to make sure that I'm getting my stuff done on time at a high quality. Management - rather than focus on the nonsense above - can focus on productive tasks. And so can I.

  14. Re:YIIIPPPPEEEEEEE!!!!! by slashdice · · Score: 1

    duxup loves you.

    --
    Copyright (c) 1990 - 2014 Dice. All rights reserved. Use of this comment is subject to certain Terms and Conditions.
  15. No. Reciprocal loyalty is dead. by tlambert · · Score: 4, Interesting

    No. Reciprocal loyalty is dead.

    If you work in SV, you can likely walk away from a tech job you can't stand and have another tech job inside a week. Some people can do it the same day.

    If you work in Omaha Nebraska, you can walk away from a tech job you can't stand and have another job inside a week. At Pizza Hut.

    There's a huge benefit to the worker to being able to switch loyalties quickly in an industry which is notoriously disloyal to their workers; some people's notification comes in the form of them coming back from a trip and finding that their badge no longer opens the door.

    There are also economic factors. First, it's very east to relocate from San Francisco to Omaha, because it's an economic downslope. It's very hard to migrate from Omaha to ... well, anywhere ... because it's an economic upslope. The equity in your house or condo will convert out nicely, going one direction, and will end very poorly going in the other.

    Finally, there are the social aspects; I'm not just talking about nightlife, or the bar scene, or sexuality issues, I'm talking about having a group of friends and acquaintances with whom you can maintain face to face contact, who are able to help you out in a job search, which simply doesn't exist, if you're looking for a tech job, but don't live in a tech Mecca. It's just not going to happen. So when your company is disloyal to you (read: let go, RIF'ed, laid off, temporarily cut back, or any of the other euphemisms), there's no reciprocity.

    Gone are the days you could move to Southern Utah, go to work for Browning Arms, and write IBM 360 assembly code happily until you hit retirement age, and then collect your pension for the remainder of your life, in happy retirement. Even IBM has moved to a cash-balance pension plan, instead of a fully funded pension plan. Jobs for life are a thing of the past. And relocation, when it happens, is generally a long term thing. IF jobs don't last as long as the relocation does, and there are no alternatives: no thank you.

  16. Joel on Remote Software by Marginal+Coward · · Score: 2

    I recently attended a talk by Joel Spolsky, of "Joel on Software" and "Stack Overflow" fame, who made exactly the same point as TFS. He said they were routinely hiring people to work remotely at Stack Overflow and using remote technology such as Skype in order to get the best and the brightest - presumably also at the best price, though he didn't actually say that. He suggested this as a future trend that companies were eventually going to adapt to.

    Ironically, he gave that talk at a company that concentrates as many engineers as possible in one location. Oh, and he gave his talk onsite, not via Skype. Go figure.

    1. Re:Joel on Remote Software by bondsbw · · Score: 1

      I don't think Joel likes TFS all that much. He's more into Mercurial/Kiln and Fogbugz.

      --
      All my liberal friends think I'm a conservative, all my conservative friends think I'm a liberal.
    2. Re:Joel on Remote Software by Anonymous Coward · · Score: 1

      I recently attended a talk by Joel Spolsky, of "Joel on Software" and "Stack Overflow" fame, who made exactly the same point as TFS. He said they were routinely hiring people to work remotely at Stack Overflow and using remote technology such as Skype in order to get the best and the brightest - presumably also at the best price, though he didn't actually say that. He suggested this as a future trend that companies were eventually going to adapt to.

      Ironically, he gave that talk at a company that concentrates as many engineers as possible in one location. Oh, and he gave his talk onsite, not via Skype. Go figure.

      Spolsky's such a huge tool that I would consider his advocacy as an argument against allowing remote work.

  17. Telecommute for the win, the future is now. by GoodNewsJimDotCom · · Score: 2

    Little guys like Indie video game companies can't afford studios. They make video games with an artist in one state, and a programmer in another state. The teams can get big, but they get successful software done. Telecommuting saves people tens of grand a year, and I'd take a job for 20-30 grand less a year if I could telecommute. That's the price of gas, time to commute and big time savings on housing. Meetings are even more productive than in face meetings because you both share computers with things like gotomeeting or join.me. You get communication via voice, and can share copy/paste buffers and write code together which is productive unlike face to face meetings where no actual code normally gets done.

    Don't criticize telecommuting if you haven't done it yet. I know it is different(and people are afraid of change), but it is superior in many ways.

    1. Re:Telecommute for the win, the future is now. by Shados · · Score: 1

      As that get widespread, the "big time savings on housing" will be a wash though. Salaries are so high in SF, Boston, NYC, etc, because you have to pay someone that much if you want them to move there, because of housing cost.

      And right now, if someone telecommute for one of those companies, salaries stay roughly the same, because that would be a dick move for it not to be.

      But companies located in low cost areas don't pay nearly as much.... once its the norm to telecommute, they'll pay you accordingly, since there won't be incentive to do otherwise. You already see it in the couple of telecommute-only companies. Since they have a very large pool of people to pick from, many in low cost areas, they don't need to raise the bid nearly as high to get people.

  18. Re:Management will support this kicking and scream by Shados · · Score: 1

    There's more to it than just that though. My current employer was founded by engineers...they know damn well how it goes, and they've been only hiring people they feel they can trust (break that trust and you're out damn quick...but that pretty much never happens. People are pretty honest).

    People work from home (legitimately) left and right, schedules are nearly random (some people come in at 3 pm and work until midnight as their normal schedule, others are in at 5 am and are out right for time for a late lunch...).

    We can still get face time when needed and collaborate in real time without friction of shitty tools though (everyone uses Slack or whatever when that's not needed). The inability to have ad-hoc face to face meetings without flying people over is just a deal breaker.

    To be able to scale the company, some groups are in separate offices at other locations, but they take care to keep engineering together, sales together, design together, etc. Having engineering and sales videoconference once a month isn't too bad, but having engineering people have to teleconference with each other whenever text isn't good enough would just slow things down.

    One day they'll hit the limit of how many they can realistically hire in one location for a given group, then things will change...but you probably want to avoid it if you can.

  19. I have a great gig... by djbckr · · Score: 1

    I was lucky enough to be hired by a company that lets me work remotely. I get paid what I expect/deserve, and I didn't have to move to San Francisco. I go there about 3~4 times a year just to get face-time with the people I work with. They like it because they don't have to find a space for me, and I like it because I didn't want to move to California.

  20. The problems of distance by Marginal+Coward · · Score: 4, Insightful

    I've had experience working with people remotely, and my experience has been that the problems scale with distance. Specifically, it's easiest to work with someone in your own office, a little harder to work with someone across the hall, harder still to work with someone across the country, and *quite* hard to work with someone across the ocean. By the time you get that far away, timezones become a major problem, and IT systems don't always work well.

    From a business point of view, you have to look at the cost versus the benefits. I once worked with a group of people from India who reportedly cost 1/4 of what we cost. But we did some metrics that showed we were 6x as productive, so we actually cost less overall than them. The main reason we were more productive was that our local group was highly experienced in the specialized technology we were developing, whereas the folks in India were brand new to it. Also, the folks in India ran into numerous network and server problems that slowed them down. Evidently, nobody in The Big Corporation realized that they needed to spend money on IT, since this experiment was supposed to be about "cost savings".

    Given time, the IT problems might have gotten ironed out, and the Indians might have developed the necessary experience. However, the India group had so much turnover that they never became experienced in that technology as a group. In contrast, we had some Indian folks who worked with us locally, stuck around (at least until they got their Green Cards), and were ultimately as productive as the rest of us.

    1. Re:The problems of distance by melchoir55 · · Score: 4, Insightful

      My best frontend developer is in Germany (I'm in the bay area). I spend about 2 hours a week interacting with him on a really busy week. 30 minutes to an hour normally. At the beginning of a project, I hand him a wireframe and we go over requirements. He asks me questions if anything is unclear. As the project continues, I check on how he's doing once a week. Sometimes I find he is mildly off course and I set him straight, but it is an uncommon occurrence. The stuff he delivers is mostly great, with a few bugs that usually end up getting ironed out the week after the turn in date.

      How do I achieve success with a worker on the other side of the planet?
      - I pay him very well. His wage ends up being about $65 usd per hour (which is high for a frontend developer).
      - I maintain a professional, but friendly relationship with him. He's a person, not my underling, and not a mere resource.
      - I made sure I know what he is good at and interested in. I give him tasks he is either good at or can/wants-to adapt to.
      - I don't engage him in communication unless doing so would be productive, though I do respond quickly if he wishes to initiate communication for any reason.

      This list should seem blindingly obvious to everyone reading this. "OF COURSE you do these things", you folks are saying. Well, I've found that although everyone agrees on the best methods to engage employees, very few people actually follow that course. Many corporations large and small appear to think there are shortcuts around building a strong employee. There are not. If you think there are, you're a bad manager.

  21. My own experience. by sls1j · · Score: 1

    I've worked from home for about 14 years, and my software has worked from home for at least a decade. We work well "together" and have been successful. The remote work place has some challenges, but we've adapted. When offering remote support to customers we all are better at it and have a good idea what can be understood and how to go about the work.

    One of the big advantages is having the space needed to really think free from distractions of coworkers. I'm definitely more productive.

    If your employees won't work unless they are watched you have a management problem not a worker problem. Your employees obviously don't feel the success of the company is to their own advantage. They obviously don't feel like your giving them enough, and I don't necessarily mean money. Does the job make them feel important? Do they feel like they are contributors? Are you as a manager undermining the good they have done?

    1. Re:My own experience. by serviscope_minor · · Score: 1

      If your employees won't work unless they are watched you have a management problem not a worker problem.

      That is very, very far from being universally true.

      I have a desk in a co-working space. Many of the people I talk to there share the same story: it's they liked coming into an office to work and found it hard to work at home, alone. These are almost all people who of course work for themselves.

      Many, many people simply don't work well at home. I've tried and I can't do it.

      --
      SJW n. One who posts facts.
  22. The REAL problem is the credentials barrier by Anonymous Coward · · Score: 2, Insightful

    The USA if full of talent that can't get employed because the cost of credentials in terms of time and money is much too high. Kids that excel in programming while in public school are told that after 12 years of a public education, they now need to slog through years of college and build a mountain of debt before they can apply their talent.

    But without credentials, SV won't even look at you -- and they are mostly legally prevented from doing so .

    Lots of foreign labor have the credentials, though, in part because their educational system is cheaper, less time consuming, and frankly less demanding of their students.

    If SV will take a little time and reach out to high schools, they'll find tons of talent.

    Of better, if they can create a credentialing body, they can more easily avoid legal pitfalls.

    1. Re:The REAL problem is the credentials barrier by Shados · · Score: 1

      Even Google will take you without a degree if you're good enough... I don't have a degree, and honestly no one has even looked in years. I also don't remember when's the last time I heard it come up during an interview review, and I've worked at a lot of places...

      I mean sure, if you don't have any experience, people will look for SOMETHING to gauge you to see if its worth their time to phone screen you. But you said "the USA is full of talent". If they're talented, actually talented, they got the skills SOMEWHERE, so they have some kind of experience to show, even if its just a github account.

      Then of course there's a lot of people who think they're good but aren't...

  23. Time zone: irrelevant. by fyngyrz · · Score: 1

    Especially remote working across 8 time zones (i.e. you only actually get to chat to each other for 1-2 hours a day)

    This is just the kind of thinking I was speaking of. It makes no sense whatsoever when you actually consider it, yet people throw it up as if it was a real thing you had to worry about.

    If someone hired me and was X time zones away, I would simply adjust my hours by X, or X +/- Y as they considered useful to them. This is no different than, for instance, having to work the night shift (or any other fixed shift, or a swing shift.)

    This is a factor that should be of absolutely no relevance unless the prospective employee actually refuses to work the required hours, in which case, I guess they didn't want the job anyway, and you're better off moving right along.

    --
    I've fallen off your lawn, and I can't get up.
  24. Yes by bjk002 · · Score: 3, Insightful

    " is "being stubborn on keeping a company culture that requires people to be physically co-located," as Mullenweg puts it, a big part of tech's 'talent shortage' problem?""

    Yes.

    --
    Opinion:=TMyOpinion.Create(Me);
  25. Re:No. Reciprocal loyalty is dead. by loufoque · · Score: 1

    I doubt you can really find a good job within a week.
    Finding a really good job takes months at best.

  26. Re:No. Reciprocal loyalty is dead. by phantomfive · · Score: 5, Insightful

    No. Reciprocal loyalty is dead.

    Exactly. Be loyal to people but never to corporations. The corporation will never be loyal back: it will lay you off as soon as it benefits the bottom line.

    --
    "First they came for the slanderers and i said nothing."
  27. Programming vs. copy-and-paste by jtara · · Score: 2

    No, 95% of great programmers are not in the U.S. But they ARE in high-educated, Western countries.

    We're talking about actual programmers, BTW, not copy-and-paste artists.

  28. Silicon Valley is overrated by Anonymous Coward · · Score: 1

    Why should I want a job in one of the most expensive places to live in the country, in a poor work environment, under leadership that thinks nothing of using people up and throwing them away? Remember, you are just an expense to be managed, interchangeable and easily replaceable. I did that for over 25 years and have finally had the strength to walk away from it and not look back.

    1. Re:Silicon Valley is overrated by gatkinso · · Score: 1

      Why do I suspect "strength to walk away" translates to "savings"?

      --
      I am very small, utmostly microscopic.
  29. Re:No. Reciprocal loyalty is dead. by gatkinso · · Score: 1

    One can definitely find a replacement tech job in a week. A replacement tech job they want/like/is satisfying....? That sometimes takes the better part of a career.

    --
    I am very small, utmostly microscopic.
  30. If 95% of the best programmers are not in the US.. by gatkinso · · Score: 1

    ...then why are virtually all of the most successful tech companies here?

    Yes, a few exist outside of the US. Not many.

    --
    I am very small, utmostly microscopic.
  31. But the US Benefits by Their Spending Here!!! by Baldrson · · Score: 2

    If all these immigrants are so beneficial to me, I want a citizen's dividend to prove it and I do _not_ want my citizenship's equity diluted by making "voting share holders" out of these immigrants.

    Oh, you can't provide that for me?

    Take your immigration propaganda and shove it.

  32. Re:If 95% of the best programmers are not in the U by m00sh · · Score: 1

    ...then why are virtually all of the most successful tech companies here?

    Yes, a few exist outside of the US. Not many.

    It's because we have been so far successful in getting the a large chunk of the 95% to move the US.

    But, new programmers are being minted everyday and if we don't get there here, they will start creating their own software companies in their own countries. It doesn't take long for a company to start with nothing and become one of the largest company in the world in a decade.

    I'm only half serious though. There are enough reasons why the next Google can or can't come from outside the US. Can we confidently say that the next Google will be an American company? Can we do anything about it or just sit and wait?

  33. Re:No. Reciprocal loyalty is dead. by tlambert · · Score: 1

    I doubt you can really find a good job within a week.
    Finding a really good job takes months at best.

    You can if you have standing offers. Many people have multiple standing offers, at least one of which would qualify as "good". How often do you get "hit on" by a recruiter? If it's once a week, chances are good they will have a job in inventory that's to your liking. If you just hang up on them when they call, rather than maintaining an amicable relationship, then yes, it can take you a while to find a job.

    You can also do it if you have the friends network that I mentioned in my first posting; put the word out you are looking, and you will likely get multiple offers. The quality of the offers will likely depend on the connectedness and quality of your friends, and whether or not they are connected in the domains where you want to work, but this is why you cultivate a network.

    Both of these bring me back to the original points of why you go into a tech Mecca, rather than going to Omaha: (1) Standing offers are generally "for someone in your geographic area", and (2) Your friends network's ability to help you out is dependent on connectivity to a large enough base of companies that cover some at which you'd want to work.

    But, yes: if you are in Omaha(*), it can take months, at best.

    (*) I picked Omaha more or less at random, so sorry if you are a tech company in Omaha trying to hire, it was not a personal grudge.

  34. Re:No. Reciprocal loyalty is dead. by loufoque · · Score: 1

    I get offers on a weekly basis, if not more, but finding a well-paid job in a domain you're interested in, close to your home, and that still leaves you enough free time to spend with your family is not that easy.

  35. Re:No. Reciprocal loyalty is dead. by cascadingstylesheet · · Score: 1

    If you work in Omaha Nebraska, you can walk away from a tech job you can't stand and have another job inside a week. At Pizza Hut.

    I'm talking about having a group of friends and acquaintances with whom you can maintain face to face contact, who are able to help you out in a job search, which simply doesn't exist, if you're looking for a tech job, but don't live in a tech Mecca.

    Huh. I must just be imagining that I live in a medium-sized metro area in flyover country (that nobody would think of as a "tech mecca")? Must be imagining that I've voluntarily changed jobs five times here, without more than a weekend between them. That for my most recent job I was hired (at a new company) by someone I had worked with two jobs ago. That this was over a period of years, that each job was better than the last.

    Because that's only possible in tech meccas, right?

    There's a strong bias to justify to yourself living in a high cost of living area.

  36. Re:If 95% of the best programmers are not in the U by laird · · Score: 1

    There are many successful tech companies outside the US. Heck, Intel would be nearly dead if it weren't for their Israeli R&D team and the (British) ARM chip. And SAP is German. Samsung, Foxcon, Hitachi, Sony, Panasonic, Toshiba, LG, Nokia, Arduino, ... they all do tech, and they're outside the US, right?

    Yes, there are tons of US tech companies. But don't forget that the rest of the world exists, and has exciting stuff going on, too!

  37. Yup by bmajik · · Score: 1

    I'm going on my 15th year at Microsoft. The first three were spent in Redmond. The rest have been at the office in Fargo, ND. For family reasons, I asked to be xferred to Fargo.

    These days, not only do I not want to work in Redmond, I would prefer to not regularly go to a company office at all. Last year, I moved to a farmstead that is a bit outside of town. I've been working from home irregularly -- a few days here and there. Now that I have a new boss who is in Redmond, he doesn't care if I'm a remote employee in a Fargo office or a remote employee in my basement. So, I expect to be doing quite a bit more WFH.

    It turns out that I am way more individually productive at completing tasks from home than I am when I am in the office.

    However, there are definite advantages to getting some face to face time with the people you regularly work with. But not every day.

    Every few months, Google, Netflix, Salesforce,etc will grab my linked in profile and ask if I'm interested. I tell them all the same thing - there is no condition under which I would move to the Bay Area. None at all. Furthermore, these companies are all based off of opensource software that was developed via distributed engineering - so what's their excuse to want to co-locate people into offices? Surely it isn't an engineering reason? Surely what they're building isn't more complicated than the linux kernel?

    When something happens to my MS job out here, I plan on taking a 50% pay cut when I find whatever is next. That's not ideal, but I'm not willing to move to a big urban area again. There are people who are competent software engineers that don't want to live in large cities, or who don't want to commute to an office even if they do live in a large city. We're affordable to hire, we incur no facilities costs, and we're appreciative and loyal. Stop overlooking us.

    Corporate culture is behind social and technical culture. Most of us interact daily with acquantances that live multiple timezones away. The reasons for forcing co-workers into the same building every day continue to shrink. It will be great when cube farms are levelled and other more interesting things are built in their place.

    --
    My opinions are my own, and do not necessarily represent those of my employer.
  38. I'm in this boat by Anonymous Coward · · Score: 1

    I get contacted probably 10 - 20 times per week to take work in California. I do not live in CA. My response every time I get contacted is that the opportunity sounds great, but I can't afford to live in CA. The salary raise they tout is nowhere near enough to cover the cost of living increase. I have suggested several times that I would be willing to work remotely and even commute every few weeks to still have the connection to the team and nobody is willing to do it. I even offered to make a little less than the CA co-workers because my costs to live are much less. Still a no go.

    Silicon valley can't complain about the worker shortage and not be flexible. Anybody that is willing to relocate to CA is a sucker because the costs of living outweigh any salary that could be offered.

  39. BS, just like TFA by s.petry · · Score: 2

    Nearly everyone I know in the Bay Area leaves for better pay, not "boredom" as you claim. The larger companies in the Bay area, and the elephant in the room I have yet to see discussed, were found guilty of illegally colluding to keep wages artificially low just a few months back. This impacted the wages of everyone in the bay area, like it or not (that is the nature of Capitalism). You can bet that there is still collusion, but people are going to be a lot more careful about their deals for a while. Those same companies for years have claimed "we need more H1Bs because nobody is qualified" as a way of further artificially depressing wages. Which brings up the 2nd elephant in the room, that a company not too long ago was found guilty of slavery abusing H1B workers.

    So now a few of those same companies are claiming "95% of the good programmers are not in the USA" and who really believes them?

    Stop and think about what it means to be a "good" programmer from your perspective, then from the egocentric pricks making these claims. I guarantee it's a completely different standard. To them, it's whether or not they get paid average or less in wages and how much hiring someone impacts their bonuses and income (which to us would be insanely excessive). For example: How well an employee can communicate is not in their measures, and in fact they don't want people that can communicate. How good is your team when there is poor communication?

    --

    -The wise argue that there are few absolutes, the fool argues that there are no probabilities.

  40. Mirrors by s.petry · · Score: 1

    There is a big problem tossing around the Dunning-Kruger effect, and that is "you" look guilty as hell. Philosophy is in essence logic, which is in essence programming. Not the same language of course, but a person that learned symbolic logic that can break down written language to measure truth can do it in any language they decide to learn.

    Computers are logical and programs are logical. A person with extensive training in Logic, as a PhD would have, does do exceptionally well.

    Blindly claiming "Dunning Kruger" when a person has at least 7 years of University knowledge is telling. Sure, I have met a couple I don't trust. At the same time, I have met countless people that don't know what Philosophy is (Academically speaking) I trust less. The latter always seems to claim "Philosophy is bad" in some way.

    --

    -The wise argue that there are few absolutes, the fool argues that there are no probabilities.

    1. Re:Mirrors by Pseudonym · · Score: 1

      Blindly claiming "Dunning Kruger" when a person has at least 7 years of University knowledge is telling.

      I had some high-profile examples in mind as I was writing that. Richard Dawkins is probably the clearest example of someone who is an undoubted world expert in one field (biology, and evolutionary biology specifically), who vastly overrates his competence in pretty much any other field.

      Philosophy is in essence logic [...]

      I'm going to say "no". Philosophy is, in essence, critical and systematic thinking. Its boundaries are fuzzy, but it is the primordial soup from which new fields of human endeavour form. These fields eventually graduate to be new faculties and departments of their own. Logic is one such field, but it's not the only one.

      So let me be more clear on this.

      I would not turn my nose up at anyone with a PhD in philosophy from a non-fake institution of higher learning. That person is very likely to be highly valuable. However, the context is hiring an engineer to implement and maintain industrial control systems. I don't know specifically what the job was, but do remember that SCADA systems are often the second line of defence against an industrial accident. I've been engineering for 20 years, and I consider myself unqualified to work on safety-critical systems.

      If all you knew about someone was that they had a PhD in philosophy and described themselves as a "self-taught Java guru", what are the chances that they have the appropriate knowledge and methodology (whether formally acquired or not) for this specific job?

      Does this guy have what it takes to learn the requisite knowledge? That seems likely; in fact, he probably has more aptitude for working in this area than most software engineering graduates. Has he acquired the knowledge during his "self-taught Java guru" training? That seems unlikely.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    2. Re:Mirrors by s.petry · · Score: 1

      Philosophy is in essence logic [...]

      I'm going to say "no". Philosophy is, in essence, critical and systematic thinking. Its boundaries are fuzzy, but it is the primordial soup from which new fields of human endeavour form. These fields eventually graduate to be new faculties and departments of their own. Logic is one such field, but it's not the only one.

      And you define critical thinking as different from logic? Well now, I guess Trig must not be math either.. because you know.. it's "trig" right? Good grief!

      If all you knew about someone was that they had a PhD in philosophy and described themselves as a "self-taught Java guru", what are the chances that they have the appropriate knowledge and methodology (whether formally acquired or not) for this specific job?

      Compared to who, the High School grad? I have much more confidence, but I'd question why the guy went into a shit language like Java. Joking aside, no matter what I would test their knowledge in person (meaning both candidates). The PhD is going to be able to grasp new concepts and see a big picture better than the guy with the high school diploma every time. Sometimes that is a good thing, other times not so much. The PhD is also going to be much better at communication.

      Point is, claiming someone can't be a good programmer because they have a PhD is pure idiocy. Worse than your claim that critical thinking is different from logic even.

      --

      -The wise argue that there are few absolutes, the fool argues that there are no probabilities.

    3. Re:Mirrors by Pseudonym · · Score: 1

      And you define critical thinking as different from logic?

      Uhm... yes.

      Logic is a framework for constructing individual theories which can then be used to model real-world situations. Critical thinking is a system and methodology for understanding and analysing arguments made by others, and to ensure that your own thoughts are clear and reasoned. These are obviously distinct areas, though they are not disjoint. And they are both "philosophy".

      The critical thinking subject which I did didn't touch on linear logic (for example) at all. Plus, a lot of it was analysing the semantics and pragmatics of language.

      Well now, I guess Trig must not be math either.. because you know.. it's "trig" right?

      Trigonometry isn't calculus, even though there are plenty of places where they touch. But they are both "mathematics".

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    4. Re:Mirrors by s.petry · · Score: 1

      And you define critical thinking as different from logic?

      Uhm... yes.

      I gave the example based on text books, and you still invent your own. Critical thinking requires knowledge of Logic, Logic is a part of Critical thought. Similarly, Math requires trig, at least beyond algebra.

      --

      -The wise argue that there are few absolutes, the fool argues that there are no probabilities.

  41. Marissa Meyer was right (for once) by nicoleb_x · · Score: 1

    Having people working remotely by themselves is not (currently) a great model. Software is produced by teams not individuals and teams really need to collaborate to be effective and the easier it is to collaborate the better the results. I'm sure you all read the recent report about open space offices? Until that trend ends you can expect that remote/cubed workers are not going to be in vogue.

    I do think that robotic avatars will eventually solve this problem, so if I was the Indian, Russian or whatever government I'd get cracking on this.

  42. Re:No. Reciprocal loyalty is dead. by tlambert · · Score: 1

    I've voluntarily changed jobs five times here, without more than a weekend between them.

    "Voluntarily" is disloyalty on your par, and generally has only the downtime you choose to have, since you tend to explore all your options, then pick up the new job before you leave the old job.

    What I was talking about was employment risk. Employment risk is the risk of your employer *leaving you in the lurch*, and what happens when that happens. In that case, it's typical that there are other people from the same company, and you are all looking for jobs at once.

    For example, I was working in Tucson, Arizona when the company basically ran out of money (the new CEO had spent all of the company's buffer on telephony acquisitions, because he thought that was the next big thing), and a company that had been operating for over a decade suddenly became insolvent. Suddenly, there were 400+ people looking for work in the same job market, with roughly comparable skill sets to their peers. Tucson is a limited tech job market. I was lucky, I had an existing network, and an industry reputation. Some of my peers were not so lucky.

    I didn't mention industry reputation before, because it's simply not possible for everyone to have one, and these people tend to have standing offers, even if it requires the company pay relocation for the person to take advantage of them. They're kind of irrelevant to the idea of Joe Shmoe, techie, who answers a billboard ad and moves to Omaha, only to be competing with 10 former coworkers for the same *small* set of jobs within a largely non-tech region.

    So I will claim non-applicability of your case, based on (1) voluntarily means you avoided the "flash crowd" problem, and (2) You demonstrated use of a small network, and (3) it was not a case of company disloyalty to the worker.

  43. Re:No. Reciprocal loyalty is dead. by tlambert · · Score: 1

    This seems heavily biased to the US... or maybe low-demand skill sets.

    I jump jobs regularly in AU as a contractor, I'm rarely down for more than a week, with no help from anyone (not even a recruitment agent), traveling all over AU 2-3 times a year where jobs take me.

    Again, this is voluntary on your part, not the company flooding the job market with people. And yes, contracting is not the same as having a full time job, and requires the ability to sell yourself. The original article was not about sales skills, it was about "Hey! Come move out to the boonies! The water's fine!", when in fact the water is *not* fine for stereotypical job seekers in stereotypical jobs.

  44. Tax them by NewYork · · Score: 1

    Tell Obama regime to impose tax on Company revenues, not profits.
    http://wh.gov/iYIFb

  45. Re:Let's see how good you are... apk by Khyber · · Score: 1

    HOSTs won't even block Camfrog Ads. They figured out a way around it AND figured out a way to get their ad network to prompt you to install stuff.

    Which means your entire HOSTs file is bullshit, now!

    --
    Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
  46. Re:WRONG... apk by Khyber · · Score: 1

    "So its useless in blocking botnets, malscripted sites, phish/spam sources & trackers to, & speeding you up via hardcodes hosts have (which also secure you vs. DNS issues too of ALL kinds)"

    Yea, your HOSTS file will *CERTAINLY* protect against DNS poisoning.

    What a fucking tool.

    --
    Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
  47. Re:WRONG... apk by Khyber · · Score: 1

    " I'd LIKE to KNOW how you know that, if you don't use hosts?"

    Easy - we had this conversation in the tech room on Camfrog, where actual tech people can talk without idiots like you spamming your useles solutions all over the place. Guess what? When you ingrain parts of the service so every part has contact capability with ad networks, if you block them all, you block Camfrog from working in its entirety.

    Your HOSTS file is useless. All that whitespace taking up room and making websites unusable. Can be effectively and easily bypassed, subject to DNS poisoning, modern browsers won't pay attention to it (Opera, for example) unless you root your phone you can't access HOSTS, etc.

    Guess what works far better than a HOSTS file?

    Being competent enough to run your own fucking DNS server.

    Which you obviously aren't competent enough to do.

    --
    Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
  48. Re:Aha: Khyber ADMITS it & fails... apk by Khyber · · Score: 1

    "Yes: Avoiding DNS via fav. site hardcodes protects users vs. DNS issues (via fav site hardcodes). For once, you're right - however, ONLY BY AGREEING WITH 1 OF MY TOTALLY VALID POINTS!"

    You totally miss sarcasm. No wonder you're so retarded and keep on about a HOSTS file that won't protect against DNS poisoning (If your hard-coded IP/DNS entry gets fucked, you're fucked, stupid.)

    "P.S.=> Issuing downmods vs. facts & truths YOU FUCKED UP ON"

    I haven't had mod points in a couple of months, so once again, you're full of shit and know nothing.

    --
    Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
  49. Re:LMAO: More Khyber fails... apk by Khyber · · Score: 1

    "Downmodding my posts not proving 'em wrong = you fail Khyber!"

    Considering I haven't had mod points in a couple of months, you're obviously full of shit.

    Meanwhile...

    "where you STILL refuse to show me these 'camfrog' ads, which are easy to stop..)"

    Install the program yourself, asshole. Since you won't, you're obviously scared that you'll find out just how WRONG you are.

    So yes, HOSTS files are useless. Note how you CONVENIENTLY avoid the fact I can list stuff that bypasses HOSTS (like Opera) without any issues, making your HOSTS file pointless and useless in the first place. Let alone all the attacks that target (and bypass) HOSTS all day.

    But no comment towards that, eh loser? Given proof, you ignore it and keep attacking on your other futile points.

    You're so wrong. You're a running joke at google. Whenever the Helpouts service has a minor issue, we say "It's been APK'd."

    When GOOGLE laughs at your ass, you should just give the fuck up.

    --
    Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
  50. Polite discussion is possible by OffTheWallSoccer · · Score: 1

    Hey apk,

    Just because people don't like something you posted and thus mod it down, doesn't mean that Khyber or anyone else in the discussion did the down-modding. You have no way to know who the moderators were, and accusing random people of doing so just makes you come off as an asshole.

    I know this is a long shot, but why not make your point(s) without making personal attacks? If you want to be taken seriously, then discuss things rationally *and* politely. If you are only here to attack in hopes of "destroying" people, then you are clearly asking moderators to jump all over you.

  51. Re:Everyone knows barb sockpuppets by OffTheWallSoccer · · Score: 1

    Apk,

    My comment was about the content of your posts, and has nothing to do with your preconceived (and incorrect) notion that I am defending anyone.

    I come here to read interesting discussions. Posts (from anyone) containing attacks and finger pointing are boring and hurt everyone's experience.

    So again let me ask you:

    why not make your point(s) without making personal attacks?

    And please don't respond with "so and so was mean to me, so I needed to destroy them". You can rise above someone else's childish comment, if you so choose. Just ignore their comment and move on. It isn't worth your time.

  52. Re:If you're going to "defend" Barb by OffTheWallSoccer · · Score: 1

    Take a shot at this challenge of mine ...http://slashdot.org/comments.p... instead - Go on: Go for it...

    Been there, done that. You and I previously discussed the Ad Muncher software that I have been using for many years, and you agreed it was a good solution (especially compared to browser plugins). Is hosts file manipulation another solution? Sure, probably. But I don't care, since I already have a good solution.

    In regards to my question to you, instead of repeating myself, I will just refer you to our other conversation.