About time: coding time

That’s right: it is better late than never. I am returning to my blog writing once again. I had a long discussion with myself about whether I should or should not start a blog of my own. During my ongoing pre-course at Makers Academy, I have discovered that TIME is valuable and should be used wisely. Nothing I start I can finish, just because I don't have enough time.

Choosing to work during the four weeks of the pre-course was a pretty dumb decision because the number of hours spent over the code challenges exceed the recommended 20 hours per week. I can convince anyone arguing against this point that you will need much more time than that. If you ask me why, I would say that even if the pre-course is designed for complete beginners, you would still need a good foundation and extra online tutorials coupled with books to grasp all the fundamental programming concepts hidden behind the scenes. 

I am still working full-time, not to mention my current role which has nothing to do with coding. Hence, I struggle. I struggle to find time to fill the gaps in my knowledge and do some extra reading. The last one is crucial when it comes to learning how to code. 

John F. Kennedy said:
“We must use time is a tool, not as a crutch“

Regarding the books, some heavy reading, check this out yourself. These are brilliant works written by experienced programmers: 
1. A Well-Grounded Rubyist by David A. Black - 506 pages, plus exercises 
2. Practical Object-Oriented Design in Ruby by Sandi Metz - 247 pages, plus exercises


Don't expect to read them in one day, remember it would take time! 

During your four weeks of the course you will cover the following: 
Test Driven Development 
Ruby 
Command Line 
Git & GitHub

These are the core aspects that you will cover, on top of these many others, such as solving Kata challenges, meditating over the code on Ruby Koans, writing your first command line application, brushing up your CV, getting familiar with various test editors, including VIM, and occasionally meeting with your mentor or cohort to practice all of the above. 

On Friday of the first week, I realised that I am way behind and have not got very far with the weekly challenge. After work, my brain gets too tired and can not focus, so I have to spend the entire weekend at home, hitting my head against the wall. The good news is I managed to submit everything on time. At the weekends, I did my very best to try to make the most of my time and practice writing the code all day long. Coding for 12 hours straight would not probably be the smartest idea, so I took a lot of breaks - for morning tea, for breakfast, for lunch, for Insta check, for calling my mom and for dinner. 

Even if you miss a deadline, try to complete your work ASAP. Do not take it as a general piece of advice and strive to finalise a project within the given timeframe.

I have learned that setting a deadline is a great practice and a perfect motivator to keep yourself going.

It does work for me. The better you understand yourself the better you can manage your own time. And if you do so, I believe you will succeed at everything, including in coding!

Remember the key is in not spending time, but investing in it.