3 ms·

> I feel that we hired someone who wasn't sold on the whole startup thing, and treated an early stage startup as if it were a regular job. Or maybe he realized

> I feel that we hired someone who wasn't sold on the whole startup thing, and treated an early stage startup as if it were a regular job. Or maybe he realized that working long hours on the same thing with no breaks would actually bring productivity down below what a normal 40 hour week would after just a few weeks. You know, maybe he actually kept up on the science of productivity.

pbiggar 16y ago
[citation needed]
- loewenskind 16y ago
  Really? This information is over 100 years old in some cases. Here's a few links I found quickly. The first one has a lot of citations itself. http://archives.igda.org/articles/erobinson_crunch.php http://archives.igda.org/articles/erobinson_crunch.php http://hbswk.hbs.edu/archive/5190.html http://hbswk.hbs.edu/archive/5190.html http://blogs.hbr.org/cs/2010/05/the_productivity_myth.html http://blogs.hbr.org/cs/2010/05/the_productivity_myth.html It seems to me that it's come up several times that in your company you chose to follow what you thought was right instead of actually researching it. I hope you can correct this before future ventures.
  - pbiggar 16y ago
    I apologize for my flippant remark above. People aren't getting what I'm trying to say in this thread, and my remark reflected that. The key part here is that it's not sustainable long term. It would be silly to optimize for long-term productivity with launch looming and features unimplemented.
    - loewenskind 16y ago
      According to the latest research I've seen, you start dropping productivity within a couple of weeks of over work. You were in this mode for months, no?
      - pbiggar 16y ago
        Personally yes, same for my co-founder. However, the employee under discussion had only just started. (and a quick reminder here that we're not discussing the employee's passion for the startup--which everyone would agree was low--not his "goodness" as a human being or as a developer.)

pbiggar 16y ago

[citation needed]

loewenskind 16y ago
Really? This information is over 100 years old in some cases. Here's a few links I found quickly. The first one has a lot of citations itself. http://archives.igda.org/articles/erobinson_crunch.php http://archives.igda.org/articles/erobinson_crunch.php http://hbswk.hbs.edu/archive/5190.html http://hbswk.hbs.edu/archive/5190.html http://blogs.hbr.org/cs/2010/05/the_productivity_myth.html http://blogs.hbr.org/cs/2010/05/the_productivity_myth.html It seems to me that it's come up several times that in your company you chose to follow what you thought was right instead of actually researching it. I hope you can correct this before future ventures.
- pbiggar 16y ago
  I apologize for my flippant remark above. People aren't getting what I'm trying to say in this thread, and my remark reflected that. The key part here is that it's not sustainable long term. It would be silly to optimize for long-term productivity with launch looming and features unimplemented.
  - loewenskind 16y ago
    According to the latest research I've seen, you start dropping productivity within a couple of weeks of over work. You were in this mode for months, no?
    - pbiggar 16y ago
      Personally yes, same for my co-founder. However, the employee under discussion had only just started. (and a quick reminder here that we're not discussing the employee's passion for the startup--which everyone would agree was low--not his "goodness" as a human being or as a developer.)