I love this. I am a huge proponent of continuous improvement. It keeps me fresh and constantly wanting more, otherwise I just get bored. A few weeks ago I started learning about test-driven development in .NET. Even though I don't use it every day, knowing something like TDD in the context of .NET has helped me contribute more to conversations with my peers at work.
Learn, learn, learn! Even if you don't think you'll use it every day, there's always something useful with every tool you add to the toolbelt.
How do you feel about the "80/20" work ratio that some companies talk about? Providing "20%" paid time to "work on any project you want". Do you think that basically comes down to the 15/5 that you're advocating, even if they don't call it that?
Seems like they have similar goals—uncover value by getting out of a local maxima. Most companies don’t have the guts to follow through though. “Giving up” 20% seems like it’s “too expensive” regardless of what they might get in return.
I love the intent behind this schedule. You ended with a framing in a 40-hour work week though. Would you say the same ratio applies to a 32-hour work week? I think it’s certainly possible that as time goes on, the prevalence of such work weeks will become higher.
The percentages should be roughly the same. The trick is to do the exploratory work in little bites. By the time you're making a big bet, it should no longer be a bet.
If you are a professional software developer and only work 40 hours a week, you are not going to do very well in that career. And if you only spend 2 hours a week "satisfying your curiosity" you are doomed.
I love this. I am a huge proponent of continuous improvement. It keeps me fresh and constantly wanting more, otherwise I just get bored. A few weeks ago I started learning about test-driven development in .NET. Even though I don't use it every day, knowing something like TDD in the context of .NET has helped me contribute more to conversations with my peers at work.
Learn, learn, learn! Even if you don't think you'll use it every day, there's always something useful with every tool you add to the toolbelt.
How do you feel about the "80/20" work ratio that some companies talk about? Providing "20%" paid time to "work on any project you want". Do you think that basically comes down to the 15/5 that you're advocating, even if they don't call it that?
Seems like they have similar goals—uncover value by getting out of a local maxima. Most companies don’t have the guts to follow through though. “Giving up” 20% seems like it’s “too expensive” regardless of what they might get in return.
I love the intent behind this schedule. You ended with a framing in a 40-hour work week though. Would you say the same ratio applies to a 32-hour work week? I think it’s certainly possible that as time goes on, the prevalence of such work weeks will become higher.
The percentages should be roughly the same. The trick is to do the exploratory work in little bites. By the time you're making a big bet, it should no longer be a bet.
If you are a professional software developer and only work 40 hours a week, you are not going to do very well in that career. And if you only spend 2 hours a week "satisfying your curiosity" you are doomed.
Work out ratios that work for you. But don’t feel ashamed about the 15s and the 5s (whatever numbers you choose).