[nostalgiac]

Although the author phrases it as "70+ hours a week", my assumption is it's not the hours per week that he doesn't want to commit to it, but the total hours involved that it's going to require to solve the situation.

Whether that's 70 per week or 5 hours per month, the total amount of hours needed is going to be x,00 or x,000 - and that's time he simply thinks is not a priority or valuable to him.

[onion2k]

There's a total number of hours of work needed to build something, but they don't all have to be put in by one person. It might be one person doing 70 hours a week, but equally it can be two people doing 35 hours each (probably more like 40 hours actually to account for comms, but still, not even close to 70). The hard part is finding someone who can do the role.

[bkor]

I don't agree on the assumption that the total number of hours is a given. If you're working on something 70+ days per week for an entire year, your productivity is going to drop. If you work less, but are refreshed when you start working, you'll be way more productive. Especially if it requires any amount of thinking.