> I agree that extremism in order to learn is a great strategy.
I think it is key to consciously decide when you're learning and when you're doing, and to keep that in mind as you act.
If your goal is to learn, feel free to try bold stuff that might not work. But when your goal is to build, stick to boring stuff that you're confident will work.
This applies at all scales. When you're inventing a programming language, is it a scientific instrument or an engineering tool? When you're adding a feature, it is to understand the users or to deliver value to them? When you're changing the signature of a function, is it an experiment or an improvement?