3 ms·
Eh, from my perspective 20% time is both implicit and unwanted. It's implicit because I'm not coding to a spec. I've got an area of responsibility and some ge
by saalweachter 13y ago
Eh, from my perspective 20% time is both implicit and unwanted.
It's implicit because I'm not coding to a spec. I've got an area of responsibility and some general goals the people above me would like to see accomplished. If I have an idea, I try it out. I could see someone in a more spec-based, feature-driven role wanting to have time to work on their own features off the spec.
On the other hand, I personally don't want conventional 20% time. I don't really like working on two projects at once. One fills my head and all of my ideas relate to it and a second one gets in the way. I once again understand that some people can work on two things at once and enjoy it, but hey, I'm not one of them.
So I'm not sure there's an actual problem. If most of your engineers are like me, and are working with a great deal of independence on a project they find interesting, why would they want 20% time?