Ask HN: How do you balance learning a new skill/toolset and implementing it?
For example, I just moved from refactoring and extending a JavaScript graphics processing library to writing a Python program that interfaces with USB and WiFi-enabled IoT devices.
I’m excited to learn new technologies, but I find myself spending quite a lot of time (4-5 hours per day for the first week, ~2 hours per day thereafter) trying to learn the new language, toolset, best practices, etc. I wouldn’t call myself a perfectionist, but I hate the feeing of looking back on my code and seeing problems that I should/could have caught, if I had known a little bit more.
So I find myself plunging deep into, say, TCP/IP network administration when I really don’t need to know everything about networking to deliver my work.
When your job requires you to learn something new, how do you determine “yes, that’s enough for me to get the job done”?
0 comments
[ 4.7 ms ] story [ 16.6 ms ] threadNo comments yet.