Adventures in Code

On Monday, December 9th, where I left my previous post, I picked up my first task of Week 2. The previous week I didn't get much work done, and really had to catch up with others this week. I picked up my first real coding task, where I wrote lots of code. I claimed the task at 7:00 PM and started working on it immediately. The task was to implement a new coding exercise on this website called Exercism, and I did exactly that. It was a steep learning curve to complete this task since this was my first Issue and Pull Request on Github. I quickly learned the basics, implemented the exercise, and Committed my changes to the Repo. To my great disappointment, 2/21 of the tests on my code were failing! I had no idea what to do and felt like I couldn't complete the task. The task had an optional part, and I attempted that, but in Python. I submitted my task sleepily at 11:30 PM and hoped my mediocre work would get accepted.  The next morning, my mentors said that the optional...

I know this is a week late, but I decided to write down my experience later. For many others in my organization —  Julia  —  this week was incredibly productive; They had already completed 5 tasks. But my first week had a slow start. Google Code-in started on December 2nd at 11:30 PM IST. I looked at the tasks for Julia, and I decided this was the organization for me. At 7:20 PM on December 3, I claimed my first task: "Introduction to the Julia community". In this task, we had to join the Julia Slack, and write a small script to familiarize ourselves with the language. I wrote a Quadratic Equation Solver for this task. Since it was a beginner task, it didn't take much time. By 9:30, I had written, tested and added comments to my code. I submitted my task for review, and overnight, it was accepted and I could choose another task. The next day, at 7:30 PM, I claimed my next task: "Write a blog post about 1-based vs 0-based array indexing". In this task, I res...