The first run will be a killer, but after that, save time and IOs people. Only run it daily or weekly and then only on objects that have changed over the past two days or week and a day. Q. Why the extra day? A. I don't run it at midnight.
It runs in <1/2 hour per week with 200-400 object changes. Why reindex everything if only a few objects have changed? Only spend the extra IOs and CPU once a quarter or twice a year and rebuild it completely. Then only if there have been a lot of changes.
I realize that I've used a lot of loose terms, "a lot of changes", "only a few objects", etc. This is because each company has a different configuration with different amount of work being done at different times. Use the right definitions for your organization.
Make your developers happy, run it daily. No harm done and they'll appreciate it.