Working on an implementation > working on a code by thinking of it > typing code. Still, all activities above are strictly technical. So, is your question rea

Working on an implementation > working on a code by thinking of it > typing code. Still, all activities above are strictly technical. So, is your question really about whether we have as much time for technical activities (as opposed to bureaucracy, marketing, managing, selling...) as we'd like to? Or is your question about how our time devoted to strictly technical things is organized? FWIW, I recommend RHickey's "Hammock-driven development" to think of it more..