My experience is that this works well in an IT infrastructure sort of environment where you're assigned tickets that takes a couple of hours on the average. It

My experience is that this works well in an IT infrastructure sort of environment where you're assigned tickets that takes a couple of hours on the average. It sort of works in a project-based product development effort where programmers are implementing features and fixing bugs, but breaks down horribly on anything that involves any sort of research and experimentation (you know, the sorts of things that actually create breakthroughs and make money?) And God forbid you ever try to learn anything new: "Yesterday: read 50 pages of the ElasticSearch manual. Today: read 50 more pages of the ElasticSearch manual. Tomorrow: get fired for not having anything immediately profitable to put on status report."