As I was trying to find other students who might code release 0.1 in GO in the channel, I kept running into disappointment as most students decided to write this in more well-known languages like JavaScript, Java or Python. Eventually, I got lucky. After a few non-replied efforts, someone finally replied and told me that his friend was doing release 0.1 in GO. And I managed to connect with him.
The requirements of lab 1 is to work with a partner to raise issues and resolve problems potentially located in your codes. You need to find an issue in your partner code and he/she need to do the same in yours. Then you need to come back to your codes and try to fix it and tell how you feel about the whole process. As I was looking at my partner’s repo, I realized the real meaning of open source development when you have someone looks at your repo. It is not only you help them fix a bug but you can also learn a lot from the way they code their project. I have learned how to use WorkGroup with Go routine as an alternative way to using channel to keep the main routine running. I have also learned that you can optimize your http call by using a HEAD request instead of a GET request.
As for my partner, I helped him to fix his check for status code logic and also the check for length of arguments that could never be a negative number. He agreed with me and merged my PR.
This has been a very good experience working with someone that you do not know personally. It has taught me the values of working on an open source project and how they can make a great impact in my learning and future work because I would have chances to test my knowledge as well as practice teamwork.
Shout out to Phil and Mat for collaborating with me for lab 1. I am looking forward to working with you guys in the next release.
Thank you for reading,
Tony.
