If it's something I need to learn for work, I go shallow... because usually at work we focus on trendy buzzwords (e.g., k8s, graphql, protobuffers, etc.). So, i

If it's something I need to learn for work, I go shallow... because usually at work we focus on trendy buzzwords (e.g., k8s, graphql, protobuffers, etc.). So, it usually take me a few days to get the enough knowledge to keep pushing code to production. If it's something I want to learn to satisfy my curiosity (e.g., Golang, TCP/IP, architectural patterns, linux kernel, etc.) it takes me months and I usually stop after building a couple of projects and after reading a couple of reference books.