In my rather limited experience this doesn't work.
Ex: Say you are working on just one feature for your company's software.
Most people, including myself, aren't able to sit for 8-10 hours a day in front of the computer working on just one problem. Your brain turns to goo, you start getting easily distracted and your productivity drops through the floor. I'd say at most I can sit in front of a debugger for 3 hours, and that's on particularly good day.
People need to be able to switch their brains to other work when they get overwhelmed or get stuck.
More interesting is the opposite problem of having too many things to do. At some point you never get to focus on any one of feature and you end up not getting anywhere.
When I get in the flow, writing software, I get a day of work done per hour. When I do 5 hours of focused work, I do about 2 weeks worth of work. The slightest distraction throws me off, though, because the context-switching becomes enormous. My favorite (yikes) distraction: having a tool I know and use not be available because of outdated company policy. This throws off everything and loads Anger and Frustration 3.7 in the brain processing center.
Ex: Say you are working on just one feature for your company's software.
Most people, including myself, aren't able to sit for 8-10 hours a day in front of the computer working on just one problem. Your brain turns to goo, you start getting easily distracted and your productivity drops through the floor. I'd say at most I can sit in front of a debugger for 3 hours, and that's on particularly good day.
People need to be able to switch their brains to other work when they get overwhelmed or get stuck.
More interesting is the opposite problem of having too many things to do. At some point you never get to focus on any one of feature and you end up not getting anywhere.