But perhaps one could argue that this resulted in those hours being more productive because they were more spread out. So assuming what you're saying is true, they could have gotten more productivity out of the same number of hours as another business that condensed its work more.
That seems like a very simplistic question, and adrian and seoxy are trying to explain why that is so. There are MANY facets within both coding and design. It would be simplistic to assume you could be excellent in all facets of either one (because they are so broad). So why can't it be possible to be excellent at certain aspects of both coding and design?
Maybe technically, but the word doesn't really add anything to the statement if someone uses it anytime they didn't observe what happened. Supposedly is akin to saying "Assuming what this person said is true, ..." which in many cases implies doubt (why not just say "so and so said she went into town").
I think his point was that it makes literal sense, but it doesn't help the process of communication, which is why he's torn on the issue.
I think his point was that it makes literal sense, but it doesn't help the process of communication
I think it does help - it implies that there is doubt (and possibly some lying involved with what's going on).
Simply stating "so and so said she went into town" is factual (although emphasizing "said" can also imply the same things that using "supposedly" does).
However, if the top-level-commenter's GF is using "supposedly" not in this way, I'd agree that'd be annoying. Maybe she's the mistrustful sort?
