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."
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.
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.
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.
...for having a CEO that actually cares about them.
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.
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.
Please do and leave it that way, because no one with a productive/meaningful life cares anything about your trivial host file ramblings.
The one consistent thing about Agile: "you're doing it wrong". I have never seen a different answer to any complaint about Agile.
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.
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.
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)
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
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.
:-P
(*) Then again, the 1990s probably want their "[year] called, they want their [subject] back" cliche back, but they're not getting it
"Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
"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.
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."
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.
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.)
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.
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.
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.