day 4— jan. 12, 2017
*Sigh* many many many distractions.
Didn’t get much coding done but I did read a lot about code today. As I mentioned before, I love reading documentation. It’s very helpful and one of the best ways for me to understand something deeply.
But I do want to be transparent in that, I can get a bit carried away when it comes to reading technical blog posts/documentation. I get excited about a particular advanced topic and think ‘This is doable, this makes sense, I can do it, in fact I’ll give it a shot RIGHT NOW!’ and I’m off trying to deploy something that I might not be ready for.
Which, don’t get me wrong, is a great way to learn sometimes. The most repeated advice I hear from developers/engineers/designers is “Just build something. Anything. Just start where you are. Do it.” And I agree. I realize that I have the ‘just start it’ enthusiasm but in the past, tended to get overwhelmed because my planning style leans towards big picture and not small parts. “If I can’t do it all, how can I do any of it,” is what I thought to myself at times. And for obvious reasons, that can be discouraging. I don’t need to know how to do all parts of the project before starting it. I need to focus on what I can do, what I know how to do, and do it. And when I hit something that I am not sure I can do, treat it as a learning opportunity.
I have identified that this is something I need to continuously work on; reconciling between the need to know ~all the things~ before I can start something and starting things that perhaps are more advanced for where I am in my coding journey (because excited) and then judging myself harshly for not understanding it quickly. I am always striving to find the sweet spot between writing lines of code AND understanding why it works. I want to not only be enthusiastic about starting personal projects, but also be strong in completing them.