Slashdot Mirror


Dropcam CEO's Beef With Brogramming and Free Dinners

waderoush writes "Plenty of technology companies serve free breakfast, lunch, and dinner to their employees, but Dropcam CEO Greg Duffy says that's a form of mind control designed to get people to to work late. To keep employees happy, Duffy says, it's better to make them go home to their families for dinner. Some other suggestions from the San Francisco video monitoring startup: don't fill your engineering department with young, single, childless males (aka brogrammers). Keep your business model simple by making actual stuff that you can sell for a profit. And don't hire assholes. Why pay attention to Duffy's advice? Because Dropcam has a 100 percent employee retention rate — no one who has joined the 4-year-old company has ever left."

400 comments

  1. Hm. by Anonymous Coward · · Score: 4, Insightful

    I'd agree with dinner, and maybe breakfast to an extent.
    But lunch? It's just a time saver to have it at work.
    If I eat while working and don't take the time off for lunch, I can leave sooner.

    1. Re:Hm. by Penguinisto · · Score: 5, Insightful

      Yes and no.

      Sometimes you need to get off your ass and walk around once in awhile. Focus your eyes on something that doesn't involve pixels or a desk. Lunchtime is perfect for that. Gives you a chance to get out, walk around, notice things, talk to folks in a groups, and in a setting where you're not all eyeballing a PowerPoint presentation.

      I get the leave-earlier paradigm, but honestly? 8-10 straight hours in front a screen makes Johnny a very unhappy soul. Break that shit up.

      --
      Quo usque tandem abutere, Nimbus, patientia nostra?
    2. Re:Hm. by dragon-file · · Score: 4, Funny

      Wait... people do that sort of thing? I mean the walking and the looking at things that aren't pixels?....

      --
      Whenever a player quits EVE to go play WoW, the Average IQ of both games increase.
    3. Re:Hm. by MindStalker · · Score: 3, Insightful

      You can provide lunch and this as well. Many companies you see people packing their lunch and eating at the desk in order to get lunch over quickly so they can leave early. If you provide lunch in other area but insist they don't bring their lunch to their desk, it would be a positive.

    4. Re:Hm. by Wookact · · Score: 3, Insightful

      I get an hour for lunch. I may spend the entire lunch doing what ever I choose. Or I can eat at my desk and field calls for that hour, and I am allowed to leave 30 minutes early. Well on some days, unless things are running late, or I am the last one here and we need coverage till 5:30, or a million other things that could keep me here late. Lotsa ways to throw a wrench in the leave early plan.

      I enjoy my lunch hour.

    5. Re:Hm. by egcagrac0 · · Score: 5, Informative

      Normal people do, yes.

      A lot of tech workers don't act like normal people, however.

    6. Re:Hm. by Anonymous Coward · · Score: 0

      That's what smoke breaks are for.

    7. Re:Hm. by Anonymous Coward · · Score: 3, Insightful

      You can provide lunch and this as well. Many companies you see people packing their lunch and eating at the desk in order to get lunch over quickly so they can leave early. If you provide lunch in other area but insist they don't bring their lunch to their desk, it would be a positive.

      Yes, being micromanaged by control freaks who want to tell me how and where I may eat is so exquisitely positive and definitely boosts morale.

      Here's a better idea: if the employee is productive and does good work, find something that actually IS broken and fix that instead.

    8. Re:Hm. by trev.norris · · Score: 2

      My eyes can handle it. My ass can't.

    9. Re:Hm. by alphax45 · · Score: 1

      Oh how I wish I had mod points for you :)

      --
      K Man
    10. Re:Hm. by jittles · · Score: 1

      Yes and no.

      Sometimes you need to get off your ass and walk around once in awhile. Focus your eyes on something that doesn't involve pixels or a desk. Lunchtime is perfect for that. Gives you a chance to get out, walk around, notice things, talk to folks in a groups, and in a setting where you're not all eyeballing a PowerPoint presentation.

      I get the leave-earlier paradigm, but honestly? 8-10 straight hours in front a screen makes Johnny a very unhappy soul. Break that shit up.

      I like to eat lunch while I work. But I also like to go for a walk outside after I am done eating. I might do a 10-15 minute walk on average and 30 minutes if its an exceptionally nice day. But I also walk before and after I work, as well.

    11. Re:Hm. by Anonymous Coward · · Score: 0

      I'd personally offer them, but not feel like having to force them in to wanting to stay.
      I'd make the eating place simple and clinical looking at best, so even though it might get some attention, it may turn off some people.
      Guess it just depends on those who you hire. Some like nice clean spaces, some prefer traditional wooden designs, some metal, etc.

      But equally I would also run the café at a profit. It would be on the ground floor with public access section from the street as well.
      Why not have the best of both worlds? I guess that would you could have it look all fancy.
      The meal would essentially be free since it would be supported by the public who come in to the café, not so much a direct main product. Secondary profit, if you will.
      Free family meals as well, bring the family to the company, make it all fancy and stuff.
      Who wouldn't love that?

    12. Re:Hm. by Anonymous Coward · · Score: 0

      >... Lotsa ways to throw a wrench in the leave early plan...

      Throw a wench in, and there goes my leave-early plan.

    13. Re:Hm. by Anonymous Coward · · Score: 0

      I do :)

      AC for obvious reasons.

    14. Re:Hm. by Anonymous Coward · · Score: 1

      Or a deal breaker. I eat lunch at my desk so that I can finish half an hour earlier. That lets me beat the peak traffic flows, which can shave as much as another half an hour off my drive home. A company that insisted I go have lunch somewhere else would effectively be insisting that I spend more time in traffic. I don't think that I'd work for such a company.

    15. Re:Hm. by Anonymous Coward · · Score: 0

      Oh? I worked for a place where it was salary, plus paid overtime. 36 hour week (but you worked 8 hours and then got every second Friday off). It was still a wonderful thing to get up at lunch and get out for a walk. And it typically was a brown bag lunch. No other perks. The hardware was old, the office was hot in summer, freezing in winter. If it weren't so boring, I would still be there (but the system had been installed 10 years prior, so it was maintenance only, no projects, and little contact with the outside world. 3 years was long enough to pay off student loans and car payments. Tech people like to have a life too, and they didn't have any interest in changing things.

    16. Re:Hm. by grumpyman · · Score: 1

      One of the architect I worked with has odd hours, just like any other I guess: 11am-3pm and then 10pm-3am : )

    17. Re:Hm. by gbjbaanb · · Score: 1

      ...which is probably the single biggest problem with this industry...

    18. Re:Hm. by gbjbaanb · · Score: 1

      lunch - sure, but in a staff canteen where you can talk with other people and generally take a break from whatever you were doing and let your brain relax enough to let you do it better when you get back to work.

      I'd also recommend a sweet trolley in the afternoon, but that's mainly because I just like cake.

    19. Re:Hm. by Anonymous Coward · · Score: 0

      I was a programmer many, many years ago. We worked ten or twelve hour days because that's the way that we were wired. A problem left resolved simply festers and keeps you from sleeping. Of course the girls in the shop didn't see life that way and left promptly at five.

    20. Re:Hm. by Seumas · · Score: 1

      I don't agree with any of them. Making work life an enjoyable place and taking care of an employee's needs is more "being an awesome employer" and less "mind control".

      If you really want to go home at the end of the day and/or eat with other people, go do that. Some people enjoy working. Some people enjoy putting in the long hours. If you can make it so they don't have to leave the office, drive around go find a place to eat and waste their whole evening, then that's fantastic.

      I mean, what's next - "child care at work is mind control"? How about "bathrooms at work are mind control"?

    21. Re:Hm. by Grishnakh · · Score: 2

      You guys seem to be missing another big reason to bring a lunch to work and eat it there: money. Eating out at a local restaurant is expensive, whereas I can bring a lunch in, and only pay $1-5, depending on the ingredients or it it's a microwave meal. You're not going to get a good meal at a local restaurant for that. And the quality will probably be bad too.

    22. Re:Hm. by antdude · · Score: 1

      I am abnormal. :P

      --
      Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
    23. Re:Hm. by Anonymous Coward · · Score: 0

      How about you DON'T EAT where I try to work, you fucking asshole. Read up on flow, how that works, and then let go of your ego. Kthxbye.

    24. Re:Hm. by Geeky · · Score: 2

      Coming late to this, but drinks are one thing. Food at the desk is messy, and potentially smelly. I don't want to sit next to someone having a microwave curry, or some fish abomination, and stinking the office out. Not allowing you to eat at your desk isn't micromanaging you - it's putting a rule in place to stop inconsiderate bastards pissing off their colleagues (and sometimes nauseating them). Rather than say "no smelly food" and leave it open to argument and accusations, it's easier and fairer to just provide a separate area to eat.

      --
      Sigs are so 1990s. No way would I be seen dead with one.
    25. Re:Hm. by Anonymous Coward · · Score: 0

      visit http://footballworld2013.blogspot.com

    26. Re:Hm. by KingBenny · · Score: 1

      at the risk of repeating you, yup, in any kind of work based on set hours, the option of skipping lunch and going home thirty minutes or an hour earlier i have always deemed most attractive. It's virtually non-existent here as far as i'm aware and ofcourse i never had the honour of being googles or spacex's leading programmer (i dont think i will ever be either) which might bring with it a different point of view

      --
      Free speech was meant to be free for all... how can anyone grow up in a nanny state ?
    27. Re:Hm. by RockDoctor · · Score: 1

      Sometimes you need to get off your ass and walk around once in awhile. Focus your eyes on something that doesn't involve pixels or a desk. Lunchtime is perfect for that.

      TFS and the parent didn't talk about eating lunch at your desk ; they were talking about having lunch in the building or on site.

      I don't know what it's like where you work, but most places I've ever worked at have strongly encouraged (or "required", as in "Verbal Warning, then Written Warning if you don't comply.") to go to a separate break room to eat. Some others provide a (paid for, if subsidised) canteen on site.

      People having to leave the site to go and get a meal is a really big time waster. Particularly if the restaurant or whatever has a bar.

      On which point, lunch time looms ; leave the desk and 6 decks down to the Mess, on the deck level between the engine rooms and the accommodation levels, to manage noise levels for those off-shift.

      --
      Birds are not dinosaur descendants;birds are dinosaurs, for all useful meanings of "birds", "are" and "dinosaurs"
    28. Re:Hm. by Anonymous Coward · · Score: 0

      Yes, yes they do. In fact, I work at M$ and the grounds here are beautifully landscaped with a man made creek and small pond and water falls running through the campus I work at (redwest in Redmond, WA). I work in a big room around a lot of people and I try to just get out and walk around the grounds as often as I can get away with and it really is helpful.

  2. What about Foosball ? by Anonymous Coward · · Score: 0

    Whats his position on Foosball ? No Foosball, no work, seriously.

    1. Re:What about Foosball ? by Dogtanian · · Score: 2, Insightful

      Whats his position on Foosball ? No Foosball, no work, seriously.

      1999 called, they want their overused dotcom-era fads back. (*) Seriously, at this point, a foosball table is probably a negative sign, the cliched, almost obligatory easy-choice symbol a company would choose if they wanted to make themselves appear a (superficially) fun and exciting place to gullible young programmers.

      (*) Then again, the 1990s probably want their "[year] called, they want their [subject] back" cliche back, but they're not getting it :-P

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
    2. Re:What about Foosball ? by SkimTony · · Score: 2

      Did you warn them? You didn't?!

      http://xkcd.com/875/

    3. Re:What about Foosball ? by OakDragon · · Score: 1

      Your severance package is a roll of stock options, and all the copper wiring you can tear out of the walls.

    4. Re:What about Foosball ? by bickerdyke · · Score: 1

      the cliched, almost obligatory easy-choice symbol a company would choose if they wanted to make themselves appear a (superficially) fun and exciting place to gullible young programmers.

      Hmmm... We obviously work in the same company....

      --
      bickerdyke
    5. Re:What about Foosball ? by tgeller · · Score: 1

      I'm guessing you don't live in Europe. The foosball table at a Paris client of mine is a *necessity*, as is the espresso machine.

      By the way, they call it "babyfoot". Isn't that adorable?

      --
      Tom Geller
    6. Re:What about Foosball ? by Seumas · · Score: 2

      How is at-work entertainment a fad? At Netscape, we had foosball, ping-pong, pool, and arcade machines. It builds camaraderie and is a great way to blow off some stress when you need to clear your mind for ten minutes.

      Seriously, I just don't get what's with the Slashdot crowd, half the time. It's like they just want to hate what they do for a living so much and hate their work environment so much that when the opportunity to enjoy both comes along, they have to attack it with one ridiculous mentality or another.

      The next best thing to loving what you do for a living is at least loving the environment you do it in. By some of the comments, here, you'd think everyone wanted to work in a coal mine and have people whipping them.

    7. Re:What about Foosball ? by Dogtanian · · Score: 1

      How is at-work entertainment a fad? At Netscape, we had foosball, ping-pong, pool, and arcade machines. It builds camaraderie and is a great way to blow off some stress when you need to clear your mind for ten minutes.

      Go back and read what I said. I didn't say "at work" entertainment was a fad.

      It was *specifically* (and clearly) a criticism of the overuse of foosball as the lazy man/company's superficial choice of showing what a "fun" place they were to work at (i.e. it wasn't even really a criticism of foosball in itself).

      It's become a cliche since the dotcom era (which, I assume, is the time you worked at Netscape.) Yeah, we get it- the fortysomething guy in charge wanted to make this a "cooler" place to work, so he got his secretary to buy a foosball machine and paint the walls in bright, funky (*) colours. Bingo, we're cool- end of story. Also, I hear that "Friends" is popular with young people!

      Is foosball really *that* blooming great?!

      (*) To paraphrase Alexei Sayle, anyone who uses the word "funky" that isn't in the music industry is a right ****! :-)

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
  3. But...Agile teaches us... by engineerErrant · · Score: 0

    ...that we shouldn't want things like identities, families, and lives. It is a joy for us to be interchangeable work-bots. Dissention must be expunged so that we can be assimilated. Obedience is happiness!

    1. Re:But...Agile teaches us... by Jane+Q.+Public · · Score: 5, Informative

      "...that we shouldn't want things like identities, families, and lives. It is a joy for us to be interchangeable work-bots. Dissention must be expunged so that we can be assimilated. Obedience is happiness!"

      "Agile" does nothing of the sort. If that's how you're doing Agile, you're doing it wrong.

    2. Re: But...Agile teaches us... by Anonymous Coward · · Score: 5, Funny

      Isn't it a crucial part of Agile to tell others they are doing Agile wrong? :)

    3. Re:But...Agile teaches us... by Anonymous Coward · · Score: 0

      I see this sort of comment a lot, but I think it's important to note that this comes close to sounding like a "no true scotsman" fallacy. If the net effect of agile were that most places that practice it in some form end up like he is describing, does it really matter what the intention is? At best, it would mean that agile is helpless to solve the problems that exist in all of those workplaces.

    4. Re:But...Agile teaches us... by Anonymous Coward · · Score: 0

      That is not 'agile'. Agile is about consistency (you know, knowing people work 8-5 and have a family). If you are working to a deadline then you are not being agile. It is about knowing what you CAN do in the next 2-3 weeks with a fixed input. It is not about what you are going to do.

      I have seen so many abuses of agile its scary. The truly scary is it is from the same group of people who claim to be it. Current flavor is trying to cram it back into waterfall. "we want the product on july 20 and these 300 features, but use the agile tools to create your whole roadmap for the next 4 months".

      Some people have used agile as an excuse to be even more pedantic about schedules.

    5. Re:But...Agile teaches us... by obarel · · Score: 4, Insightful

      The one consistent thing about Agile: "you're doing it wrong". I have never seen a different answer to any complaint about Agile.

    6. Re:But...Agile teaches us... by PmanAce · · Score: 1

      All agile does is to make the client more involved in the shorten development cycle, the work more accountable (as in changes and implementations are done earlier), and the team members better team players. Agile has nothing to do with workplace problems.

      --
      Tired of my customary (Score:1)
    7. Re:But...Agile teaches us... by AuMatar · · Score: 3, Interesting

      No, those are things that agile *claims* to do. Whether it does that, what else it does, and how well it actually does those things varies greatly. "Agile" in my experience is usually just a buzzword meaning iterative development of any sort.

      --
      I still have more fans than freaks. WTF is wrong with you people?
    8. Re:But...Agile teaches us... by Colonel+Korn · · Score: 4, Insightful

      No, those are things that agile *claims* to do. Whether it does that, what else it does, and how well it actually does those things varies greatly. "Agile" in my experience is usually just a buzzword meaning iterative development of any sort.

      This is a pretty good little tangential comment thread. IANAPC (professional coder), but I'm quite familiar with professional methods with capitalized names that use the no true Scotsman fallacy to claim that every unsuccessful project was simply one that didn't correctly follow the method's instructions. On the other hand, any successful project was necessarily successful because of the Capitalized Method and the only way to quantify the value added by this method is to claim that the profit generated by the entire project is 100% due to the method's efficacy, of course.

      --
      "I zero-index my hamsters" - Willtor (147206)
    9. Re:But...Agile teaches us... by lgw · · Score: 4, Insightful

      "Agile" in my experience is usually just a buzzword meaning iterative development of any sort.

      But that's what agile really is. If you're really doing iterative development (getting to shippable every so often, not merely calling N weeks of coding "an iteration") then you're doing Agile.

      Don't confuse "Agile" with products cooked up by Agile consulting companies in order to have something to sell, like scrum and eXtremeProgramming.

      Agile is 4 ideas:
      * Individuals and interactions over processes and tools
      * Working software over comprehensive documentation
      * Customer collaboration over contract negotiation
      * Responding to change over following a plan

      There's a bunch of buzzwordism and scams and generally bad news sold as Agile, and all the BS has (perhaps rightfully) given Agile a bad name, but those 4 ideas are good ones.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    10. Re:But...Agile teaches us... by Anonymous Coward · · Score: 0

      That's because Agile is seen by middle and upper management as a silver bullet, never once realizing that they're delegating/ceding a goodly portion of their "authority" to the Engineers underneath them on the org chart. The bean counters, PLMs, project managers, and upper management, they oftentimes can't wrap their head around the concept of worrying about what can realistically be done in 2-4 weeks; they're too wrapped up in "aggressive" (Translation: Insane, utterly out of touch with reality...) schedules with explicit deadlines that have no correlation with reality- and you "HAVE TO GET THEM DONE THEN, WHATEVER IT TAKES" (Sigh...). They delude themselves that they can jam this through with a waterfall approach because that was what they were often taught in their MBA classes (nothing wrong with an MBA in and of itself, but it's hubris beyond words to think that you can actuall manage something you've no concept of otherwise in most cases...) and it's what "works" (not...).

    11. Re: But...Agile teaches us... by TheMathemagician · · Score: 1

      There's more to it than that?

    12. Re:But...Agile teaches us... by Anonymous Coward · · Score: 2, Insightful

      All agile does is to make the client more involved in the shorten development cycle, the work more accountable (as in changes and implementations are done earlier), and the team members better team players. Agile has nothing to do with workplace problems.

      As a veteran of TQM, ISO9000, XP, and fuck-knows-what in between, allow me to translate: All agile does is to make us jump more frantically whenever the client farts, get bitched out at for not having it fixed yesterday (as in fuck quality, just slap something together so you don't get reamed at the standup tomorrow morning), and the team members turn into their own slave drivers so that management doesn't have to take the heat for a Bataan Death March.

      (You're right in that Agile has nothing to do with workplace problems. It's just another way of not fixing them while looking good on a resume.)

    13. Re:But...Agile teaches us... by TWiTfan · · Score: 1

      You're ALL doing programming all wrong!! Just ask this guy.

      --
      The cow says "Moo." The dog says "Woof." The Timothy says "Thanks, valued customer. We appreciate your input."
    14. Re:But...Agile teaches us... by Anonymous Coward · · Score: 0

      Agile can't fail, you can only fail Agile...

    15. Re:But...Agile teaches us... by Xphile101361 · · Score: 1

      To me, that makes sense.
      The purpose of being "agile" is to be able to change things. If you have to complain and bitch on forums about things not working, then you obviously aren't getting feedback from those evolved and changing things to make them work.

    16. Re:But...Agile teaches us... by ebno-10db · · Score: 3, Insightful

      Agile is 4 ideas ...

      Congratulations, you've passed the Rorschach test! For bonus points, tell us what the "cloud" really is.

      BTW, I not only like your ideas, I've followed them as much as possible since long before "Agile" was a buzzword. But while decrying buzzwordism, you've overlooked that "Agile" (capitalized? seriously?) is itself just a buzzword.

    17. Re:But...Agile teaches us... by AuMatar · · Score: 2

      None of which have anything to do with a majority of agile I've seen

      *Individuals.. blah blah blah

      Yeah, I can't even tell you what this means. I doubt anyone else can either. Its marketing drivel that sounds moderately impressive, but has no real effect on how any company does anything.

      *working software over documentation

      Even when doing agile the absolute most effective companies I've seen have lots of documentation. Those that didn't either had 1 or 2 amazing developers who were the documentation (have a problem? Ask Gabe), or they failed miserably.

      *Customer collaboration blah blah blah

      Yeah- I've worked at multiple companies doing agile. Never talked to a customer. Wouldn't want to- we hire technical PMs for a reason. My company wouldn't want me to either- I'm too blunt and too honest.

      *Responding to change

      Everyone responds to change. And the general response by most agile places is the same as in non-agile- try to save room later in the schedule to meet the final release date you want for feature X. Because regardless of all the hand waving, there's still always a roadmap where you have features planned out for the next X quarters.

      Here's what agile actually means in industry- that there's going to be some attempt at organizing work into X week batches. That's it. Do that, and they consider it agile.

      --
      I still have more fans than freaks. WTF is wrong with you people?
    18. Re:But...Agile teaches us... by 140Mandak262Jamuna · · Score: 2

      . If that's how you're doing Agile, you're doing it wrong.

      At this point Agile has assume mythical qualities. Any time anything fails to work as promised by Agile, the implementation gets the blame, not Agile. They keep parroting the same thing. "if it does not work, you are doing agile wrong". You could postulate an imaginary waterfall organization, staffed with mythical programmers who do waterfall right. Then I could also say, "if it does not work, you are not doing waterfall right".

      We have agile. We have agile tools. We have vendors selling agile management tools to our company making oodles of money. And you ask the agile tool vendor to implement something, suddenly it is going to take 18 months and two release cycles. They are agile, they sell agile tools, they should know how to do agile, and I ask for something simple like, "I want to be able to add/delete people to the notification list of user stories. There is no need to assume, there is going to be only one customer proxy or just one person monitoring progress. So when will I be able to add a notification field and add email ids to it?" 18 months and two releases.

      The defect reports come from the field via Siebel database, and some script converts it to rally. In the process it fumbles the name of the submitter and the stupid script becomes the submitter. There is no lookup table to go from Siebel ticket number of Rally defect number or vice versa. Hey, vaunted rally tool vendor, when can you fix it? 18 months and two releases. This is already 18 months and two releases gone, and there is no solution in sight.

      Rally is snake oil. It promises to deliver skycastles to addled top management which thinks building software is like toasting bread in Quiznos or building a car in the assembly line.

      There are problems with waterfall. There is an entirely different set of problems with agile and rally. Agile is not going to make your process more efficient, or your software higher quality.

      Now is your time to come in and say, "Rally is not agile" "You are doing agile wrong" completely ignoring the point there is no documented case of agile working better than waterfall given the same resources and goals.

      --
      sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
    19. Re:But...Agile teaches us... by twisted_pare · · Score: 1

      Precisely. I went from working heroic hours to 9-5 once we really were Agile. Most of those long hours in the past could be traced back to poor planning and management acquiescing to last minute customer requirement changes. Once you accept that you were doing Waterfall wrong and want to fix it, life can be much better.

      --
      HTFU
    20. Re:But...Agile teaches us... by FuegoFuerte · · Score: 2

      If only I had mod points... Agile is another buzzword for management to hide behind and another way for them to pin their personal failures on the people who work for them. Hooray.

      Corporate America sucks.

    21. Re:But...Agile teaches us... by lgw · · Score: 2

      Agile has been around for quite some time now - certainly before the inanity of extreme programming and long before scrum. But giving something a buzzwordy name helps sell it to management. It doesn't matter how good your ideas are without management buy-In.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    22. Re: But...Agile teaches us... by Anonymous Coward · · Score: 1

      Yes. You also spew jargon that is specific to Agile but means things you didn't have a need for a word for before. Like "backlog", "sprint", and "scrum".

      And oh yeah, now they're managing operations teams with Agile. Seriously?

    23. Re:But...Agile teaches us... by lgw · · Score: 0

      Your hostility has thwarted your understanding I fear. The basic ideas are, less tersely:

      * Software is written by people, not processes. The goal is to ship software, not paperwork.

      * If you spend 6 months writing design docs before writing a line of code, you end up throwing away half of that work because the market changes. Vision statements and requirements docs and design docs are tools that server the purpose of shipping code the customer wants to use, not ends in themselves.

      * Your PMs are your customers, if you're not consulting. If your release ends with a screaming match over "You didn't give me what I wanted! No - we gave you what you asked for: see, it's written right here!" your doing it wrong. If you have that conversation every couple of week, since the customer won't know what he really wants till he see what he asked for, you're doing it right.

      * There are very much shops that work to deliver exactly to the contract agreed on with the customer (internal or external) and build all sorts of safeguards around "change control". The alternative is to work on what's seen as most important this month, and assume all work scheduled several months off will likely have its requirements change before you even get to it, so don't bother with throw-away work for that stuff.

      I suspect none of those seem like shocking or new ideas to you? Guess what - they're shocking and new ideas to a lot of middle management, and very objectionable to people who's only skill is contract negotiation and process management.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    24. Re:But...Agile teaches us... by tnk1 · · Score: 2

      Even when doing agile the absolute most effective companies I've seen have lots of documentation. Those that didn't either had 1 or 2 amazing developers who were the documentation (have a problem? Ask Gabe), or they failed miserably.

      I have to agree. The one thing I unconditionally disagree with Agile on is their attitude towards documentation. I agree that this may speed the process of coding... maybe... but it makes long term support a disaster. Code is not documentation, even well formatted and commented (which is infrequent to begin with). Some coders may be able to translate on the fly, but even then, it doesn't explain very well the requirements behind the code or the model being used.

      In short, it is coders and architects surrendering to product owners who want their stuff "fast". And as such, I understand that they want features out the door fast to capitalize on trends or whatever, but if the code attains any sort of age, it becomes a nightmare.

      If anything, documentation proves that the developer actually understands what they wrote, as opposed to merely looking for validation by it compiling and then seeing it do (mostly) was it is expected to do on the surface. It's great for new features quickly, but I've seen there is a tendency for much Agile-generated code to limp along until it is completely re-written later. Or as I'd call it, TP code, although ultimately I might hesitate to even wipe my ass with it.

    25. Re:But...Agile teaches us... by obarel · · Score: 2

      That's one possibility. Another is that whatever is supposed to be The One True Agile (tm) requires certain pre-conditions that aren't always met.

      I could say "don't blame the single-pass waterfall process - if it failed for you, then you're doing it wrong". In some (rare) cases, single-pass waterfall is exactly right - a single programmer implementing a rigid specification (for example writing an H.264 decoder). But that's a pre-condition. It won't always fail and it won't always work, just like "Agile" or any other "methodology".

      The truth is that there's no silver bullet. Every set of guidelines also includes a set of conditions (implicit or explicit). For example, most software development processes assume that the programmers involved are not all back-stabbing psychos. But even that's not always the case. Blaming reality for the failure of a process is the wrong way around.

    26. Re:But...Agile teaches us... by ebno-10db · · Score: 1

      I assure you there was a time before "Agile" was a buzzword. Of course I also remember NMOS. You may be right about "management buy in" in some places. There are still a few endangered management iconoclasts who think that "good productive way to work" beats a buzzword any day, but you've got to work with what you've got. There are also a few dinosaurs like me who remember when working this way was common practice, but we didn't know it needed a buzzword. I also remember when resources were called people. Would you like to read my first hand account of the American Revolution?

      P.S. Since you seem a little touchy on this, I'll remind you that this is a criticism of the buzzword mentality rather than your ideas.

    27. Re:But...Agile teaches us... by obarel · · Score: 1

      So what happens now with last minute customer requirement changes? I'm really trying to understand this (and hopefully learn from this).
      If you have to push them in anyway, then you're still working to crazy deadlines.
      And if you don't have to push them in, couldn't you have said "no" before moving to Agile? How did moving to Agile change your relationship with the customer?

    28. Re:But...Agile teaches us... by Anonymous Coward · · Score: 0

      requires certain pre-conditions that aren't always met

      That condition is that people are willing to use the method. Most of the time when I see it 'fail' it is because people do not even give it a chance, or go back to the old way. Usually it is allowed to happen from the top down.

      Using it also does not mean you are guaranteed success. It just means you are more consistent in what you can do. You are well rested (more important than people give it credit for). The ones who usually rebel are the ones who *want* to work 80 hours a week and they see everyone else as 'goofing off'.

    29. Re:But...Agile teaches us... by lgw · · Score: 1

      I'm just tired of programmers who think that a good idea is all you need, and don't see the value in wrapping good ideas in marketing manure, so that they can grow when planted in the empty skulls of middle management. (Me? Bitter?) The buzzword mentality isn't going away, so buzzword-compliant good ideas are worth holding on to.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    30. Re:But...Agile teaches us... by AuMatar · · Score: 2

      *Software is written by people...

      Umm, no duh? Once again, is there anything that means anything in that sentence? At absolute best it says "too much process is bad", which is a tautology- if it wasn't bad it wouldn't be too much.

      *If you spend 6 months...

      And in reality nobody ever spent 6 months just writing docs before writing code. On the other hand most agile projects fall way to hard on the other side- absolutely no documentation. Architecture doesn't appear- at least not good, clean, usable architecture. You have to think that stuff out beforehand. Its good to have the freedom to change it where it isn't meeting your needs, but spending large amounts of time constantly refactoring things because you didn't think things through up front is also wasteful. Part of the art of software engineering is figuring out where that line is.

      *PMs are your customers.

      No, not really. Not even close. My PMs represent a subset of my customers. Who aren't the same as my users. Listening to them is a good idea. Giving them what they want unfiltered is a bad one. And neither of them are necessarily the user, who also needs a seat at the table. But guess what- I don't interact with the PMs anymore at an agile company than at a non-agile one. The amount is relatively unchanged.

      *Early delivery- has as many minuses as pluses. Ever work on software that had a meaningless deadline 3 months in and need to scramble to meet it? Iterative development gives you that fun ever couple of weeks. Plus you get to show the customer half finished software and get yelled at for it not working when you know you won't have it working for months. There's situations where this is actually worth the costs- heavily GUI software where the user really deeply cares about the look and feel of the UI, is paying by the hour so you have infinite time to tweak it, and doesn't have a lot of dependencies that take a long time. There's also situations where its a miserable failure- backend software where you need to do heavy calculations and heuristics for your result where the results will need to be massaged for weeks. Or anything where you're doing actual research, and not just development. A real project needs to weigh these factors and decide which set of problems is a better one to have.

      Here's the problem- you, and a lot of other agilers, seem to think you've found something new and creative and preach it as a programming religion, and the solution to all problems. It isn't any of those things. The ideas have been around for decades. They're mostly being applied in the same way they always have. And some of the common practices are good for some types of situations. Some aren't. And those can switch up depending on the personalities of the team, the customer, the company, and the type of problem you're solving.

      You throw out the baby with the bathwater with a lot of practices recommended by Scrum, XP, etc. Particularly the utter lack of documentation, design, and forward planning. And rather than listen when people try to give you feedback all you say is "you're not doing it right".

      You want a real development methodology, I'll give you one. Think about what you're trying to do. Think about what the customer and user wants. Think about your team, their skills, and how they interact. Think about common practices and whether they fit those other things. Then choose the ones you think will work. Implement them. When something starts causing you problems, change something to fix it. In a reasonable timeframe, evaluate if that fixed it. Keep it or alter it based on that. Repeat.

      The problem is that this doesn't follow a preset plan or a nice 4 bullet points manifesto. It requires people actually work at it. Its much easier to say "we're going to be Agile" then adopt a bunch of processes (and yes, daily scrums, automated unit tests, tdd, etc are all processes and may or may not be a good fit for you) and treat that as holy writ. Then when things change and

      --
      I still have more fans than freaks. WTF is wrong with you people?
    31. Re: But...Agile teaches us... by Rhacman · · Score: 1

      It's important to use cool sounding terms in brogramming so that outsiders can know that, despite the pale complexion, that the development team is a bunch of strapping young bucks dismissing with the conventions of the establishment and putting in their all while drinking indecipherably named beverages wrought from free-trade organic coffee beans.

      --
      Account -> Discussions -> Disable Sigs
    32. Re:But...Agile teaches us... by Anonymous Coward · · Score: 0

      This +1.

      I recently documented an agile shop to capture processes, etc. Yes, they were "doing it all wrong," yet the results were solid and they delivered good code on-time (usually ahead of schedule).

      Another agile shop I worked with "did it by the book" and it was a mess. The "4 ideas" were missing.

      Its the people. Good competent people, in whatever paradigm, do good things.

      -T

    33. Re:But...Agile teaches us... by ebno-10db · · Score: 1

      The buzzword mentality isn't going away ...

      Damn, buzzwords are the one resource I wouldn't mind a shortage of.

    34. Re:But...Agile teaches us... by AuMatar · · Score: 1

      THe problem is that when you sell it based on strength of buzzword, you sell it to people looking for a buzzword. So they'll treat it like they do a buzzword- half understanding half not, so they implement the wrong parts in wrong ways. The end solution is just as bad, possibly even worse and you wasted a lot of time doing it. You do more harm than good.

      You can't solve a management problem that way, not reliably and not for long. The solution is to replace the manager, or find a job with sane management- when enough people do that they'll figure it out. Or they'll fail, either way it isn't your problem.

      --
      I still have more fans than freaks. WTF is wrong with you people?
    35. Re:But...Agile teaches us... by lgw · · Score: 1

      absolute best it says "too much process is bad", which is a tautology-

      You've clearly never worked for/with people for whom "too much process" is meaningless. Hint: some people have process as their full-time job. The more process, the more job security and the better they get paid. Glad you've had it so good.

      And in reality nobody ever spent 6 months just writing docs before writing code.

      You never did, so no one did? Believe me, such places are real: I have worked in one. Glad you've had it so good.

      My PMs represent a subset of my customers. Who aren't the same as my users. Listening to them is a good idea. Giving them what they want unfiltered is a bad one.

      So you have bad PMs? That's not rare. But thinking you have better insight into users than a PM who spends half his life talking to users is also a mistake - or are your PMs so bad they don't even do that? In any case someone who's not a dev needs to be the customer-advocate and call bullshit on the occasional "only makes sense to an engineer" design element that leaks through", and someone needs to be able to officially accept or reject work as meeting requirements - ideally they're the same person (ideally they're actual customers), but of course you have to work with what you've got.

      Ever work on software that had a meaningless deadline 3 months in and need to scramble to meet it? Iterative development gives you that fun ever couple of weeks.

      Every software project I've ever been on that badly missed it's deadlines did so because integration blew up. Multiple teams each thought they understood the spec, and each had a reasonable, but different, understanding. Forcing everyone to get not only checked in, but working together, every few weeks is the only way I've ever seen teams of 100+ meet their dates.

      Here's the problem- you, and a lot of other agilers, seem to think you've found something new and creative and preach it as a programming religion, and the solution to all problems. It isn't any of those things

      I'm not an "Agiler" and I think none of those things. All these good ideas pre-date Agile. (Are you confusing the agile philosophy with goofy methodologies like XP and scrum?) Selling a good idea to middle management requires marketing, and agile is some good (and frankly obvious) ideas dressed up with a ton of marketing and buzzwords, so that it fits in the mindset of a "VP of Engineering" who likely never coded.

      You throw out the baby with the bathwater with a lot of practices recommended by Scrum, XP, etc. Particularly the utter lack of documentation, design, and forward planning.

      Scrum and XP are products invented by consultants so that they would have something to sell. They each have some good and some bad points. But where the fuck does the idea that agile means no design come from? Heck, I've taken stupid multi-day classes on scrum (more than one) and they ridiculed that idea. Of course no sane person would work that way. Agile means not designing stuff until you must for the code you need to work on next, as opposed to designing everything before coding anything, which is just as nuts as no design.

      The heart of agile is "avoid work that you'll throw away because the requirements changed before you shipped it". Most of the rest is just expression of that aversion to throw-away work.

      It's not that I hate Agile, I don't. I hate people who push agile as "the way". And I hate Agile when its put in a place where it doesn't fit

      True enough - there will always be people who think software is created by process, and for them Agile is just the new process to slavishly follow. At least with agile, you have "too much process is bad" right there on the label, so you have less of an uphill battle.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    36. Re:But...Agile teaches us... by lgw · · Score: 1

      Sure, but it does no good to write design docs for code that never ships. Better to have both, of course - but if you only get one of code or docs? As code ages you also run into the problem that it's easier to refactor code than docs. While in a glorious utopia design docs would be kept up to date as the design changes over time - I've never seen that actually happen. So the valuable lifetime of good docs is short.

      Anyone who writes no docs at all is just being an idiot, but it's really easy to find yourself doing throw-away work when writing docs.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    37. Re:But...Agile teaches us... by gander666 · · Score: 1

      Oh, my kingdom for modpoints. This.

      --
      Suppose you were an idiot and suppose you were a member of Congress ... but I repeat myself. - Mark T
    38. Re: But...Agile teaches us... by jayesel · · Score: 1

      ROTFL!

    39. Re:But...Agile teaches us... by Chibi+Merrow · · Score: 1

      And in reality nobody ever spent 6 months just writing docs before writing code.

      What reality do you live in? I'd really like to move there if that's true, because it sure isn't in mine...

      --
      Maxim: People cannot follow directions.
      Increases in truth directly with the length of time spent explaining them
    40. Re:But...Agile teaches us... by Stiletto · · Score: 1

      We write much of our documentation while the software is being developed--it's descriptive, not prescriptive. Works for us. Much better than waterfall.

    41. Re:But...Agile teaches us... by cpitman · · Score: 1

      The difference is that saying "no" can mean the client gets it in 3 to 4 weeks (if it is really important enough to push out other work), instead of getting it in 2 years. 2 years isn't an exageration, I've worked on a project that the turn around time for a new requirement was 2+ years from conception to release to production. If you know you'll have to wait 2 years if it doesn't get in NOW, you'll fight tooth and nail.

    42. Re:But...Agile teaches us... by Jane+Q.+Public · · Score: 1

      "At this point Agile has assume mythical qualities. Any time anything fails to work as promised by Agile, the implementation gets the blame, not Agile."

      I do not agree with you at all. My point was that there are good and bad environments all over the place. You can't blame the particular things GP complained about on Agile, because they simply don't have anything to do with Agile.

      Please explain to me where it is written that Agile methodologies have anything to do with any of these things:

      Your identity, your family life, your life, being a work-bot, dissention, obedience.

      I have seen bad office environments and I have seen good office environments. And those things can be bad anywhere, for any kind of work methodology.

      I have also worked in bad "Agile" shops. And I worked in one very GOOD Agile shop. The difference is night and day. The first one was kind of like GP describes. The other was like the difference between night and day. I'd work in a place like that again any day.

      But, the important part is: they were all "Agile" shops. Those things GP complained about had nothing to do with the Agile methodology at all. Some workplaces were good, some were bad. The bad ones had bad management. Period.

    43. Re:But...Agile teaches us... by Jane+Q.+Public · · Score: 1

      Didn't mean to repeat myself in that 5th paragraph. Wasn't paying enough attention to my editing.

    44. Re:But...Agile teaches us... by RabidReindeer · · Score: 1

      We write much of our documentation while the software is being developed--it's descriptive, not prescriptive. Works for us. Much better than waterfall.

      I write a lot of MY documentation BEFORE the software is coded. Basically, I was doing Literate Programming before Knuth named it. I also wised up to Agile before it was a Big Deal when I realized that every time I delivered something to users, they said "That's great! Now I can do this! Oh wait, now I see that it would be even better it could do that!"

      Fred Brook's Chief Programmer Team concept (speaking of silver bullets that didn't Solve Everything) included a librarian as part of the team.

      Of course that was back before the days when the Chief Programmer was also supposed to be the Network Administrator and DBA.

    45. Re:But...Agile teaches us... by RabidReindeer · · Score: 1

      Oh, my kingdom for modpoints. This.

      Modded down for "This."

      Just kidding. I think.

    46. Re:But...Agile teaches us... by Anonymous Coward · · Score: 0

      The problem is that a lot of places that implement it don't commit to it. Management, instead, sees it as an opportunity for micro-management. So you end up with the worst of both worlds...no specs, extremely tight deadlines and management that wants to constantly know exactly what you're doing at all times...agile done wrong is hell.

      But there are plenty of "true scotsman"...I've worked for 2 now. But just because there are some doesn't mean that many, if not most, aren't doing it horribly wrong.

    47. Re:But...Agile teaches us... by wiredlogic · · Score: 1

      No what Agile means is "we're too lazy to develop specifications before development and we're too lazy to document the behavior when we make a release because we're already working on the next sprint".

      --
      I am becoming gerund, destroyer of verbs.
    48. Re:But...Agile teaches us... by toddestan · · Score: 1
    49. Re:But...Agile teaches us... by kermidge · · Score: 1

      Yes, we need to leveragize the forwardly of the resourcerons.

      Give it five years, you'll see it. Even better, /. didn't mind the spelling of the middle term. Ouch.

      It's happening sooner than I thought, but it's the only maxful way to methoderate ownerage through synergation.

    50. Re:But...Agile teaches us... by kermidge · · Score: 1

      "Blaming reality for the failure of a process is the wrong way around."

      Chisel that into stone. Except for those bits of reality that we collectively build.

    51. Re:But...Agile teaches us... by Anonymous Coward · · Score: 1

      If only I had mod points... Agile is another buzzword for management to hide behind and another way for them to pin their personal failures on the people who work for them. Hooray.

      It's more insidious than that. It's not management that pins the failure on the grunts. It's the grunts themselves who pin the failure on each other.

      In the one Agile conversion I worked at, I saw teams of convival developers end up going at each other's throats. *I* can't do *my* stupid little kanban card because *you* are busy doing *your* stupid little kanban card. In theory, you have the daily standup so that everyone gets the dependencies ironed out for the day.

      There's nothing intrinsically wrong with Kanban - it's just that we used to call it a defect tracking system, and we used computers to track it, and to generate reports that we could grep through for interesting keywords, rather than covering cubicle walls with paper index cards. Got nothing better to do? Pick a bug that looks like you might be able to solve it in the time you have available, with the longterm goal of reducing the number of open bugs.

      In practice, it turned into "Hey, doofus, why the fuck didn't you solve $INTRACTABLE last night, I needed it solved by this morning!" / "Because $OTHERGUY didn't solve his $TRIVIAL yesterday!" etc. etc. etc.

    52. Re: But...Agile teaches us... by Anonymous Coward · · Score: 0

      The ENTIRE point of Agile is that people are not fungible resource units.

      Jebus, at least read the manifesto before you comment.

      The amount of bitterness and deliberate ignorance in /. is astounding.

    53. Re:But...Agile teaches us... by Anonymous Coward · · Score: 0

      What's wrong with using buzzwords?

    54. Re:But...Agile teaches us... by Xest · · Score: 1

      Well that's probably because it's true.

      Agile is such a varied and broad list of principles which you can pick and choose from that it's flexible enough that you shouldn't really have any problems from it.

      Effectively, if you take waterfall and apply some of the most simple agile principles, like the idea of regular client engagement to ensure that what you understood from the original spec, and what the client understood from it (because everything is always open to interpretation, no matter how hard you hammer down the initial spec) match correctly and that the end project will be what is expected then you've still improved waterfall. If something isn't working there then it's not really the fault of agile, agile wont magically fix a failing team, but it can certainly improve processes.

      I agree there are a lot of advocates of specific well defined agile methods like SCRUM that will moan and bitch at you if you don't do anything to the letter, and I agree that in the agile community that there are lots of petty pointless arguments of what "to the letter" even is.

      But fundamentally I've never once seen a scenario where waterfall couldn't be improved by at least some of the ideas that are encompassed in the agile ideology - even if it's just allowing your developers to timebox if they work better that way, or to have retrospectives every now and then to figure out what went wrong, why, and how it can be avoided in future.

      Agile works best when you pick and choose elements that best suit your environment and in fact, if you choose to move towards SCRUM I found this better in general, moving one idea at a time, than moving directly from waterfall to full on SCRUM or whatever.

      As a counter to your "you're doing it wrong" jibe I've similarly found that the only thing consistent about people who complain about agile is that they've doing it wrong, largely because they haven't learnt enough about it, haven't spent the effort figuring out how it fits in for their work patterns, and haven't bothered to explain it to their team properly and make sure their team gets it. It works both ways. It's a bit like taking a team of Java programmers and then telling them from tomorrow everything will have to be done in assembly - it's not a change you can make overnight, some developers are going to struggle with the transition and changes, and your entire tool chain is going to have to change and so forth. A lot of people who have tried and failed simply don't get that and blame agile, rather than their poorly researched understanding and poor planning for the changes. If you really want to do the move then nothing beats some professional training from a genuinely good trainer, but many just try to hack it in with no planning based on nothing more than a few shitty articles they've read on the internet. The other common reason for complaints I've seen have been from development leads who have misfunctioning teams that keep failing and/or doing a bad job and expect agile to be a magic fix, then blame it when it isn't, and when in reality they needed to solve the inherent problems with their team, be that lack of cohesion, incompetence, demotivation, or whatever.

      It's not that I'm some agile fanboy or something, where I work now we're still primarily waterfall oriented and haven't made the move and I don't really have a problem with it, but I've done some decent agile training, have worked places where it does work, have worked places where a hash up was made of it, and have successfully transitioned teams to it. I also understand that as in my current place of work, it's a large initial time and cost investment to move over to it successfully precisely because you do have to do it right and that right now, we just don't have the free time for that level of investment and have a strong enough team of only senior developers and up that the current status quo is working okay despite the flaws in the methodology which we're experienced enough to work around (often by using elements of agile informally

    55. Re:But...Agile teaches us... by PmanAce · · Score: 1

      Well you are doing it wrong. In my experience (I worked in one of the top 3 video game companies in the world) it worked like it claims to do. A different team member was the scrum master every week, assured that the daily meetings were short and concise. We had our iteration planning done properly and our death mortem meetings at the end of each iteration to discuss improvements and fails. Once your team gets into the groove, your team velocity is calculable and improvable...maybe you guys were just lazy?

      --
      Tired of my customary (Score:1)
    56. Re:But...Agile teaches us... by PmanAce · · Score: 1

      Why do I keep seeing the notion that agile speeds up coding? That is simply not true! All it does is releases certain features sooner so the client can approve of them instead of releasing everything at the end and having an "oh shit, he changed his mind" moment when it's too late. As for the documentation aspect, we had several tasks in our iterations to document code, use cases, etc. The team lead or project manager usually took care of obtaining the specs from the clients and writing the documentation for it.

      --
      Tired of my customary (Score:1)
    57. Re:But...Agile teaches us... by AuMatar · · Score: 1

      Once again- a prime example of the problem with agile. Believes that it solves every problem, and his first reaction, rather than asking for details an analyzing, is to say "you're doing it wrong".

      --
      I still have more fans than freaks. WTF is wrong with you people?
    58. Re:But...Agile teaches us... by PmanAce · · Score: 1

      It doesn't solve every problem but it can darn well replace the old waterfall development practice which is/was used for pretty much every project. If agile works for making AAAA games as well as a wide variety of projects involved in game development, HR systems, IT, finance, etc...why wouldn't it work for your projects?

      --
      Tired of my customary (Score:1)
  4. Pfft by Dancindan84 · · Score: 5, Funny

    To keep employees happy, Duffy says, it's better to make them go home to their families for dinner.

    That's fine for regular employees, but assuming sys admins want to go home to their families is just silly.

    http://xkcd.com/705/

    --
    "Always forgive your enemies; nothing annoys them so much." - Oscar Wilde
    1. Re:Pfft by egcagrac0 · · Score: 4, Insightful

      Being the kind of sysadmin that behaves like that, I can assure you I'd prefer to work in a team with other like-minded types, so I know that I can go home, and we'll still be online.

      24 hour coverage is much easier to do with 4 or 5 rotating watches than 1 guy on call.

    2. Re:Pfft by Dancindan84 · · Score: 1

      A team of 4-5 sys admins? Do you guys all have the passwords? Someone should tell San Francisco.

      --
      "Always forgive your enemies; nothing annoys them so much." - Oscar Wilde
    3. Re:Pfft by egcagrac0 · · Score: 2

      You really need to look into something like this.

    4. Re:Pfft by Anonymous Coward · · Score: 0

      In most companies they don't want to spend money on extra bodies so one guy does all.

    5. Re:Pfft by mvdwege · · Score: 1

      No, you really shouldn't. Cyber-Ark sucks donkey balls, its support for anything but Windows is cumbersome, adminning it is even more cumbersome, and when the unintuitive GUI gives an uninformative error and you can't reach your systems, you get to deal with their lousy support.

      --
      "I know I will be modded down for this": where's the option '-1, Asking for it'?
    6. Re:Pfft by egcagrac0 · · Score: 1

      Cyber-Ark sucks donkey balls

      Stipulated. (IMO, the solution sucks because the nature of the problem sucks.)

      What's a better solution with similar functionality for a group of admins?

    7. Re:Pfft by mvdwege · · Score: 1

      This is taking it off-topic, but in short: it depends on how you define 'similar functionality'. For the practical purposes of sharing privileged passwords, any decent password storage application like KeePassX will do.

      Cyber-Ark is specifically created to take away privileged system powers away from admins and put their administration in management's hands. This is why it is almost always pitched at management, not admins themselves.

      And the auditing argument is silly, because there already exist methods of tracking the use of privileged accounts without hassling admins.

      --
      "I know I will be modded down for this": where's the option '-1, Asking for it'?
    8. Re:Pfft by egcagrac0 · · Score: 1

      KeePass (and derivatives) looks like a reasonable system for a group of 4-5 admins.

      The group I deal with is significantly larger than that.

      If you trust all your admins with root access to all your systems, then KeePass might work for you.

      If you don't trust all of your admins with root access to all your systems, then something that allows access to some (but not all) systems based on user ID is preferred.

    9. Re:Pfft by mvdwege · · Score: 1

      Cyber-Ark is not any better at dealing with large groups.

      The best way to do it in KeePassX is to set up a separate database per user group; but I agree that currently there is nothing that easily integrates with existing Identity Management systems; I would love to have a decent solution that talks LDAP, for example.

      --
      "I know I will be modded down for this": where's the option '-1, Asking for it'?
  5. Hiring assholes is never worth it. by gestalt_n_pepper · · Score: 5, Insightful

    You end up with unmaintainable code, late deadlines and an environment where numerous employees want to kill each other. Profit? Good luck.

    It doesn't matter how talented the asshole is if he\she costs more than they're worth. I'd rather have a few mediocre developers who are nice to each other, write to spec, comment appropriately, and write code that anyone can understand and maintain.

    --
    Please do not read this sig. Thank you.
    1. Re:Hiring assholes is never worth it. by NFN_NLN · · Score: 3, Insightful

      You end up with unmaintainable code, late deadlines and an environment where numerous employees want to kill each other. Profit? Good luck.

      It doesn't matter how talented the asshole is if he\she costs more than they're worth. I'd rather have a few mediocre developers who are nice to each other, write to spec, comment appropriately, and write code that anyone can understand and maintain.

      I think you're confusing jerk-off with asshole. A jerk-off is what you're describing in the first sentence, and also the environment that eventually turns other people into assholes.

      A true asshole does quality work, but quickly becomes annoyed when:
      - people check in "shit" code that fixes the symptom without addressing the actual problem
      - they have to adhere to shit specs they had no input on
      - they have to work with jerk-offs (as defined above)

      "Know your shit" OR "Know you're shit"

    2. Re:Hiring assholes is never worth it. by TXG1112 · · Score: 5, Insightful

      developers who are nice to each other, write to spec, comment appropriately, and write code that anyone can understand and maintain.

      This is pretty much the textbook definition of a good programmer, not a mediocre one.

      --
      I will not be pushed, filed, stamped, indexed, briefed, debriefed, or numbered. My life is my own.
    3. Re:Hiring assholes is never worth it. by Spy+Handler · · Score: 5, Insightful

      I'd rather have a few mediocre developers who are nice to each other, write to spec, comment appropriately, and write code that anyone can understand and maintain.

      If they could do that (esp. the bold part), they wouldn't be mediocre developers.

    4. Re:Hiring assholes is never worth it. by Anonymous Coward · · Score: 1

      I'd rather have a few mediocre developers who are nice to each other, write to spec, comment appropriately, and write code that anyone can understand and maintain.

      I don't think mediocre means what you think it means.

    5. Re:Hiring assholes is never worth it. by Tablizer · · Score: 1

      You may be confusing social assholes with coding assholes. Sometimes socially clueless idiots write the best code; you just don't want to interact with them if possible unless you've formed a tough back-bone.

    6. Re:Hiring assholes is never worth it. by HeckRuler · · Score: 1

      Salesmen.

    7. Re:Hiring assholes is never worth it. by Anonymous Coward · · Score: 0

      That's not entirely true. There are certain problems (not even all that difficult) that mediocre people will never, ever be able to solve. One's best bet is to hire a gifted person who is pleasant but if it's not possible, a business must bite the bullet in some way: hire the difficult person as a contractor or potentially lose business while searching for someone nice capable of doing the work.

      A developer who writes unmaintainable code and misses deadlines is by definition not a gifted worker. It doesn't matter whether such a developer is pleasant or not: such a person is a liability and should not be hired and, if he is employed, he should be redeployed into an area where he can be an asset or he should be fired.

      Finally, the classic example of the asshole who is worth it is Steve Jobs. I have never read of a successful person who created a real business who was such an incredible douche bag.

    8. Re:Hiring assholes is never worth it. by Dancindan84 · · Score: 3

      You end up with unmaintainable code, late deadlines and an environment where numerous employees want to kill each other.

      Assholes create and cause shit. Noted.

      --
      "Always forgive your enemies; nothing annoys them so much." - Oscar Wilde
    9. Re:Hiring assholes is never worth it. by Anonymous Coward · · Score: 1

      You are falling into the trap of correlating talent with asshole. In my experience, a lot of real assholes also tend to be less technically talented as well.

      Lack of social skills does not correlate to intelligence either.

    10. Re:Hiring assholes is never worth it. by Anonymous Coward · · Score: 5, Insightful

      Have people been calling you an asshole for so long that you feel the need to redefine the word asshole into something good? "Asshole" most certainly does not imply or even in the slightest connote competence.

    11. Re:Hiring assholes is never worth it. by dgatwood · · Score: 3, Insightful

      A good programmer, but not a good developer. Non-mediocre developers are good enough at software architecture to contribute to the spec, not just follow it.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    12. Re:Hiring assholes is never worth it. by Kwyj1b0 · · Score: 4, Insightful

      developers who are nice to each other, write to spec, comment appropriately, and write code that anyone can understand and maintain.

      This is pretty much the textbook definition of a good programmer, not a mediocre one.

      Ah, but the definition among many young-uns is all night marathon coding living off soda and cheetos with the occasional coffee/smoke break, and producing something that is lean, mean and impresses other programmers with cryptic lines that no one else understands. After all, who looks at code they wrote the previous semester? Whitespaces and comments are for n00bs - the code is the documentation.

    13. Re:Hiring assholes is never worth it. by Anonymous Coward · · Score: 1

      No, an asshole isn't a nice person who's better than everyone. They're just that, an asshole.

    14. Re:Hiring assholes is never worth it. by lgw · · Score: 5, Insightful

      To me, the bold part is the bar for being an average developer. Not to be harsh, but if you can't right good code to spec then you suck, and should do something else for a living.

      A good developer finds the simplicity hidden in each complex problem. He creates the design that makes people say "wow, it really is that simple" not "hmmm, how does that actually solve the problem here".

      --
      Socialism: a lie told by totalitarians and believed by fools.
    15. Re:Hiring assholes is never worth it. by Kjella · · Score: 1

      This is pretty much the textbook definition of a good programmer, not a mediocre one.

      It could be.. but you can still get stuff like "implement a product filter" with this pseudocode

      List<Product> getProducts( string filter ) {
      List<Product> out;
      SELECT * FROM products
      foreach product {
            if column 2 match filter then append to out
      }
      return out;
      }

      It's to spec, understandable, maintainable yet stupid and fragile. Particularly some rather fresh developers can comment a lot and KISS, but still have a way to go to be good code.

      --
      Live today, because you never know what tomorrow brings
    16. Re:Hiring assholes is never worth it. by donscarletti · · Score: 2

      Assholes is a very subjective term. I know plenty of guys who are frequently labelled "assholes" who write brilliantly clear, extensible code to deadline, mentor others and drive groups of people forward as a team. They are labelled assholes by the people who don't complete tasks, push both work and blame onto others and shirk responsibility. Brilliant and hard working people have very high standards and very rarely afford civility to those who willingly fall short and thus are perceived as assholes by them.

      I worked in a company where people would regularly curse a guy who resigned a year before I arrived, saying he's a giant asshole, he wrote unmaintainable code, he used perverted coding conventions, blah blah blah. I thought it was strange since I noticed his name all though the commit log with more than double the work output of everyone else and more or less the same quality code. I met him afterwards and the guy was clever, articulate, polite and we discussed his code. He humbly acknowledged that he had written that code in a rush under pressure and was very surprised that it was still there in its entirety and nobody had bothered to revise it with something more permanent. He also explained to me his slightly unorthodox coding conventions (antonyms having the same number of letters to make definitions line up) and they made a bit of sense too, as much as anyone else's conventions. You see, people didn't like him, not because he was selfish or abusive or whatever, just because he was better than them and he wouldn't waste his time mentally masturbating with them when there was a deadline looming.

      I realise now, "asshole" tends to work both ways.

      --
      When Argumentum ad Hominem falls short, try Argumentum ad Matrem
    17. Re:Hiring assholes is never worth it. by Anonymous Coward · · Score: 0

      Wow, all those people were right. I really am an asshole.

    18. Re:Hiring assholes is never worth it. by cayenne8 · · Score: 1
      True, but if you are mildly decent with skills, and superior with social skills, you can often not only get by, but excel in the company.

      Manipulation is a skill that is often underrated, and not always a bad thing.

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    19. Re:Hiring assholes is never worth it. by Anonymous Coward · · Score: 2, Interesting

      "A true asshole does quality work" - -really? How is an asshole more likely to do quality work than anyone else? As you state, assholes are as part of the definition thin skinned, and generally overbearing (read, do not consider other, possibly better, solutions) and destory what could be an optimal path for their ego. The asshole has pretty much set all mankind back thousands of years, from the assholes who destroyed the Library of Alexandria, to the assholes who imprisoned Coppernicus, to the assholes who killed Aristotle, to the assholes who burned the Mayan codices, to the assholes who worked in _n_ corporations and led _x_ teams down the drain.

    20. Re:Hiring assholes is never worth it. by Anonymous Coward · · Score: 0

      If you really mean _anyone_ then I respectfully disagree. I much prefer being able to write (month+1)%12 instead of dozen ifs.

    21. Re:Hiring assholes is never worth it. by tnk1 · · Score: 1

      If you're working on a team where one person truly cannot do all the heavy lifting, a social asshole is nearly equivalent to a coding asshole. If you can put them in a corner and use their code like a black box, then maybe it works out. Even then, that guy would have to be a fucking genius to justify their limited usefulness as a team member.

      What I see often is people who assume that what comes out of the asshole can be black boxed, but in the end, is not actually independent. Or even if it *could* be independent, the asshole decides to piss in the others coders' Cheerios and start redefining shit outside their designated box.

      In short, assholes with a high level of talent have to be dealt with very carefully, and assholes who are merely even above average may not even rate employment unless you have no other option. In the end, in this field, it is often the assholes who put the "work" in to "workday". Their "talent" is rarely an excuse for their inability to understand social conventions.

    22. Re:Hiring assholes is never worth it. by Anonymous Coward · · Score: 0

      Very much depends on the spec, doesn't it? Are we talking about a 3-ring binder filled with every UML diagram known to mankind, and a few that aren't? Or a grubby napkin from the pizza joint across the street with a sketch in blue pen with "Do This!!!!!" circled in red ink?

    23. Re:Hiring assholes is never worth it. by forkazoo · · Score: 1

      You end up with unmaintainable code, late deadlines and an environment where numerous employees want to kill each other. Profit? Good luck.

      It doesn't matter how talented the asshole is if he\she costs more than they're worth. I'd rather have a few mediocre developers who are nice to each other, write to spec, comment appropriately, and write code that anyone can understand and maintain.

      Indeed, hiring an asshole rarely survives a really thorough cost benefit analysis. Unfortunately, the people who hire assholes never seem to take into account the potentially far reaching effects that one epic ass can have on a company. Even people who never have to interact with that person have to deal with the people who do, and the morale impact can be far reaching. I'm sure there are some rare cases where an absolute ass is unarguably the right person for a job, but these cases are few and far between. If there are any objections to be made, the long run cost is generally not worth the trouble.

      (Recently had my asshole quotient expanded at the office. Have basically become completely ambivalent about the job. If they convince me to resign, they are losing one of the more qualified people in the US in a very narrow niche that I fill.)

    24. Re:Hiring assholes is never worth it. by grumpyman · · Score: 1

      No kidding. I'm sure many heard of coders holding employer/managers hostage.

    25. Re:Hiring assholes is never worth it. by techno-vampire · · Score: 1

      After all, who looks at code they wrote the previous semester?

      And, of course, if last semester's code is all you have to show, you're probably not qualified unless you're applying for an internship or a job as an entry-level code monkey. Real programmers have real-world experience to show.

      --
      Good, inexpensive web hosting
    26. Re:Hiring assholes is never worth it. by Anonymous Coward · · Score: 1

      "Know your shit" OR "Know you're shit"

      The best programmers I've worked with have always told me that they're terrible and that they make mistakes all the time. They then set up processes to deal with all the mistakes they're going to make (TDD, code reviews, etc). So in a way, you'd want to both "Know your shit" AND "Know you're shit", but know how to handle your shit when you didn't know your shit as well as you thought.

    27. Re:Hiring assholes is never worth it. by admdrew · · Score: 3, Insightful

      Our top performing salespeople are all incredibly nice people that are easy to get along with. Sales is about developing and maintaining relationships, both with customers, and with the engineers/support people/managers that drive the concrete aspects of your business. If you need to be an asshole to be a good salesperson, then the product/service you're selling is terrible, or you don't understand it well enough to sell effectively.

    28. Re:Hiring assholes is never worth it. by Anonymous Coward · · Score: 0

      This depends. If the architecture is already being followed by others (perhaps the dev is a late edition to the team), they should be following the spec, not "contributing" to it. Consistency is king. A bad architecture can be re-written bit by bit, an inconsistent one is screwed.

    29. Re:Hiring assholes is never worth it. by jayesel · · Score: 2

      Assholes are assholes. They stink, and are terrible for any org. Your post, turning it into a positive is simply silliness. That word must have some positive value to you. Sad if it does.

    30. Re:Hiring assholes is never worth it. by operagost · · Score: 1

      But what about the dicks and pussies?

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    31. Re:Hiring assholes is never worth it. by Anonymous Coward · · Score: 0

      I know you don't, nigger.

    32. Re:Hiring assholes is never worth it. by Stiletto · · Score: 1

      If that's true, then it's exceedingly difficult to find average-or-better programmers.

    33. Re:Hiring assholes is never worth it. by Hognoxious · · Score: 1

      Finally, the classic example of the asshole who is worth it is Steve Jobs.

      One, most companies are not looking for Steve Jobs. Or rather, most positions in companies are not the ones where St. Steve would fit.

      Two, most assholes are not Steve Jobs. There is (was, if he doesn't rise again) one Steve Jobs. There a millions of assholes. Do the math.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    34. Re:Hiring assholes is never worth it. by Anonymous Coward · · Score: 0

      I knew it! I'm surrounded by Assholes!

    35. Re:Hiring assholes is never worth it. by Anonymous Coward · · Score: 0

      Want them to use whitespace? Make them debug JavaScript without whitespace in Notepad. Control-arrows are your friend.

    36. Re:Hiring assholes is never worth it. by flandre · · Score: 1

      well, assholes certainly do deal with a lot of shit on a regular basis!

    37. Re:Hiring assholes is never worth it. by Anonymous Coward · · Score: 0

      Sure it does...incompetent assholes get fired. Competent assholes get tolerated (and often promoted).

    38. Re:Hiring assholes is never worth it. by Anonymous Coward · · Score: 0

      The code is the documentation. Documentation is required for people who cannot write code. People who cannot write code have no business pretending that they can read code. Know your shit or know you're shit.

    39. Re:Hiring assholes is never worth it. by Anonymous Coward · · Score: 0

      ok, so how do you interview for this? I AM THIS PROGRAMMER. But if I can't pass your Whiteboard Gauntlet of Pain, what does it matter?

       

    40. Re:Hiring assholes is never worth it. by Anonymous Coward · · Score: 0

      Good code doesn't need anybody to right it to spec. It's already written to spec so there isn't anything needing to be righted.

    41. Re:Hiring assholes is never worth it. by TheGratefulNet · · Score: 1

      the old joke "commenting is for newbs; if the code was hard to write, it should be hard to read!"

      (no, I don't follow that, myself!)

      --

      --
      "It is now safe to switch off your computer."
    42. Re:Hiring assholes is never worth it. by Anonymous Coward · · Score: 0

      Not to be harsh, but if you can't right good code to spec then you suck, and should do something else for a living.

      I'm pretty sure you intended to be harsh. Or, you would have found a better way to express your thoughts. Bravado can be just as toxic to a work environment as a poor coder. I've seen developers get so caught up in stuff like this, they forget their audience.

      Good developers look in the proverbial mirror and often find things were not "as simple as that".
         

    43. Re:Hiring assholes is never worth it. by Anonymous Coward · · Score: 0

      Your metaphors are wrong, because what comes out of the asshole is either shit or stinky hot air without substance. The shit is nothing but undesirable waste product and the hot air is nothing but a nuisance.

      The jerk-off, on the other hand is too busy trying to produce (and then waste) a certain bodily fluid that has nothing or (generally) very little to do with shit or assholes.

      Although an asshole can be contained within the jerk-off, it can only be the other way around in cases of physical abuse or non-conforming personal preferences involving more than one individual.

    44. Re:Hiring assholes is never worth it. by Anonymous Coward · · Score: 0

      You sound like a real Jerk off.

    45. Re:Hiring assholes is never worth it. by Anonymous Coward · · Score: 0

      commenting to undo rating mistake.

    46. Re:Hiring assholes is never worth it. by kermidge · · Score: 1

      They're whence assholes come.

    47. Re:Hiring assholes is never worth it. by S3D · · Score: 1

      However some projects require for code do something specific, nontrivial and be finished in finite time. Readable, commented, understandable code which do nothing is acceptable for very long projects where managers and team leaders change job before project is cancelled.

    48. Re:Hiring assholes is never worth it. by Anonymous Coward · · Score: 0

      He didn't imply that "asshole" means "competent". I don't see how you made that conclusion. He just described how a competent person becomes an asshole.

    49. Re:Hiring assholes is never worth it. by lgw · · Score: 1

      Have you been personally involved in searching? With a good interview process it's not hard to screen for good programmers. The challenge is getting any kind of candidate pipeline if you're not at one of the big name shops - but that's not unique to software by any means.

      --
      Socialism: a lie told by totalitarians and believed by fools.
  6. yay! by Anonymous Coward · · Score: 1

    We have brogrammers where I work. Idiots, every one of them.

    1. Re:yay! by Anonymous Coward · · Score: 0

      I see someone's dropped a few tabs of Agile this morning.

    2. Re:yay! by moeinvt · · Score: 0

      Send this article to your CEO and recommend that they fire all the young, single, childless (white) males.

    3. Re:yay! by Minwee · · Score: 1

      Send this article to your CEO and recommend that they fire all the young, single, childless (white) males.

      But then who will make all of your games?

  7. lol by Anonymous Coward · · Score: 0

    30 employees and nobody's left? Wow! And they offer maternity leave? O. M. G. Seriously, what kind of ignorant fluff is this?

  8. Reactionary much? by Anonymous Coward · · Score: 0

    Some of us are young, single, and childless (not necessarily male). It's a neat perk that keeps the cost of living down, and in the Bay Area those costs are already ludicrously expensive.

    Besides, who wants to take advice from a four year old no name company just barely out of its diapers? Come back when you've been around at least a decade.

    1. Re:Reactionary much? by Anonymous Coward · · Score: 0

      I work for a 30+ year old company that's doing particularly well. Lots of experience (read: older workforce with very little attrition), offices in areas with far lower CoL than SF, relatively little empire building, few primadonnas, absolutely no brogrammer culture, and most importantly work weeks capped at 50 hours for salaried employees. Seek us out before your caffeine tolerance builds up and you have to switch to Adderall.

    2. Re:Reactionary much? by salteye · · Score: 0

      See this? Pompous, self-righteous attitude. Yeah, I'm sure your older workforce is made of coding aces who are honing their skills after their families go to bed. Have fun living in your bubble. Hope you don't get laid off!

    3. Re:Reactionary much? by mjwalshe · · Score: 1

      And when the IRS clamps down on benefits in kind will you feel the same way.

    4. Re:Reactionary much? by hawguy · · Score: 1

      Some of us are young, single, and childless (not necessarily male). It's a neat perk that keeps the cost of living down, and in the Bay Area those costs are already ludicrously expensive.

      Besides, who wants to take advice from a four year old no name company just barely out of its diapers? Come back when you've been around at least a decade.

      There's plenty of cheap (and good) food in the bay area - if you can afford the cost of Bay Area housing, dinners needn't be a major expense. I can pick up a decent meal (Chinese, Mexican, Thai, Vietnamese, etc) for $6 - $8 within a 10 minute walk from home or from the office. Though I usually end up cooking.

    5. Re:Reactionary much? by Anonymous Coward · · Score: 0

      You sound like you're insecure about your livelihood. If you choose to spend your free time getting ahead in life instead of enjoying it, I'd suggest trying to build your skills in areas that are under-served.

    6. Re:Reactionary much? by salteye · · Score: 0

      No, it's just that as younger programmer it bothers the hell out of me that people take age as an automatic sign of superiority or inferiority.

    7. Re:Reactionary much? by lgw · · Score: 3, Insightful

      There are plenty of place that don't suck. I hope you work in one. There are plenty of places where no one needs to work more than 40 hours to meet commitments, and only the overachievers do.

      There are plenty of places where the norm is for a coder to have his or her daily schedule dominated by whether he or she "picks up" or "drops off" the kids, not by meetings. There are plenty of places where keeping your skills current isn't some after-hours effort. Strangely enough, programming doesn't require heroic effort to ship on time if your basic engineering processes are smart to begin with - something that requires experience with many ways of doing things to get right.

      A mature workforce is part of all of that. Look at any other engineering discipline, and you'll see careers from the early 20s to the early 60s, and a real career path for the second twenty years of engineering work. Software engineering is still maturing as a field, but we'll get there.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    8. Re:Reactionary much? by salteye · · Score: 0

      I guess if you want to hire people based on age rather than programming ability you've probably got a suboptimal team anyway. So in a way you're right, I'm caring way too much about this.

    9. Re:Reactionary much? by cayenne8 · · Score: 1

      No, it's just that as younger programmer it bothers the hell out of me that people take age as an automatic sign of superiority or inferiority.

      Well, age *is* about the ONLY way you'll gain superiority in experience, which often is a trait that is highly desired, and hard to come by when still wet behind the ears so to speak.

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    10. Re:Reactionary much? by ebno-10db · · Score: 1

      Slashdot is now for angry older people in their 30s and 40s.

      Who keeps moding this guy down? The comic relief is great! And no, I don't mean that as a joke.

    11. Re:Reactionary much? by Stiletto · · Score: 1

      If you need to work more than 40 hours a week to meet your commitments, that's definitely not over-achievement. You're taking 80 hours to do 40 hours of work.

    12. Re:Reactionary much? by Seumas · · Score: 1

      I'm fortunately child-free and I enjoy working. I'm in no rush to not be working and even if I weren't paid to do what I do for a living, I would probably be doing some form of it on the side, for free. I always enjoyed having a cafeteria with several restaurants in it open for at least two meals a day (and good food, too -- made by a variety of professional chefs). I've always enjoyed the free drinks and coffee. The free donuts, muffins, bagels, and fruit. The on-site star-bucks (with ice-cream parlor). The recreational activities. Bringing the dogs to work. Having a concierge to help with arranging, planning, or finding things around town. The high quality vending machines. The giant beanbags and comfortable community seating and open-areas.

      All of these things contribute to a positive and friendly atmosphere for the place you spend more than a third of your life at. Just because some people might be in a rush to get home to park themselves in front of the television all night with a house full of noisy kids doesn't mean everyone is and creating a great work environment doesn't mean that people who don't want to be there more than they have to be can't just go home and do whatever it is they're itching to go do.

      Besides, I've gotten far more value out of such amenities and environments over my career than I ever got from countless stock options (even restricted options). :D

  9. 30 workers over 4 years? by Anonymous Coward · · Score: 0

    While I don't disagree with his logic or reasoning I do double his methodology would hold true for a larger subset of employee demographic.
    Basically to summarize he states:
    Make a highly profitable product.
    Don't overwork your staff.
    Hire people who can't as easily uproot and change.
    Don't hire assholes.
    No shit... really.

    1. Re:30 workers over 4 years? by Zephyn · · Score: 1

      Based on what I've seen and the places I've worked over the years, all of that is nowhere near as easy as it sounds.

    2. Re:30 workers over 4 years? by benjfowler · · Score: 1

      It's common sense.

      And there's nothing common at all about "common" sense. Duffy is a genius, so you'd expect him to show common sense even at his age (he's only 26).

      What he seems to have stumbled upon too, is our industry's ridiculous Peter Pan myth, that youth and rudderless energy trumps experience and wisdom.

      A lot of people start startups to flip them. The failure rate is exceedingly high. Conventional businesses that aim to grow organically are less sexy, still fail, but don't fail nearly as often as "startups". I would like to build a serious business once; I don't think I would like to start a "startup".

    3. Re:30 workers over 4 years? by wonkey_monkey · · Score: 1

      Duffy is a genius, so you'd expect him to show common sense

      I don't think the link between genius and common sense is as strong as you seem to think it is.

      Though I may only be saying that because I definitely don't have any of one of those.

      --
      systemd is Roko's Basilisk.
    4. Re:30 workers over 4 years? by benjfowler · · Score: 1

      "Common sense" is basically wisdom.

      The exceptional people I've known can not only assimilate enormous amounts of knowledge in a short time, they can also pick up wisdom faster. Wisdom is definitely an edge when starting and running a business.

  10. They're overanalyzing. by ron_ivi · · Score: 5, Insightful
    Just keep employees happy.

    Some programmers like free dinners, and enjoy sleeping til noon and working til midnight, and don't mind the 12 hours because their best friends are at work.

    Other programmers want to work 9-5 to drop kids off in the morning and get home to them at dinner.

    Many programmers go through each of those stages in their carreers.

    It's not an either/or question. Just make a workplace that accomodates both groups and keeps both happy.

    1. Re:They're overanalyzing. by dkleinsc · · Score: 3, Insightful

      The thing is, the art of management in IT is often perceived as being maximizing the amount of hours worked (in the demonstrably mistaken belief that this means these programmers are getting more done), so companies try to ensure they get more programmers in the first group and no programmers in the second group.

      --
      I am officially gone from /. Long live http://www.soylentnews.com/
    2. Re:They're overanalyzing. by Hentes · · Score: 1

      Maybe it's easier to accomodate to a uniform group. Although it's worth pointing out that this approach may not work outside the US, hiring based on age, sex and family status isn't exactly legal everywhere.

    3. Re:They're overanalyzing. by benjfowler · · Score: 4, Insightful

      Maximising output, perhaps?

      Dumb people think that (maximising hours) == (maximising output), knowing nothing about how productivity tails off when hours worked in a week exceed ~ 40 or so.

      There's a VERY good reason why people work 35-40 hour weeks. To maximise individual output.

    4. Re:They're overanalyzing. by The+End+Of+Days · · Score: 0

      Well shitty programmers need jobs as well. They get jobs in the places like you describe.

      Are those the jobs you seem to keep getting? Guess what that says about your skills.

    5. Re:They're overanalyzing. by Anon-Admin · · Score: 1

      Managers and MBA's think that (maximising hours) == (maximising output), knowing nothing about how productivity tails off when hours worked in a week exceed ~ 40 or so.

      I fixed it for you. The above is true of 99.9% of the companies I have worked for.

    6. Re:They're overanalyzing. by moeinvt · · Score: 2

      "Dumb people think that (maximising hours) == (maximising output),"

      The post clearly stated that this is the philosophy of "IT management".

    7. Re:They're overanalyzing. by Anonymous Coward · · Score: 1

      Some programmers like free dinners, and enjoy sleeping til noon and working til midnight, and don't mind the 12 hours because their best friends are at work.

      Other programmers want to work 9-5 to drop kids off in the morning and get home to them at dinner.

      Then there are people with circadian rhythm or other sleep disorders.

    8. Re:They're overanalyzing. by Kwyj1b0 · · Score: 0

      Just keep employees happy.

      Some programmers like free dinners, and enjoy sleeping til noon and working til midnight, and don't mind the 12 hours because their best friends are at work.

      Other programmers want to work 9-5 to drop kids off in the morning and get home to them at dinner.

      Many programmers go through each of those stages in their carreers.

      It's not an either/or question. Just make a workplace that accomodates both groups and keeps both happy.

      While I agree in principle, it doesn't help in practice. Maybe someone young comes in who likes spending time away from the office, maybe has a significant other/children. If his boss is a workaholic (he might like being that way), junior feels pressured into staying late and sacrificing his interest so as not to "look bad" or get laid off when things go bad (as they eventually do, for factors outside the organization's control).

      In fact, I'd say that having such a policy is good because if you really want to work, you can always network in from home or take your work home or something. But you don't pressure others into staying with you. You could do something like have a take out cafeteria at the end of the day - want to keep working? Grab a to-go bag and go wherever you want and work.

    9. Re:They're overanalyzing. by dgatwood · · Score: 5, Interesting

      Productivity in areas that require actual thought and concentration falls off after about 20 hours. Even 40 hours is a joke for anything but menial physical labor.

      What this means is that the best ways to increase worker productivity are:

      • Ban meetings. Most days should have exactly zero meetings; if you have three meetings per day, you can't get work done because of all the interruptions.
      • Most meetings should be either at the end of the day, the beginning of the day, or at lunch (with food). This minimizes the disruption that they cause.
      • Require all emails to contain a bullet-point executive summary. One person concentrates when writing it so everyone else doesn't have to concentrate while skimming it.
      • Standardize on a 30-hour workweek.
      • Standardize on an office environment so that workers can easily shut their doors and concentrate for periods of time.
      • Suggest specific break times that workers can choose so that they maximize their interaction with other people while minimizing how much they interrupt other workers in between.
      • Encourage workers to take non-work classes, form activity groups, etc. so that they don't burn out.
      • Encourage workers to work on things that they enjoy working on. Hire contractors to deal with the painful crap.

      If you do these things, your productivity will soar.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    10. Re:They're overanalyzing. by cayenne8 · · Score: 2

      Hire contractors to deal with the painful crap.

      I'll take BE a contractor...

      Come in, do work, have incredibly HIGH bill rate, don't have to fsck with office politics, get paid for EVERY hour you work, rarely get asked to work OT, and write off many more things on taxes than the W2 employees.

      Also..dictate your own vacation hours (included in your bill rate).

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    11. Re:They're overanalyzing. by kimvette · · Score: 1

      As a release engineer I loved going into work between 6:30 and 7:00 (after having logged in at 5:30 remotely to check on things), then leaving between 3:00 and 3:30 and having late afternoon and evening free to go out.

      --
      The Christian Right is Neither (Christian nor right). See: Matthew 23, Matthew 25, Ezekiel 16:48-50
    12. Re:They're overanalyzing. by Anonymous Coward · · Score: 1

      Ban meetings. Most days should have exactly zero meetings; if you have three meetings per day, you can't get work done because of all the interruptions.

      Sometimes possible, but simply having a managerial dislike of meetings is significantly better than having managers addicted to meetings.

      Most meetings should be either at the end of the day, the beginning of the day, or at lunch (with food). This minimizes the disruption that they cause.

      Even more important is making sure that the population of the meeting is exactly the collection of people who will benefit and/or provide benefit by being present.

      Require all emails to contain a bullet-point executive summary. One person concentrates when writing it so everyone else doesn't have to concentrate while skimming it.

      If your email needs an executive summary, it is too long already. Send the summary, and put in a link for more detail if anyone is curious.

      Standardize on a 30-hour workweek.

      Or at least accept that people are not so binary as to be able to completely stop thinking about work-related challenges in their off-time, so relax about the scheduled workweek.

      Standardize on an office environment so that workers can easily shut their doors and concentrate for periods of time.

      I haven't had a door, but the nature of the co-workers (and management) seems to be a bigger factor than the inherent privacy options of the room layout.

      Suggest specific break times that workers can choose so that they maximize their interaction with other people while minimizing how much they interrupt other workers in between.

      Sounds a bit more overmanaged than I prefer, but I would see nothing wrong with posting a "please contact me in the below timeslots" list for those who like the structure.

      Encourage workers to take non-work classes, form activity groups, etc. so that they don't burn out.

      Such as, letting employees go pursue their hobbies after work and on the weekend, and not crushing them with overtime or "mandatory office parties," sure.

      Encourage workers to work on things that they enjoy working on. Hire contractors to deal with the painful crap.

      When possible, but this mentality has been the primary weakness of open-source projects. Developers work only on the parts that interest them, and longstanding bugs that they personally don't mind will be overlooked for years. While the best solution is to find people who are happy to work on correcting bugs, you will often have problems that need to be done, and need to be done with more understanding of the complete system than a contractor can be expected to know in any reasonable timeframe.

    13. Re:They're overanalyzing. by Anonymous Coward · · Score: 0

      Would you please talk to my manager?

    14. Re:They're overanalyzing. by Anonymous Coward · · Score: 0

      hiring based on age, sex and family status isn't exactly legal everywhere.

      Sure it is...you just have to use proxies. Want family people? Make the required hours 8:30am to 4:30pm and ask for 15 years experience. Want youngsters? Make it mandatory to stay until 7pm and offer a sub $100k salary.

      Selecting based on the employee stage in life is as easy as finding legitimate work requirements that are incompatible with the employees you don't want.

    15. Re:They're overanalyzing. by frank_adrian314159 · · Score: 2

      ...this is the philosophy of bad "IT management".

      FTFY.

      --
      That is all.
    16. Re:They're overanalyzing. by Anonymous Coward · · Score: 0

      Leaving "on time" often reduces productivity. If I was in the middle of a knotty problem and I left promptly at five PM when I came back in the morning it could be two or three hours before I was back up to the point where I was the night before. Sometimes, especially for creative people, the best creativity comes late at night. Sadly, today most programmer types aren't really creative, they just plug and chug.

    17. Re:They're overanalyzing. by Stiletto · · Score: 1

      ...and don't get sick or injured to the point where you'd have to use your nonexistent health insurance.

    18. Re:They're overanalyzing. by Anonymous Coward · · Score: 0

      Encourage workers to work on things that they enjoy working on. Hire contractors to deal with the painful crap.

      My work hires contractors to do the easy stuff I'd enjoy working on, spends tons of money on it and gets something back full with so many utterly stupid design flaws I cant help but think to myself "even when I was first starting to program at age 10 I wouldnt have made such a stupid mistake", then forces me to spend years doing the hard part of integrating it without ever letting me rewrite it/replace it, constantly trying to come up with creative solutions to get around problems that should never even exist in the first place.
      Sadly, this is the bestjob I've had in this regard...most others are much worse, because they don't even allow creative solutions, they tell you how to solve the problems which shouldn't even exist in ways that couldn't possibly work. Idiocracy was a documentary, not a prediction.

    19. Re:They're overanalyzing. by cayenne8 · · Score: 1

      ...and don't get sick or injured to the point where you'd have to use your nonexistent health insurance.

      Seriously, not a problem.

      YOu calculate that into the bill rate too, and like everything, you plan.

      When I've done the self contracting gig...I set up a high deductible insurance policy, for catastrophic needs only. That covers heart attacks, serious injury, etc.

      I also set up (since above makes me eligible for it) a HSA, Health Savings Account that I sock away the max (like $3200 a year I think these days) pre-tax. I use that for routine medical needs (dr visits, meds).

      The HSA, unlike a FSA is not use it or lose it, it continues to grow annually, and you can have it in interest growing accounts and even can invest some in the mkt if you want.

      Its called being responsible for yourself.

      And no, it isn't difficult to get that insurance, before Obamacare laws I still got it...even with conditions like extremely high tryglycerides, smoking...etc.

      Remember....it wasn't always on employers to provide insurance for employees.

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    20. Re:They're overanalyzing. by Anonymous Coward · · Score: 0

      Tell this to agile development fanatics and let us know if you survive them afterwards.

      I worked for some company where they loved agile methodology, and while some of agile development ideas I personally found useful most of them were just a long chain of day to day annoyances. Hard to focus on my programming, they want you to program sitting in each other laps, holding hands, open office space so you can be disturbed starting with HR people to sales or whatever departments they might have, etc etc. Thanks God they let me go to the bathroom alone. That is one place where pair programming is unacceptable. Anyway, I left that company with the first opportunity I had. Needles to say I am more happy and productive atm.
       

  11. Don't fill your company with X or Y by Anonymous Coward · · Score: 0

    because it doesn't fit my model of reality and goes against all these cool buzzwords that I just made up.

  12. Garbage, Wrong by salteye · · Score: 0, Troll

    Young, single, childless males are the ones who will dedicate their evenings to making sure not only that things run properly, but that you are in the front of your field. Filling your department with family oriented people is just going to give you a whole bunch of people who will do what they must and anything they need to not to lose their job. If you follow this advice, DO NOT EXPECT TO INNOVATE!

    1. Re:Garbage, Wrong by benjfowler · · Score: 4, Insightful

      Obviously not hiring the right people then!

      All the biggest innovators I have worked with in my current gig are married with kids. One has teenage kids.

      Hiring kids and brogrammers, you end up with a shitload of very clever people (or 'clever', since many have intelligence, but lack knowledge and wisdom). And a mountain of garbage. What you're looking for is people who _aren't_ wet behind the ears, but who actually give a shit about what they do. If they hack Lisp in their spare time, but have a family, they stand a decent chance of being a good hire.

    2. Re:Garbage, Wrong by Anonymous Coward · · Score: 1

      Young, single, childless males are the ones who will dedicate their evenings to making sure not only that things run properly, but that you are in the front of your field. Filling your department with family oriented people is just going to give you a whole bunch of people who will do what they must and anything they need to not to lose their job.

      If you follow this advice, DO NOT EXPECT TO INNOVATE!

      Because, we all know, young single people never act in ways that just favor their career. And never make mistakes from inexperience that an older programmer has learned how to avoid. And never decide to quit suddenly so they can backpack Honduras.

    3. Re:Garbage, Wrong by Anonymous Coward · · Score: 0

      That work ethic is a fast path burnout. That's fine for a company with a 2-4 year lifespan striving for a buyout. But what happens after all the tribal knowledge walks out the door?

    4. Re:Garbage, Wrong by hendrikboom · · Score: 1

      Some creative, innovative youngsters grow up to become creative, innovative parents with children.

    5. Re:Garbage, Wrong by Anonymous Coward · · Score: 0

      Heh... In most cases, they've not refined their thoughts and taught their minds to move in the directions needed to do what you claim.

      Innovation comes from a creative mind- period. Youth isn't the sole source for this- and if you're telling yourself this, you're deluding yourself and you're part of the problem, not the solution.

    6. Re:Garbage, Wrong by Svartalf · · Score: 1

      Meltdown. That's what happens...

      --
      I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    7. Re:Garbage, Wrong by salteye · · Score: 0

      Fine, but then don't discriminate against the others simply because they don't. I'm sure you have much less time than you'd like now. Don't take it out on others.

    8. Re:Garbage, Wrong by Anonymous Coward · · Score: 0

      I like the wet behind the ears youngsters. It's fun to train them right, and they bring in new approaches and technologies I didn't know about or which I can help them refine.

    9. Re:Garbage, Wrong by lgw · · Score: 1

      A group of brogrammers heroically striving 60 hours a week is going to greatly underperform a balanced group working 40 hours a week with great engineering practices. Engineering practices aren't taught in school, they're learned through many years and the experience of many ways of doing things and how each worked out.

      But maybe you're talking about "IT" not "programming"? Work that is IT but not programming is fading - automation always wins in the end.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    10. Re:Garbage, Wrong by Anonymous Coward · · Score: 1

      Garbage here too.

      People with families are dedicated to writing quality code and testing their code to make sure it doesn't break in production and their family evenings aren't interrupted.

      The Brogrammers are just interested in banging out as much code as possible, working evenings, and could give a shit about getting called on the weekend, since they're already working. And they're most likely working because they fixing some shit they broke because of a sloppy refactor they put in because they didn't think the old fart's code, that actually worked, was cool enough.

      That's why 1 Sr. Guy, working 40 hrs/week is actually worth 2 brogrammers working 60+ hours per week.

    11. Re:Garbage, Wrong by ebno-10db · · Score: 1

      One has teenage kids.

      A veritable fossil. Has he been preserved through taxidermy? The fact that "has teenage kids" is considered a mark of extreme age says something about this industry. Someday you may even meet an empty nester or someone whose divorced daughter has moved back in with his grandchild. Them little feet keep the old farts spry.

      Sarcasm aside, I strongly agree with you. The best places I've worked have had employees from new grads to graybeards. There are pros and cons to different ages, and they make a good mix. But of course this factor is never considered when they talk about diversity in the workplace.

    12. Re:Garbage, Wrong by Anonymous Coward · · Score: 0

      If you hack software in your spare time and are sufficiently thoughtful to write that in your CV/resume you have just increased to 100% your chances of making the final interview.

    13. Re:Garbage, Wrong by HeckRuler · · Score: 1

      Ah, nice to see the rampant ageism in the industry hasn't gone anywhere.

  13. Slang isn't always cool. by Jane+Q.+Public · · Score: 0, Flamebait

    "Some other suggestions from the San Francisco video monitoring startup: don't fill your engineering department with young, single, childless males (aka brogrammers)."

    Who's the idiot who came up with "brogrammers"? Sounds like a bunch of gay guys from "da hood".

    1. Re:Slang isn't always cool. by GodfatherofSoul · · Score: 1

      I've never heard brogrammer used in this context without a negative connotation. EVERY time I've heard it used prior is in the context of sexist, discriminating work environments that tend to reinforce homogeneous work forces. I hope that term doesn't generically start referring to single, male programmers.

      --
      I swear to God...I swear to God! That is NOT how you treat your human!
    2. Re:Slang isn't always cool. by Sponge+Bath · · Score: 1

      Who's the idiot who came up with "brogrammers"?

      The sexist leaders of our oppressively matriarchal society. Ha ha, just kidding. It was probably some guy wearing a "Titty Inspector" t-shirt and backwards baseball cap.

    3. Re:Slang isn't always cool. by Zapotek · · Score: 1

      I just stopped reading at that point, he basically belittled every young, single, childless male -- unless I misunderstood and the term "brogrammer" is somehow complimentary. If that's your basic premise then your whole argument is of no value buddy.

      Also, random CEO of random start-up expresses own misguided opinion, everyone better take a knee and listen up.

    4. Re:Slang isn't always cool. by ebno-10db · · Score: 1

      I hope that term doesn't generically start referring to single, male programmers.

      Feeling discriminated against, are we? Fear not. I was once a young single white heterosexual male myself, but given a little time at least one of those things will change. Before you start getting too sensitive, note that the criticism is of places that only hire programmers in that category, not of all people in that category. However, if the bias against brogrammers gets bad enough, you can always file a discrimination suit (or dye your hair gray).

    5. Re:Slang isn't always cool. by Anonymous Coward · · Score: 0

      "Some other suggestions from the San Francisco video monitoring startup: don't fill your engineering department with young, single, childless males (aka brogrammers)."

      Who's the idiot who came up with "brogrammers"? Sounds like a bunch of gay guys from "da hood".

      You mad, bro?

    6. Re:Slang isn't always cool. by Jane+Q.+Public · · Score: 1

      "Flamebait"???

      Come on, modders, you can do better than that. Read my comment again. I didn't insult anybody.

      Um... except the idiot who came up with "brogrammers".

    7. Re:Slang isn't always cool. by russotto · · Score: 1

      I hope that term doesn't generically start referring to single, male programmers.

      The idea of "brogrammers" was a successful attempt to hoax the tech press. Dice being a little slower than the rest, they haven't caught on that it's a hoax yet, and also they don't get the reference ("brogrammers" are programmers who otherwise act like "bros" -- they write code, pump iron, and chug Red Bull. Yes, they're young, single, and male, but that's only part of it).

      I suppose there may be a few cases of life imitating hoax (as with the 5-blade razor) but it isn't any less a hoax.

    8. Re:Slang isn't always cool. by CCarrot · · Score: 1

      I hope that term doesn't generically start referring to single, male programmers.

      Fear not. I was once a young single white heterosexual male myself, but given a little time at least one of those things will change.

      So...sex change, or pigment augmentation? Or just started hanging around in the right nightclubs, maybe? ;o)

      --
      "I love animals! Some are cute, others are tasty, what's not to like?" - Betsy Schroeder, Jeopardy contestant
  14. (aka brogrammers) by Anonymous Coward · · Score: 0

    young, single, childless males (aka brogrammers)

    Yeah? Well fuck you (aka asshole), too!

  15. His Employees Already Win... by MatthiasF · · Score: 5, Insightful

    ...for having a CEO that actually cares about them.

    1. Re:His Employees Already Win... by Anonymous Coward · · Score: 0

      This is more important than the advice. It's not just the CEO. The people you want to retain aren't dumb enough to be fooled by a few free pizzas or sodas if the work environment is toxic, it doesn't matter how much you get paid... unless you are getting Wall Street money.

    2. Re:His Employees Already Win... by able1234au · · Score: 1

      Agree. Most people leave (voluntary) because they are unhappy with their manager. A bad manager can cause a whole lot of damage

  16. 4 years? by Pino+Grigio · · Score: 1

    I've been working as a software developer for the same company for 12. There are 6 other software developers who, apart from 1, arrived before me (1 arrived 1 month after me). Since then, 2 have come and gone. The first came from overseas and inevitably returned there and the second found himself detained at Her Majesty's Pleasure for something or other.

    3 of us are single childless males :).

  17. Maybe good advice, but... by Improv · · Score: 1, Insightful

    Having had a company for 4 years might not be enough to qualify for giving advice people should listen to.

    --
    For every problem, there is at least one solution that is simple, neat, and wrong.
    1. Re:Maybe good advice, but... by benjfowler · · Score: 4, Insightful

      I think he's qualified.

      For conventional small businesses, about half fail in their first year. The fact that he's managed to achieve so much at his age makes him an EXCELLENT person from whom to seek out advice.

    2. Re:Maybe good advice, but... by Anonymous Coward · · Score: 0

      Especially when his advice is illegal when taken at face value...

    3. Re:Maybe good advice, but... by erice · · Score: 1

      Having had a company for 4 years might not be enough to qualify for giving advice people should listen to.

      I've worked for several startups. Four years is long enough to expect some turnover if the headcount is non-trivial. The pointed questions to ask are:

      1) How many employees?
      2) What kind of roles to they serve?
      3) Is the company obscuring turnover by keeping traditionally high-turnover roles like sales as contractor?

    4. Re:Maybe good advice, but... by Svartalf · · Score: 1

      After seeing how several of the big boys run things, there's only really a few that actually have any better handle on it than those that've only been around for 5 years or less.

      How many businesses fail in the first year? Most of them. Honestly, some of that "sound" advice you're hinting at did well for Motorola, TI, and a few others- not.

      If you look at some of the other companies still doing well in these times, they're doing similar things. First rule of thumb: Put your employees FIRST. They will put your customers there for you. If they're not happy, they'll screw you in so many differing ways it'll be like death by ten thousand paper cuts. All this guy's talking to is this very thing. The gritch about the free dinners thing depends on situations, company, and the like- if it's not a 5-7 days a week thing, and only off-and-on done, it's a positive thing (Otherwise, he's dead on...). I'd have to say the brogrammer gritch is closer to the truth than most would like to own.

      --
      I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    5. Re:Maybe good advice, but... by Colonel+Korn · · Score: 1

      I think he's qualified.

      For conventional small businesses, about half fail in their first year. The fact that he's managed to achieve so much at his age makes him an EXCELLENT person from whom to seek out advice.

      I don't disagree that he may have great advice or that the advice in TFA may be great, but you've given an example of a fallacy that bothers me so I think I'll point it out.

      Success doesn't equal good choices. My favorite example is in the stock market. Generally the market goes up and therefore the average investor will be slightly in the black. Let's assume we pick 64 investment bankers who work for large firms and can therefore make large, leveraged bets where the outcome is roughly equally likely to be a large gain or a large loss. Now let's have them make 6 such random bets on the same 6 investments, with no broker having the same betting pattern as any other broker. One broker will have been right 6 times and made a vast fortune. The way the investment banking field works, he'll have made millions in bonuses and secured his future. He can write books. One broker will have been wrong 6 times and he'll be fired in disgrace, despite the fact that his 6 bets were just as likely to succeed as the big winner's. The 62 bankers in between will have a variety of outcomes.

      There are so many players in the stock market making decisions based on exceedingly incomplete information and guesswork, and for that matter in small businesses, that we actually have a decent random distribution of choices. Picking one of the big winners out of such a vast pool often just results in picking someone who got lucky. For the CEO in TFA, I think that his business's success is a lot less impressive than his employees' loyalty.

      --
      "I zero-index my hamsters" - Willtor (147206)
    6. Re:Maybe good advice, but... by lgw · · Score: 1

      Especially when his advice is illegal when taken at face value...

      I think you've got that backwards. The programming workforce includes all types, but specifically seeking only young male workers (because you can con them into longer hours) is likely running afoul of local laws.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    7. Re:Maybe good advice, but... by lgw · · Score: 1

      First rule of thumb: Put your employees FIRST. They will put your customers there for you.

      As I once heard it: "My job as a CEO is to take care of my stockholders and make them happy. The best way do that is to take care of my customers and make them happy. The best way do that is to take care of my employees and make them happy."

      --
      Socialism: a lie told by totalitarians and believed by fools.
  18. Brogrammer... by Anonymous Coward · · Score: 0

    Never use the word brogrammer... Ugh who comes with with these terms? Every body goes through stages, I had my 20's when I didn't mind putting in hours, now in my 30's with a family time with them is more important than establishing a career which is what I did in my 20's. So you find a company that is more family friendly, not a startup.

    1. Re:Brogrammer... by fuzzyfuzzyfungus · · Score: 1

      A 'brogrammer' is a specific subset of young male programmers generally. Anybody using it as a synonym for 'young, probably unmarried, male programmer' is doing it wrong; but there is a recognizable population(unfortunately) that it fits pretty well.

    2. Re:Brogrammer... by Anonymous Coward · · Score: 0

      Brogrammer was a joke, that many fucking geeks were too stupid to actually get.

  19. Just Like... by camperdave · · Score: 1

    "no one who has joined the 4-year-old company has ever left"

    Just like the CIA.

    --
    When our name is on the back of your car, we're behind you all the way!
    1. Re:Just Like... by Hognoxious · · Score: 1

      Or the Hotel California.

      diddle diddle DEE doo doo diddle diddle doo...

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  20. Retention rate isn't everything by Diddlbiker · · Score: 1

    Without RTFA, not sure if retention rate is the be-all-end-all. I can easily get a retention rate of 100%--hire all the incompetent idiots nobody else wants. They'll never leave my company, because they'd be out of a job. Voila!

    Not saying this guy is doing it wrong; just saying that retention rate alone isn't that much of a useful indicator.

    1. Re:Retention rate isn't everything by Bigby · · Score: 1

      That was my thought. He is keeping 100% of the good developers, but also keeping 100% of the crap.

    2. Re:Retention rate isn't everything by arglebargle_xiv · · Score: 1

      It also depends on the size of the company. For our first few years we had a 100% retention rate, but the fact that we were only half a dozen people helped with that. Now that we're 400-odd, there is some churn. Not because people are bailing, the company is still a great place to work but people move to other cities, get married, whatever.

    3. Re:Retention rate isn't everything by Anonymous Coward · · Score: 0

      You will end up with a 0% retention rate because you and everybody else will be gone.

  21. Re:100 percent of 1 is 1 by XxtraLarGe · · Score: 3, Informative

    how many employees are there? just him?

    FTA:

    Rather, it's that people just like to stay: Dropcam has hired 30 workers to date, and it's never had to give a single going-away party.

    --
    Taking guns away from the 99% gives the 1% 100% of the power.
  22. And here is where I stopped reading by SmallFurryCreature · · Score: 4, Interesting

    That’s why there are no free dinners at Dropcam—around 6:00 pm the company

    I am sorry, at WHAT time? Ever heard the song 9 to 5? 9 to 5! Dinner is at 6 o'clock. Having to stay at work till six and then the commute means you won't be home close to 8. Kids will be in bed by that time. Dinner will be waiting in the oven.

    A GOOD going home hour is 5... oh wait. that is rush hour, means you leave "early" and arrive home just as late. Do you know what would be even BETTER? A company with FLEXIBLE hours and a max 8 hours on the workfloor. Now THAT would be a social company. Even better if you can take a half day off to deal with plumbers and other stuff.

    Nobody left in the last 4 years. Geez, I wonder why. An economy down the drain may have something to do with it.

    Don't get me wrong, a company that doesn't expect unpaid overtime in exchange for a greasy cold pizza (especially if there is no pizza) everyday gets pretty old pretty fast. But closing the doors at 6 doesn't show much of an improvement. You are still putting in a long day, except now you don't get free dinner at the end of the day. What about those without a family for who a company dinner saves time not having to cook for themselves?

    It is telling that the article calls him a wunderkind idealist and then fails to list any idealistic thing in the next few paragraphs.

    --

    MMO Quests are like orgasms:

    You may solo them, I prefer them in a group.

    1. Re:And here is where I stopped reading by Anonymous Coward · · Score: 0

      Then again it doesn't say in the article that EVERYONE leaves at 6. There may be some who leave earlier than that, and those who leave at 6 may be a 10 minute bike ride from home. You don't really have any way of knowing that just from the article, so you're overreacting "slightly",,,

    2. Re:And here is where I stopped reading by AdamHaun · · Score: 5, Insightful

      Having to stay at work till six and then the commute means you won't be home close to 8.

      A two hour commute one way? If you're spending four hours a day commuting you're living in the wrong place.

      --
      Visit the
    3. Re:And here is where I stopped reading by lgw · · Score: 1

      My commute was recently an hour each way - then I finally realized what a dick I was being to myself, and now it's 5 minutes each way, 10 in the worst traffic. Sure, I took a minor paycut to make the change, but I come out far ahead getting nearly 2 hours back.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    4. Re:And here is where I stopped reading by Anonymous Coward · · Score: 0

      Nowhere in the article does it say they start at 9am. If they do and give an hour for lunch, or start at 10am, it's still an 8 hour workday.

    5. Re:And here is where I stopped reading by Anonymous Coward · · Score: 0

      Having to stay at work till six and then the commute means you won't be home close to 8.

      A two hour commute one way? If you're spending four hours a day commuting you're living in the wrong place.

      When you have a mortgage and kids, you take the work available. Not everyone gets a job on their doorstep, not everyone lives alone like you dweebs.

    6. Re:And here is where I stopped reading by Anonymous Coward · · Score: 0

      Additionally, kids in bed at 8? WTF?! My kids get a real childhood so it's "come indoors" when the street lights come on and then bed sometime after that. That "attrition" rate is unbelievable actually -- good economy or bad. I think you're just being bitter somehow and had to comment to say something negative just to do it (like I did in my first statement too)

    7. Re:And here is where I stopped reading by admdrew · · Score: 1

      Not responding to the AC, but I would amend your comment slightly as "If you're spending four hours a day commuting, and bitching about it, you're living in the wrong place."

      Uprooting a family to reduce commute time isn't always realistic, but it's still technically a decision you have the ability to make. If having a job 2 hours away is what you need to do to make ends meet, you should realize that's your choice, and you should live with it without complaining to/blaming others.

    8. Re:And here is where I stopped reading by Anonymous Coward · · Score: 0

      In the Bay Area a hour to hour and a half commute is the norm.

    9. Re:And here is where I stopped reading by Stiletto · · Score: 1

      When you work in a high cost-of-living area like Silicon Valley, you don't really have much choice about your commute. Anywhere affordable to mere mortals is 1-3 hours away.

    10. Re:And here is where I stopped reading by Anonymous Coward · · Score: 0

      A two hour commute one way? If you're spending four hours a day commuting you're living in the wrong place.

      Are you familiar with the Silicon Valley / Bay Area region? If not, let me shed some light on something that happens here. Pardon my language as I get pretty worked up about this at times.

      Houses here cost a fuck load and for no justified reason other than "we can :D :D :D :D". In the Mountain View and Palo Alto areas, houses build in the 1940s (sometimes 70s if you're lucky often go for US$600K, while new houses tend to go for over $900K (often US$1.2M). "Used" properties tend to have old walls (excessively hot during the summer, can't hold heat in during the winter, and are paper thin), often have single-pane windows, old plumbing, and electrical that consists of maybe 3 circuits for an entire house (at only 10A each, barring kitchen which probably has 15A); anything advertised as "remodelled" or "renovated" just means they fixed one of those things. Property owners/landlords here do not upgrade -- ever. Their goal is to make money off potential buyers or renters, not to break even in the long run. Regardless of new vs. old, these properties sell for about $200K lower than what I quoted. Point being: even if you're working at Google and making $150K/year, that's still a shitload of money to put down on a house, especially when there's no guarantee that it's an "investment" (what makes you think someone is going to want to rent it (effectively paying your mortgage + then some) if you move out?). Be sure to consider the fact that there's no guarantee that you and/or your spouse will have a job 2 years from now, given how the job market is and how companies act around here.

      The people that have resided here for a long time (either Bay Area natives or folks who have lived here for at least 15 years) know this fact (FYI: I'm one of the latter, I've lived here a total of 16 years). So buying/staying local is no longer an option. Renting means either getting an a) "old" house (see above), or b) apartment (most of which are identical to old homes, barring certain places which do have newer setups and the rent is usually $3000/month (higher than a mortgage), and we all know what MDUs are like -- here's one such place in case you think I'm making these numbers up). This puts people between a rock and a hard place, where the only option becomes: buy a house outside of the Bay Area.

      You can get a brand new home (as in brand-fucking-new) in outlying areas such as Brentwood, Patterson, or (god forbid) Modesto for a 1/3rd or 1/4th of the above. The trade off is is a commute of 1.5 hours each way, and that includes "average" traffic but not major traffic jams (try 2 hours for those). I personally know of at least two dozen people who commute from those cities to the Bay just for work, and 2 more who commute from Sacramento (that's 2 hours one way, on a really good/lucky day -- those folks have to do things like drive here on a Monday morning, stay with relatives, then return to Sacramento on Friday to spend time with their families over the weekend).

      Lots and lots and lots of people do this (I imagine the Sacramento thing is more rare, but the former is quite common now). Those who do stay local will tell you how lucky they are to have found a special deal or "knew someone who knew someone" or some other such story -- basically some way that allowed them to find a really good place for an amazingly low (i.e. reasonable) price.

      What created all of this was the technology boom from the 70s going forward, especially the tech bubble in the 90s. The bubble bursting many years later had a awful effect in this region, where many other aspects of living (like property costs) did not adjust accordingly, mainly because it didn't have to (side note: part of me wonders if this is one of the reasons why San Francisco has rent control). So now there's a complete imbalance between the cost of property vs. the cost of living vs. quality of an investment vs. commuting. It wasn't like this in 1996.

  23. Re:Slashdot = intellectual vomit by AaronLS · · Score: 4, Insightful

    Please do and leave it that way, because no one with a productive/meaningful life cares anything about your trivial host file ramblings.

  24. Do you even code, bro? by HeckRuler · · Score: 0

    don't fill your engineering department with young, single, childless males (aka brogrammers).

    First off, "brogrammer" is one of those moderately new phrases that hasn't been fully defined yet. I always thought it was any code shop whose members were close friends and did stuff together outside of work. It just coincodence that young single childless programmers don't have established roots and have time to go for a beer after work.
    So let's break it down:
    -Young: No experience means entry-level pay. You REALLY need at least one experienced guy, but surrounding him with minions and padawans isn't a bad business descision
    -Single/childless: No roots means that they (statistically) don't have anything better to do after work... than work. If a manager can employ a guy to do 80 hours for 40 hours of pay, they will probaly do so. Dicks.
    -Male: Sadly, sexism in the industry is pretty well established. No good reason for it. There ARE reasons, but none of them good.

    Keep your business model simple by making actual stuff that you can sell for a profit.

    Did you just associate programming with "actual stuff"? Really?

    And don't hire assholes.

    Wow, what a revelation. Now, this might actually be news for people who are used to hiring salesmen, but for code shops? Naw.

    Because Dropcam has a 100 percent employee retention rate — no one who has joined the 4-year-old company has ever left.

    Which anyone can do if they get a group of dead-end-career types who know they're lucky to have a job, any job. The dead sea effect is well known, this guy might just have hit those salty sailors early. He probably does have a good point when it comes to retention and the common family-man sort. Once you have roots it's harder to up and leave for greener fields.

    1. Re:Do you even code, bro? by lgw · · Score: 2

      -Male: Sadly, sexism in the industry is pretty well established. No good reason for it. There ARE reasons, but none of them good.

      Sexism is common in workplaces stuffed with mostly young male workers (or mostly young female workers). Hiring a more representative crowd tends to put a damper on "bro culture".

      --
      Socialism: a lie told by totalitarians and believed by fools.
  25. 100 percent rention a good thing? by Anonymous Coward · · Score: 0

    Having 100 percent retention is not necessarily a good thing either. From what I learned, too little retention is bad (for obvious reasons) but a very high retention rate can also be a sign that you are being too lenient on your employees and that may cause them to take advantage.

  26. Steve Jobs? by Tablizer · · Score: 2

    don't hire assholes

    Apple would never exist

    1. Re:Steve Jobs? by Anonymous Coward · · Score: 0

      don't hire assholes

      Apple would never exist

      You're acting like that would be a bad thing?

    2. Re:Steve Jobs? by mark-t · · Score: 1

      Woz isn't an asshole. And he never really "hired" Jobs. They cofounded the company.

  27. Food rewards by Animats · · Score: 4, Insightful

    Google uses dinner as a form of manipulation. It's considered bad form to eat dinner at Google and then go home. It's like training animals with food rewards.

    1. Re:Food rewards by Anonymous Coward · · Score: 0

      It's considered bad form to eat dinner at Google and then go home.

      How do you know?

    2. Re:Food rewards by Anonymous Coward · · Score: 0

      This is true in my office. No one checks or anything, but it's made clear that the dinners are meant for people who are working late.

    3. Re:Food rewards by Anonymous Coward · · Score: 0

      I've never quite understood why people would want free food. Free coffee, pop, water I understand, it's cheap enough and it's a time saver, but food? What if I don't like the food being served, then I feel cheated, what if the quality goes down after a year, I won't change jobs just because of the food but I'd still feel cheated. Just give me a decent pay and I'll bring food, or eat what I like at the place I like, or for a late night stint order in what I like.

      So yes, I totally agree with you, people who work for free food are just submitting themselves to unnecessary control.

    4. Re:Food rewards by Anonymous Coward · · Score: 2, Informative

      As a Googler... what? There's plenty of us that eat dinner then go straight home.

    5. Re:Food rewards by Anonymous Coward · · Score: 0

      ... and, as a Googler, I just don't eat dinner at work and instead go home early. Problem solved.

      I don't understand all these people that claim it's manipulation in some way - it's an optional thing. Nobody is forcing you to eat breakfast, lunch, and dinner at work, but the option is there if you want it and your schedule is compatible with it.

    6. Re:Food rewards by RightSaidFred99 · · Score: 1

      I heard they also use pay as a form of manipulation. They give you money to trick you into coming in to work. Those bastards!

    7. Re:Food rewards by PuZZleDucK · · Score: 1

      ...and then comment anonymously? :p

      --
      Can a person program a new solution to a problem? Why should anyone be able to stop such a thing? -Richard Stallman
  28. Let me guess which group represents the largest of by firex726 · · Score: 1

    > Some other suggestions from the San Francisco video monitoring startup: don't fill your engineering department with young, single, childless males (aka brogrammers).

    Let me guess which group represents the largest of new programmers out there?

  29. Re:100 percent of 30 is 30 by hendrikboom · · Score: 2

    30.

  30. Re:100 percent of 1 is 1 by AuMatar · · Score: 3, Interesting

    So in other words statistically insignificant. That's in line with all the startups I've worked for- we didn't lose people unless we fired them with very few exceptions.

    --
    I still have more fans than freaks. WTF is wrong with you people?
  31. 100 percent retention not always good by Anonymous Coward · · Score: 0

    100 percent retention could also mean that you retain bad employees.

  32. Wha the actual fuck? by glwtta · · Score: 1

    A young, single male is an automatic 'brogrammer' now?

    --
    sic transit gloria mundi
  33. hey jerkface by verbatim · · Score: 0

    don't fill your engineering department with young, single, childless males (aka brogrammers).

    Leave the bigotry at home, please. this isn't the 1920s and not all of us subscribe to certain puritan notions of "family".

    I would otherwise agree with the idea that "going home" to rest is better than "resting at work" (because as long as you are accessible by work, you are not fully resting and free from it).

    --
    Price, Quality, Time. Pick none. What, you thought you had a choice?
    1. Re:hey jerkface by Anonymous Coward · · Score: 0

      Even in his definition of family, he alienates a growing portion of the workforce. Many are deciding to have children later in life, resulting in lots of "childless males".

    2. Re:hey jerkface by ilsaloving · · Score: 4, Insightful

      I'm not sure how you managed to read all that from that one sentence.

      I read it as, "We don't want a bunch of inexperienced kids who don't necessarily know how to code, and don't understand anything about what real life is like."

      I think this is a great sentiment, especially considering that in silicon valley is undergoing an epidemic of age-ism.

      He didn't say anything about discriminating against anyone who doesn't fit some hetero-normative world view. He wants people who actually have a life outside work hours. You know, the kind of people whose lives revolve around more than just pizza, cola, and Call of Duty.

    3. Re:hey jerkface by Anonymous Coward · · Score: 0

      He wants people who actually have a life outside work hours.

      Yeah, so they can browse Facebook and not actually work, great choice there, buddy.
      No, really, do explain why a thing he should have no business with is so important.

    4. Re:hey jerkface by verbatim · · Score: 1

      But you're the one reading into it.

      At face value, the statement clearly implies that young, married, males with children are somehow more valuable. His argument talks about going home to rest, not how skilled they are.

      Disclosure: I'm a straight, single, over 30 (old) male without children (or the desire to procreate).

      --
      Price, Quality, Time. Pick none. What, you thought you had a choice?
    5. Re:hey jerkface by ebno-10db · · Score: 1

      silicon valley is undergoing an epidemic of age-ism

      Do you think that it's worse than it used to be? And if so, why do you think that? I ask this out of curiosity more than skepticism.

    6. Re:hey jerkface by Anonymous Coward · · Score: 0

      You're proving the OP's point.

      I'm a young, single, childless male, and I'm definitely not a brogrammer. I do have a life outside work hours.

      The bigotry is in automatically associating "not seeking to found a family at 22" and brogrammers (i.e. immature, childish).

      (heh, captcha: "puberty")

    7. Re:hey jerkface by Xest · · Score: 1

      "He wants people who actually have a life outside work hours. You know, the kind of people whose lives revolve around more than just pizza, cola, and Call of Duty."

      But why? It's not like there's any evidence that demonstrates these people as being generally worse employees. It's just mindless stereotyping.

      I'm sure we all have personal anecdotes of such people being useless, but I know that I at least have just as many anecdotes of married individuals knocking off early "for the kids" and leaving a job half done whilst the single guy is left to finish off the job and clean up the outstanding mess, or simply not giving a shit generally because said person is just after an easy ride to retirement at that point in their life and not bothered about doing a good job to maximise career potential.

      You get bad workers in all demographics, stereotyping full stop is stupid and I agree with the GP, the guy in TFA is an idiot for doing so. If the best candidates about all happen to be "brogrammers" (whatever the fuck that even means) then so be it. Don't write them off if they're the best candidates just because this idiot has some kind of ageist bias against younger candidates himself.

    8. Re:hey jerkface by Anonymous Coward · · Score: 0

      I read it as, "We don't want a bunch of inexperienced kids who don't necessarily know how to code, and don't understand anything about what real life is like."

      I think this is a great sentiment, especially considering that in silicon valley is undergoing an epidemic of age-ism.

      My irony meter just exploded. You understand that ageism isn't only when old people are ragged on, right?

    9. Re:hey jerkface by ilsaloving · · Score: 1

      Yes, I do understand that. And I will concede the point as soon as you can demonstrate that there is a systemic alienation of young people for tech jobs.

    10. Re:hey jerkface by ilsaloving · · Score: 1

      I do think it's worse, but not in and of itself. It's a symptom of an increasing amount of general (legal) abuse that corporations are perpetuating on their employees, and society in general.

      I don't want to repeat, but here's a comment I just wrote in reply to someone else:
      http://slashdot.org/comments.pl?sid=3677925&cid=43546149

  34. How did he find out? by magarity · · Score: 0

    Has it occured to this person that he's about to be hit with a class action suit by all the single people who applied and were not hired? How do you even find out if people are married with children during the interview without asking directly, which should be a dead giveaway to all the singles who are turned down? Here's a hint everyone: if asked during an interview "are you married/party member/religious?" just respond with "which do I need to be to be hired here?" Whatever the answer, reply affirmative unless the answer is "doesn't matter" in which case echo back "then it doesn't matter".

    1. Re:How did he find out? by ewieling · · Score: 1

      "single" and "unmarried" are not protected classes and so it is not illegal to discriminate against them. Smokers and fat people are also not protected classes at a federal level, though some states have made them so.

      --
      I really shouldn't have used someone else's email address for this account.
    2. Re:How did he find out? by dgatwood · · Score: 1

      Wrong question. The correct question is, "How many years of experience do you have?" If the answer is more than 10, the probability of the person being married with kids begins to climb fairly rapidly. You can, therefore, ensure a more balanced workforce by not hiring people straight out of college, or at least by setting hard limits on the number of junior coders that you hire.

      Unfortunately many tech firms do precisely the opposite, setting low limits on the number of senior engineers that they hire (because of the high cost per employee) and filling the rest of the department with new college hires. In the long run, this tends to result in a large volume of poorly written code that has to be thrown away every few years and rewritten from scratch because they didn't have a senior architect working on it.

      It also results in accusations of age discrimination, because most companies won't hire senior engineers as junior engineers, and the number of senior engineer positions is limited, effectively forcing a sizable percentage of people out of the market entirely, decades before they're ready to retire. If, instead, the industry hired more senior people and fewer young people, the number of people going into the field would decrease to match the available jobs, and you'd have a much healthier job market for everyone.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    3. Re:How did he find out? by Anonymous Coward · · Score: 0

      Stupid people were on the watch list for a while, but their lobbying efforts proved ineffective.

      (Obligatory Dogbert quote)

    4. Re:How did he find out? by Anonymous Coward · · Score: 0

      I have 13 years of experience in my field, I'm still a (relatively) young, single male.

    5. Re:How did he find out? by magarity · · Score: 1

      http://www.eeoc.gov/facts/qanda.html :

      The Civil Service Reform Act of 1978 (CSRA) contains a number of prohibitions, known as prohibited personnel practices, which are designed to promote overall fairness in federal personnel actions. 5 U.S.C. 2302. The CSRA ... It also provides that certain personnel actions can not be based on attributes or conduct that do not adversely affect employee performance, such as marital status and political affiliation.
      ...
        Note: Many states and municipalities also have enacted protections against discrimination and harassment based on sexual orientation, status as a parent, marital status and political affiliation. For information, please contact the EEOC District Office nearest you.

    6. Re:How did he find out? by dgatwood · · Score: 1

      That's the difference between an anecdote and a statistic. More than 80% of people are married by age 40, statistically, versus (currently) only 21% of people under 30. Assuming you enter the job market at age 22, this means that the statistical probability of someone being married increases very rapidly beginning in the mid-20s or early 30s.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    7. Re:How did he find out? by ewieling · · Score: 1

      Civil Service Reform Act of 1978 protects federal civilian employees onlyâ€"not private sector workers. When I wrote "at a federal level" I meant federal law applying to private employees, not federal law applying only to federal employees.

      --
      I really shouldn't have used someone else's email address for this account.
  35. Re:100 percent of 1 is 1 by dragon-file · · Score: 1

    That's because they cant get away. They are literally chained to their desks. They dont get free breakfast, lunch or dinner but they do get to spend time with their families. By spend time I mean they have visitation hours.

    --
    Whenever a player quits EVE to go play WoW, the Average IQ of both games increase.
  36. a career oriented workplace by Anonymous Coward · · Score: 0

    with regular shifts and work weeks, no forced OT, traditional benefits, decent pay, treat workers like people.. get long term stability.. imagine that. what a novel idea. too bad most companies dont do that anymore.

  37. Brogramming -- a direct result of Dunning Kruger by flarb936 · · Score: 3, Interesting

    The proverbial "brogrammer" is the only type of programmer your average valley C-level Dunning-Kruger sufferer can relate to.

    --
    ralphbarbagallo.com
  38. Uh? by Anonymous Coward · · Score: 0

    So some guy nobody has ever heard of before, who made some company and product nobody has ever heard of before, who has no employees, makes a statement about how he is the greatest hiring genius, and it gets to the frontpage of slashdot? The fuck?

  39. Excuse me? by Anonymous Coward · · Score: 0

    young, single, childless males (aka brogrammers)

    Can we address the fact that's not what the term "brogrammers" refers to, at all?

  40. Retention. by fahrbot-bot · · Score: 1

    Dropcam has a 100 percent employee retention rate — no one who has joined the 4-year-old company has ever left.

    Not a surprise in this crap economy. How many have been fired? In the '80s I worked for a very small company with an extended 100% retention rate; nothing lasts forever.

    Otherwise, I generally agree with the sentiment. As for "brogrammers," there's no evidence that young, single, childless males are better than other combinations and I'd argue that herd ("gaggle" -- "braggle"?) of them is a recipe for disaster. Varied experience and perspective are more helpful in the long run.

    --
    It must have been something you assimilated. . . .
  41. Re:100 percent of 1 is 1 by MickyTheIdiot · · Score: 1

    everyone they canned they freaking hated.

  42. Re:Slashdot = intellectual vomit by chargersfan420 · · Score: 5, Funny

    Slashdot is a .org.

  43. the guy reads like a neoconservative by nimbius · · Score: 4, Interesting

    once you take away the "works in silicon valley" and "startup." he says dont hire assholes but then goes on to tout "ethical fiber" as a hiring qualification. what even is that? You dont want a bunch of "single childless males" but what about childless women? as a gay male, is a heteronormative marriage a job requirement for me to work here? sure, people can be hit-or-miss socially but thats why you have harassment and discrimination courses, and adhere to them.

    he says he wants a family friendly company that supports paternity and maternity leave but in california those arent things you decide to "do" for employees, theyre state law. saying you're "really diverse" just because you have married couples working for you fails on so many levels to understand what diversity in the workplace means. yes ive worked for startups that buy out bars and clubs for the night, but they also give out baseball and movie tickets too. my last startup work traded in the nightclub perk for a bowling alley because they listened to their employees instead of making vague generalizations about how family friendly or unfriendly the workplace perks needed to be.

    he doesnt buy dinner for the company, which is fine. working weird hours in IT means you've alienated my entire shift by robbing me of a breakfast that for you is a dinner. not buying dinner doesnt inherently prevent people from working late. Making intelligent business decisions like purchasing new hardware based on my MTBF and MTTF calculations instead the cost avoidance of making me work 90 hour weeks failing over infrastructure will keep me from working late.

    --
    Good people go to bed earlier.
    1. Re:the guy reads like a neoconservative by moeinvt · · Score: 1

      I think he probably meant white, heterosexual, non-disabled, single, childless males who don't have military experience.

      If you're in a "diversity" bucket, I'm sure that it's all cool.

    2. Re:the guy reads like a neoconservative by ebno-10db · · Score: 1

      I think he probably meant white, heterosexual, non-disabled, single, childless males who don't have military experience.

      My, my. programmers are obviously very sensitive about challenges to their undeserved high ranking in the white male heterosexual areproductive same-abled refuse-to-serve-their-country hierarchy.

    3. Re:the guy reads like a neoconservative by Anonymous Coward · · Score: 0

      You sound like an asshole.

    4. Re:the guy reads like a neoconservative by Anonymous Coward · · Score: 0

      His recruitment/firing criteria will never hold in an employment court of law. It's pure discrimination, nothing to do with your talent, education, experience and ability to work. I mean, let's say you go from married to divorce, should you be worried about getting fired at Dropcam. And what the heck is Dropcam, if not a new kid who hasn't even been round the block (once) and is already preaching to others like an arsehole.

  44. Huh? by Type44Q · · Score: 1

    I'm not sure the words "beef" and "dinner" were the best choice to use in the headline... :p

  45. Shut up and take my money by ilsaloving · · Score: 3, Interesting

    An honest to god company that
    a) doesn't trying to abuse it's workers,
    b) hires normal people who are decent workers but also have lives outside the office

    I don't need a camera. I just want to send them money.

    1. Re:Shut up and take my money by RightSaidFred99 · · Score: 1

      I'm curious as to the moral goodness you seem to apply to b). It would seem you feel that people who are decent workers and work a _ton_ of hours don't deserve jobs? We are truly in the backwards days of yore.

    2. Re:Shut up and take my money by ilsaloving · · Score: 1

      Actually, people who work a _ton_ of hours ARE moving backward to the days of yore. As in, the days of serfdom and slavery. The fact that you consider this normal and acceptable tells me that you either don't know jack about history, or you're aiming to be in a position of power (if you're not there already) where you can abuse others.

      There's nothing wrong with working long hours. But that should be the exception, not the rule. One good thing unions did for us was establish reasonable limits on what employers should expect of their workforce, so that workers could still have lives.

      But this is all being eroded by companies that are doing everything they can to bring down the quality of life for employees. They are driving down wages, while driving up the amount of work to be done, all the while making record profits. You DO realize, that the reason companies favor young workers is NOT because they're better, right? Or that there is somehow something inherently better about working absurdly long hours?

      Young single males, as a general demographic:
      -have the energy to work longer hours,
      -are willing to tolerate longer hours because they don't have have family pressures,
      -are cheaper because they work for less (because they don't know any better),
      -are cheaper because the cumulative results of living unhealthily hasn't yet bit them in the ass

      You'll note that nowhere in that list do I state anything resembling quality of work. And I will note that even THAT isn't enough, which is why they're pushing so hard to increase the H1B quotas. Overseas workers arn't necessarily better, skill-wise, than domestic workers. But they work even that much more cheaply, and as a bonus you can just revoke their visa and send them back again when you don't want them anymore, with no repercussions.

      And all the above is why I'm applauding Dropcam. Based on the information we have, it sounds like entire *mindset* is different, where they value their employees rather than treat them as cattle, to be used and abused and then tossed aside when they won't put up with the abuse. Which is unlike an increasing number of modern MBA-mangled corporations that, despite their bubbling marketing, treat people (employees AND customers), like meat for their grinders. Fantastic examples include Electronic Arts and Goldman Sachs.

      My current employer is such a place. And you know what we have? Employees that are loyal. Employees that *care* about the quality of their work. Employees that work extended hours, when needed, not because they're required to, but because they *want* to.

  46. No one who has joined the company has ever left... by Anonymous Coward · · Score: 0

    "...ALIVE!!!.."

    (Goes into mad Vincent Price laugh as the lights fade...)

  47. Ford is irrelevant to a startup by TheMathemagician · · Score: 1

    I doubt Henry Ford gave his workers an equity stake in the company and the chance to make millions in a few years when he was doing this research that proved you can only get 40-50 productive hours/week from an employee. Probably paid them a nickel per hour extra as overtime.

    1. Re:Ford is irrelevant to a startup by ebno-10db · · Score: 1

      [Ford p]robably paid them a nickel per hour extra as overtime.

      You've obviously spent too much time brogramming and not enough reading history. Before he introduced the assembly line, Ford paid the going rate for industrial labor. After, he added a bonus that roughly doubled people's pay. No, he didn't do it out of the goodness of his heart, but as a retention bonus to avoid the high turnover and absenteeism that the boredom of the assembly line caused. Still, not bad for unskilled or semi-skilled workers in an era when dying on the job usually meant not getting paid for the full day.

    2. Re:Ford is irrelevant to a startup by twisted_pare · · Score: 1

      FWIW: Ford cared a great deal about his employees. He didn't just want them to work 40 hours a week. He wanted them to have balanced lives, nice homes and happy families. Had incentivized the whole bit of it too and even sent inspectors to make sure it was working in peoples' homes. He was not just a slave driver. Frankly, he was fairly in line with TFA.

      --
      HTFU
    3. Re:Ford is irrelevant to a startup by TheMathemagician · · Score: 1

      My point remains that an assembly line worker at Ford had a very different incentivisation scheme to a presumed equity holder at a small start-up.

  48. Dumb advice by moeinvt · · Score: 0

    How many tech companies, (or IT departments of non-tech companies) have you ever worked at? How many of those places would not be temporarily (or permanently) crippled if they suddenly got rid of their young, single male employees?

    Stick your drop-cam up your arse 'bro'.

    1. Re:Dumb advice by ebno-10db · · Score: 1

      Wow, are you people touchy! This is funny. I've heard fewer complaints at a lesbians of color left-handed veterans conference.

  49. Re:100 percent of 1 is 1 by ShanghaiBill · · Score: 0

    That's in line with all the startups I've worked for- we didn't lose people unless we fired them with very few exceptions.

    It also isn't clear that "retention rate" is an important metric, or even if it is a positive thing. The employee "churn" in Silicon Valley is often mentioned as a positive feature, because it leads to cross fertilization of ideas. It is not good for the overall economy for employees to stay in jobs that are a poor fit.

    I have worked in 80 hour/week companies and I have worked in 9-5 companies. The latter were nice, but also less successful. A VC once told me that before he invests in a start-up, he drives by their offices at 9pm on Friday night. If the parking lot is empty, that company is going to fail.

  50. Re:100 percent of 1 is 1 by Anonymous Coward · · Score: 0

    A company of 30 employees has not lost an employee in its 4 years of existence. According to the US BLS, the median tenure is 4.4 years. So he has a small sample of people who are already below average in terms of their duration with his company.

  51. Re:100 percent of 1 is 1 by TWiTfan · · Score: 4, Insightful

    A VC once told me that before he invests in a start-up, he drives by their offices at 9pm on Friday night. If the parking lot is empty, that company is going to fail.

    Isn't that a self-fulfilling prophecy? I mean, if every VC demands this, then of course every company not meeting these standards will fail--because they won't be able to get any venture capital funding.

    --
    The cow says "Moo." The dog says "Woof." The Timothy says "Thanks, valued customer. We appreciate your input."
  52. Re:100 percent of 1 is 1 by ZombieBraintrust · · Score: 2

    No mention if his company is making profits either. Easy to keep employees with high payroll based on venture capital debt.

  53. 100% retention rate by Anonymous Coward · · Score: 0

    Hotel California, now without breakfast, lunch, and dinner!

  54. Re:100 percent of 1 is 1 by tool462 · · Score: 5, Funny

    Depending on the quantity of VC available, it could be profitable to rent ~20 cars and park them in your lot overnight.

  55. The Firm by moeinvt · · Score: 1

    Not one single bachelor works at The Firm. They encourage children because children promote stability. Also, nobody has ever left The Firm(alive that is).

    Maybe "Dropcam" is just a front for some incredibly lucrative illegal business and the employees are blackmailed into staying?
    I sort of doubt he'd be giving interviews and drawing publicity to himself if that were the case however.

    1. Re:The Firm by gl4ss · · Score: 1

      Not one single bachelor works at The Firm. They encourage children because children promote stability. Also, nobody has ever left The Firm(alive that is).

      Maybe "Dropcam" is just a front for some incredibly lucrative illegal business and the employees are blackmailed into staying?
      I sort of doubt he'd be giving interviews and drawing publicity to himself if that were the case however.

      well, they make a watch-your-employees-or-family-from-anywhere product. they make a product for The Firm.

      it's just a wifi webcam, good luck for them keeping it relevant and profitable for a couple of more years, even if someone wanted to leave the company he's apparently made it a hiring policy to hire people who don't have "fuck you" possibilities(dependent on the income too much and since income is not mentioned possibly the income isn't enough that they would accumulate any fuckyou money either) or tendencies so they wont leave. however, it would be interesting to know if he has done any commitments himself to the people - like how long of a notice would they have in the event of being fired.

      --
      world was created 5 seconds before this post as it is.
  56. no one has EVER left!? by shadowrat · · Score: 1

    for a WHOLE 4 YEARS!? amazing!

    1. Re:no one has EVER left!? by frank_adrian314159 · · Score: 1

      In the tech world? Yes.

      Even over the last four or so years of industry suckage. Especially for the last two or so in SV.

      If you don't understand this, you haven't been paying attention.

      Note: I'm not in SV and even I know this.

      --
      That is all.
  57. discrimination by bananaquackmoo · · Score: 1

    Did this guy just publicly admit to job discrimination? As in he won't hire single young childess male programmers?

    1. Re:discrimination by gl4ss · · Score: 1

      yeah, but it's for the family man so it's all good! nobody in prison is a dad you know! (oh wait except half the people on lockup).

      --
      world was created 5 seconds before this post as it is.
    2. Re:Discrimination by RightSaidFred99 · · Score: 1

      So what. Whiners complain about discrimination. Most people he would label "brogrammers" would laugh at him and the title and go on to get a better job, not run with their mascara dripping down their faces to a judge.

  58. Re:100 percent of 1 is 1 by AuMatar · · Score: 3, Interesting

    I've worked at 2 startups that were sold for 125M and 225M, each making more than 5x the invested capital. At neither of them would seeing anyone there at 9 be more than an extreme rarity. 8-9 hour workdays were the norm.

    --
    I still have more fans than freaks. WTF is wrong with you people?
  59. It is a self-fulfilling prophecy. by luis_a_espinal · · Score: 5, Insightful

    A VC once told me that before he invests in a start-up, he drives by their offices at 9pm on Friday night. If the parking lot is empty, that company is going to fail.

    Isn't that a self-fulfilling prophecy? I mean, if every VC demands this, then of course every company not meeting these standards will fail--because they won't be able to get any venture capital funding.

    Indeed, it does seem a bit radical. I've worked in start-ups, incidentally ones that survived the dot-com crash and are doing well nowadays. One had a solid business model and the other one was malleable enough to change gears and explore new business venues.

    We certainly did work our asses off, but ours were cycles of 50-hour weeks followed by a week or two of 60-hours weeks prior to delivering milestones, followed by a couple of weeks of 9-5's with a couple of days off. Rinse and repeat. It worked, and I know from 2nd and 3rd hand accounts that similar cycles work in other productive environments.

    Sometimes people really have to work crazy hours, but then again, who the hell in this time and age works crazy hours on-site????? That is pretty much what this VC is expecting to see, and to me that's a big fuck-up in terms of technology-oriented work environments?

    Fine we work long hours, a good portion of it from home. If I see a tech company parking lot full on Friday 9pm, either that company is a government contractor working with classified shit that needs to be done on premises, or they are a bunch of apes who have yet to discover the blessing of telecommuting.

    The VC is full of shit, or maybe his business wisdom is sooooo out of our pedestrian ability to grasp that it looks like magic shit conjured by Harry Potter or something.

    1. Re:It is a self-fulfilling prophecy. by Anonymous Coward · · Score: 0

      Maybe it's because I'm old but I always hated working at home. Even when I was running my own company, I'd find someplace else to go to work. I had one client who didn't mind if I camped out in his firm's empty office for ten hours a day doing my own stuff.

      Working at home there are too many distractions: the fridge full of beer, the TV, the pool, the hot divorcée next door . . . you get the point.

    2. Re:It is a self-fulfilling prophecy. by luis_a_espinal · · Score: 1

      Maybe it's because I'm old but I always hated working at home. Even when I was running my own company, I'd find someplace else to go to work. I had one client who didn't mind if I camped out in his firm's empty office for ten hours a day doing my own stuff.

      Working at home there are too many distractions: the fridge full of beer, the TV, the pool, the hot divorcée next door . . . you get the point.

      I'm on the same boat. I dread working from home, even though I have, at times, done it full time. A friend of mine suggested me next time I do offsite consulting to simply rent a small office (they can run very cheap) and work from there at any time that I need. However, I do find it useful to telecommute to put a lot of extra hours. Checking my e-mails and calendar first thing right after I wake up; logging at night from home to check for any urgent e-mails or if I happen to have an epiphany on how to solve an issue or to fire a time-consuming job to have it ready in the morning. Putting a few hours during the weekend as needed.

      Lo and behold one can gradually sustain long hours that way. Long hours are never desirable but often unavoidable. Though I do not like to work from home, I certainly would not want to do 50-60 hour work weeks on premises either.

  60. Re:100 percent of 1 is 1 by Anonymous Coward · · Score: 0

    A VC once told me that before he invests in a start-up, he drives by their offices at 9pm on Friday night. If the parking lot is empty, that company is going to fail.

    That's an outdated notion given the connectivity from home to work that developers have now. Some of the most productive employees I have had would only be in the office Friday night at 9PM during customer crises or integration phases where there is a lot of 'engineer to engineer' communications that needs to happen ASAP because until problem X is solved, nothing much proceeds.

    However, these same engineers would be IMing each other and checking in code from home at 9PM, 12AM, 3AM without the distractions of the janitors, automated timers turning lights off, or heated debates between engineers about stuff that wasn't very important.

    Some such employees "disappear" online for a couple hours for dinner w/family and putting kids to bed and are then back online for hours.

    For his sake, hopefully if that VC is still in the business he's changed his views or he's likely dismissing companies that will be very successful.

  61. IPO by MDMurphy · · Score: 1

    If I hear about a startup that hasn't lost any employees then I just figure they're waiting for the IPO. While l like the description of the diverse group of employees and other aspects of the company, I think not mentioning compensation at all is a little disingenuous

    If they're paying the people a reasonable wage and the checks don't bounce then employees tend to stay. Add in stock options and waiting for the big IPO, or as mentioned in the article a very big buyout, then you have people waiting for the big payday. The perks ( or lack thereof ) might have had an effect on employee retention thus far, but you shouldn't ignore the hope of substantial monetary compensation as an additional big motivator.

  62. Re:100 percent of 1 is 1 by ebno-10db · · Score: 1

    Isn't that a self-fulfilling prophecy?

    Of course it is, but self-fulfilling prophecies are the stock-in-trade of the investment community. Without them people might start to realize that the emperor is naked (or at least very scantily clad). For example, say the investment geniuses decide that companies will only succeed if they do more than half their work in India. Since investment geniuses are famed for their group think (oops, I mean great minds think alike) nobody will invest in a company that doesn't do that. Hence the geniuses are shown to be right. Isn't that a nice organized system? Without it you might have the chaos of different companies pursuing different strategies and seeing which worked best.

  63. Illegal discrimination? by PhamNguyen · · Score: 1

    "...we want people who understand that they are making a product for normal people, for their family and friends. So we often hire them because either they have their own kids..."

    My understanding of federal anti-discrimination laws, is that this is illegal. Of course these laws were designed to protect women and Blacks, not beta males, so of course nothing will actually happen.

    1. Re:Illegal discrimination? by CanHasDIY · · Score: 1

      My understanding of federal anti-discrimination laws, is that this is illegal.

      Generally speaking, you are correct. Here's the rub - unless you can prove you weren't hired because of illegal discrimination, you're shit-out-of-luck. Doubly so if you live in an "at-will employment" state, as typically employers do not have to give a reason for firing/not hiring a person.

      To that end, and speaking from personal experience, it's really, really hard to make the case that you were discriminated against when you're a healthy, young, male Caucasian.

      --
      An enigma, wrapped in a riddle, shrouded in bacon and cheese
    2. Re:Illegal discrimination? by ebno-10db · · Score: 2

      My understanding of federal anti-discrimination laws, is that this is illegal.

      Brogrammers are quick to cite federal anti-discrimination laws. Thank heavens no company in SV would engage in say age discrimination.

    3. Re:Illegal discrimination? by PhamNguyen · · Score: 2

      Care to make an argument based on its merits rather than attack a strawman "brogrammer", brah?

    4. Re:Illegal discrimination? by Hatta · · Score: 2

      My understanding is that familial status is only a protected class for housing discrimination. At least federally.

      --
      Give me Classic Slashdot or give me death!
    5. Re:Illegal discrimination? by twisted_pare · · Score: 1

      IANAL, but I'm married to an employment attorney. People with kids are not a protected class, so no. Race, religion, gender and sexual orientation are protected classes. If someone does not like unmarried dbags, there is no legal protection.

      --
      HTFU
    6. Re:Illegal discrimination? by PhamNguyen · · Score: 1

      Are you implying that unmarried people are more likely to be dbags, or that there is a reason to especially dislike unmarried dbags as oppposed to married dbags? Either way you come accross as very bigoted.

      Yes you are right about having kids not being a protected class, although marital status is.

    7. Re:Illegal discrimination? by PhamNguyen · · Score: 1

      You are right. Even in California, anti-discrimination law doesn't cover how many children you have.

    8. Re:Illegal discrimination? by ebno-10db · · Score: 1

      Care to defend the idea that there isn't rampant age discrimination in SV?

      As for my first sentence, you're the one who cited federal anti-discrimination laws, and "brogrammer" is what's widely called a "joke". Or are you so insecure that one joke really will have you consider a federal anti-discrimination lawsuit?

    9. Re:Illegal discrimination? by tftp · · Score: 1

      Are you implying that unmarried people are more likely to be dbags

      There is something in this question. A married person is usually less volatile because s|he had been trained to observe at least some social norms. You will get fewer antisocial types among the married set. On the other hand, the unmarried set contains most of the weirdos, most of the professionally unlucky, most of the maniacs, and most of the geniuses. The latter may be helpful, but watch for all the others.

    10. Re:Illegal discrimination? by RightSaidFred99 · · Score: 1

      Sorry, most of the men he's "discriminating" against are just laughing at him and getting other jobs. No need to go whining to Uncle Sam.

    11. Re:Illegal discrimination? by RightSaidFred99 · · Score: 1

      He doesn't need to defend it, you are asserting that there is. Common sense would indicate that older people make more money. Why hire a 55 year old dude when you can hire 2 or even 3 23 year olds for the same amount of money. Experience would of course be a reason but sometimes manpower is more important than experience, and it's up to the _business_ to decide that, not you or the EEOC.

    12. Re:Illegal discrimination? by neminem · · Score: 1

      Why not just tell people a salary, and if a 55 year old dude is the most qualified, and *accepts* that salary, then you hire him?

  64. Re:Slashdot = intellectual vomit by Anonymous Coward · · Score: 0

    Think I'll put 127.0.0.1 for slashdot.com in the HOSTS file and be done with it.

    No, you won't. Not one person who says that has ever done it.

  65. Re:No one who has joined the company has ever left by Anonymous Coward · · Score: 0

    Lol best comment on this worthless story about the megalomania of some dipshit "brogrammer CEO" XD

  66. Re:100 percent of 1 is 1 by CanHasDIY · · Score: 1

    I mean, if every VC demands this, then of course every company not meeting these standards will fail--because they won't be able to get any venture capital funding.

    The very idea that a company is doomed to fail if a Vulture Capitalist doesn't buy them up makes me a saaaaaad panda :(

    I guess this means that "The American Dream" has become truly incorporeal...

    --
    An enigma, wrapped in a riddle, shrouded in bacon and cheese
  67. Re:Slashdot = intellectual vomit by Cormacus · · Score: 1

    Slashdot: Its _dot_ _org!_

    --
    Mon chien, il n'a pas du nez. Comment scent-il? TrÃs mauvais!
  68. RTFA by Anonymous Coward · · Score: 1

    “We bring in breakfast and lunch because we think it makes people more productive if they don’t have to go wait in line at restaurants in SoMa, which are crowded. But we don’t bring in dinner. We don’t make people work late. It’s a way to keep people from getting burned out.”

  69. Re:Brogramming -- a direct result of Dunning Kruge by Anonymous Coward · · Score: 0

    And this isn't distasteful stereotyping at all because we are talking about young white males and they are free game for everyone! Yay!

  70. Re:100 percent of 1 is 1 by ZombieBraintrust · · Score: 1

    Generally if your starting your own buisness you need to work crazy hours to compete with established buisness the first few years. I don't see why the expectations for programmers would be different from a mom and pop store.

  71. Re:Possible scenario by Anonymous Coward · · Score: 0

    RTFA you goddamn moron.

  72. Discrimination by kheldan · · Score: 1

    don't fill your engineering department with young, single, childless males

    You can't hire and fire based on gender, age, marital status, or family status, it is discrimination. Hire qualified, experienced people.

    --
    Are YOU using the TOOL, or is the TOOL using YOU? Think about it!
  73. Re:Slashdot = intellectual vomit by Anonymous Coward · · Score: 0

    Don't bother. I've tried it on several occasions, and it does work well to remind me to stay away. The problem is that I eventually realize I have nothing better to do, and that is why I read Slashdot, and so it gets unblocked. Still can't help but think I'd be better off doing anything else, but most of the world is intellectual vomit. Slashdot is just the vomit that still has some salvageable chunks of food in it.

  74. Re:100 percent of 1 is 1 by j00r0m4nc3r · · Score: 1

    It also isn't clear that "retention rate" is an important metric, or even if it is a positive thing.

    Nice insight. But also, he might just hire dipwads who can't find another job somewhere else. 100% retention!

  75. Re:100 percent of 1 is 1 by Anonymous Coward · · Score: 0

    Some churn is good, but lots is not. If the company is growing and never loses anyone, but gains new people, then you get both experience and new ideas at the same time.

    But yes, once a company is mature and not growing, 100% retention is not "perfect".

  76. Estimates don't account for Risks and Unknowns by mtippett · · Score: 1

    As per my blog post a couple of years ago at http://use-cases.org/2011/06/04/getting-good-estimates/ and http://use-cases.org/2011/06/22/updates-on-getting-good-estimates/

    Most good estimates have a range - and not a number, or a number with a confidence (both are interchangeable).

    If an engineer says it will take two weeks - I push for a range or a confidence. If the range is weird (2-8 weeks), I push for the engineer to tighten their estimate through discussing or raising and discovering the unknowns or the risks that they are aware off. That sort of estimate would usually end up around 3-5 weeks which is a reasonable margin - and a lot better than than underestimating by 50%.

    Same with estimates that are too narrow. "2 weeks +/- day". That implies a full level of understanding, no risk and no dependencies. Almost never happens. Work through the same risks/unknowns and the estimates usually become really bad - typically at least double of the "high confidence" estimate - similar to TFA.

    The is lots of reasonably applicable theory behind this (confidence intervals, cone of uncertainty, etc).

  77. Re:Estimates don't account for Risks and Unknowns by mtippett · · Score: 1
  78. Re:100 percent of 1 is 1 by mitgib · · Score: 1

    It's just the Hotel California, you can check-in, but you can never leave!

    --
    Being a spelling & grammar Nazi is a sign you do not poses the intelligence to contribute to the conversation
  79. Other "benefits"? by DavidClarkeHR · · Score: 1

    I'd agree with dinner, and maybe breakfast to an extent. But lunch? It's just a time saver to have it at work. If I eat while working and don't take the time off for lunch, I can leave sooner.

    Agreed. But dropcam does a lot of things that you expect in other areas ... like "maternity and paternity leave and all of the things that used to be things that only big, mature companies did."

    Sure, it might be required everywhere outside the USA, but that's a common sense program that really helps an employee get back to being productive, quickly.

    --
    - Nec Impar Pluribus, or so I'm told.
  80. DUN-DUN-DAAAH! by Guppy · · Score: 1

    "no one who has joined the 4-year-old company has ever left..."

    ...the CEO said as he glared ominously at the interviewer then laughed manically. "No one."

  81. no one hired there has ever left? by Anonymous Coward · · Score: 0

    It's a trap!

  82. frozen in place.. by hhawk · · Score: 1

    Let's hope they are not all frozen in the basement.. ;)

    --
    http://www.hawknest.com/
  83. Re:100 percent of 1 is 1 by cas2000 · · Score: 2

    A VC once told me that before he invests in a start-up, he drives by their offices at 9pm on Friday night. If the parking lot is empty, that company is going to fail.

    he was probably just ego-wanking all over you to make you realise what an important big man he was.

    only big, already successful companies can afford to own or rent their own parking lots. startups rent office space and most of their employees rely on street parking or nearby commercial parking (or public transport, bicycles, or living withing walking distance of work etc).

    The startup might rent a few parking spots for the founders or maybe top employees...but they certainly won't be in an easily identifiable Startup Inc Parking Lot that you can do a drive-by eyeball at 9pm, they'll be a few reserved spots in a nearby car park.

    now go wash that VC spoof off your face. and stop lapping it up.

  84. employee retention by jamesh · · Score: 2

    no one who has joined the 4-year-old company has ever left...

    ... alive.

  85. Dropcam sucks by Anonymous Coward · · Score: 0

    Now I know why their cam's are bandwidth hogging crap.

  86. HOLY SHIT by Anonymous Coward · · Score: 0

    companies DISCOVER if you treat people like REAL HUMAN BEINGS we appreciate it. someone tweet this so cnn etc can put this on their news site

  87. Re:100 percent of 1 is 1 by Anonymous Coward · · Score: 0

    A VC once told me that before he invests in a start-up, he drives by their offices at 9pm on Friday night. If the parking lot is empty, that company is going to fail.

    I miss the Y2k dotcom era. Startups would pay ME to let me use THIER parking lots.

    Wally - WallyWorld Parking Inc.

  88. Re:Slashdot = intellectual vomit by WGFCrafty · · Score: 1

    Please do and leave it that way, because no one with a productive/meaningful life cares anything about your trivial host file ramblings.

    And even the people on slashdot with unproductive, trivial, meaningless lives don't care.

  89. Now that's good managing by Nbrevu · · Score: 2

    I once worked on a place with such "mind control" (I would have put it as "emotional blackmail"). Oooh, free food! Oooh, videogames to play after lunch -there is a one hour mandated break, although most people will be done by 15-30 minutes-! Ooooh, free pizza&beer every Friday! Oooh, lots of parties on weekends! Yeah, well, I got fired because of the mortal sin of going home at about 7-7:30pm despite having been told that I had very good technical capabilities, so I wouldn't say it was a good job.

    I'll take owning my time over such "perks" any day, and I wish there were more CEOs like this guy.

    I work, I go home when I've done my 8 hours, I get paid. Simple. Why is this so difficult to grasp?

  90. Worse than wrong, outright being bad by Anonymous Coward · · Score: 0

    That's just more of the same, and double the asshole if you are doing this in the same room as others. A lot of youngster basement-dwellers at their first job thinks this is how it's done, and that it's so effective but it's not. You are ineffective (compared to taking a solid break and getting some air) and furthermore unhealthy and disgusting. And you are breaking the flow of everyone else in the room, costing even more money.

    Ok, I know America is like 50 years behind in management so your boss probably thinks it makes sense. Or, if your job is warming a chair *only* and you are alone in the room, then I suppose it's ok. Otherwise, no.

    Why this isn't obvious to anyone over 16 (with no diagnosis) is baffling.

  91. Four years with the job market in the dumps. by Anonymous Coward · · Score: 0

    It's probably easier to keep people in your company when the job market is bad.

    And that's been the case for a lot longer than 4 years.

    If you can keep your staff (without having to pay top dollar) when the market is booming shows that your work environment is worth value.

  92. Most of Silicon Valley would collapse by WOOFYGOOFY · · Score: 1

    If companies didn't hire brogrammers and fire anyone over 35-50, as they do, then half of Silicon Valley companies would go bankrupt tomorrow. Their entire business model is dependent on H1Bs living five to an apt. and having nothing to do but work.

    Oh and about the assholes. The assholes are already there from the top of management on down. Assholes inevitably hire assholes because they unconsciously recognize each other (assholes are a generalization of narcissists, who like themselves a lot) and because there's nothing an asshole has more contempt for than someone showing obvious signs of having a, you know, conscience.

    So what you end up with in all these companies is a two tiered caste system of brogrammers and their asshole overseers. Brogrammers are disposable, assholes are inviolate and the whole thing is run on the model of a pirate ship.

    And these are the blue chip NASDAQ companies we're talking about. (been there, done that) Beneath that level , the startups it's likely to be the same dynamic but maybe the asshole tier is populated by a runaway-H1B or three.

    American business's go-to model is always exploitation of anyone stupid enough to send in their application, ingenuousness in its dealings with its partners and customers and tax evasion to the limit of the law and beyond.

    It's the American mindset and it has been around at least since the days of the building of the railroads.

    In Germany and Scandinavia and other more, you know, evolved nations it's very different . There's just not the default assumption that the only / best way to get ahead is through exploitation and as much criminality as you think you can get away with or will still be profitable once you're caught.

    There they''re more concerned with building quality products and letting the consumer make their choices.

    This is what capitalism is supposed to be about, but the US regulatory structure is deliberately kept too weak to enforce anything like what's needed for a a "free market" to flourish for labor or services or anything else.

    It's one of the ironies that people can't get past. A strongly regulated environment is the freest. Employees who work fewer hours and have meaningful time for things like vacations, families and maintaining an interest in the broader culture in which they live are just more productive.

    Americans are just not that smart. It really sort of comes down to that basic fact. And I say this as an American.

  93. Re:100 percent of 1 is 1 by the+Gray+Mouser · · Score: 1

    Many start up restaurants do exactly this.

    No one wants to eat at an empty looking restaurant.

  94. Re:Let me guess which group represents the largest by betterprimate · · Score: 1

    This is sort of "damned if you do, damned if you don't."

    Are not some young, single, childless males being responsible by planning their careers and family life?

  95. Re:Let me guess which group represents the largest by firex726 · · Score: 1

    Sorry, how does their future life relate?

  96. Re:Let me guess which group represents the largest by betterprimate · · Score: 1

    Sorry, wrong thread.

  97. Re:100 percent of 1 is 1 by Anonymous Coward · · Score: 0

    or, if you live near a popular nightspot, hire a guard and rent your carpark out on friday nights as secure parking