Many OSS contributors disappear because they're encountering satisfyingly challenging engineering problems as their day job for the first time. It takes a speci

Many OSS contributors disappear because they're encountering satisfyingly challenging engineering problems as their day job for the first time. It takes a special discipline to actually _use_ 20% time at all (not because of team pressure, just from the ease with which one can focus on the large problems at Google). I've had that problem myself, and am considering putting said discipline in my own written goals.