Week 1 + 2 Recaps and thoughts

-
So I know the last post read a lot like an English essay assignment, that's mostly because I didn't really know how this course would've played out and treated it like any other assignment, straight to the point. But throughout the week I came to realise how casual and freeform this Open Source Dev course is and it's definitely got to do with our Professor, David Humphrey and the way he's set up the course. 

Firstly, the fact that it's asynchronous so my 13 hour time difference doesn't make things hard, unlike other courses that last until 2 am where I am. Also just cause it's asynchronous doesn't mean our interactions with him are practically none. In fact it's much more than any synchronous class. He's set up a slack group for the class that he's emphasized is pretty much imperative for success in the course, and because of that, communicating with the prof and even the class is a 24/7 thing rather than limited to class time. So I find myself reading new messages all the time, as Slack stays on in the background, and obtaining insight from everyone in it. Though I don't find myself participating in the messages so much as I lurk since Imposter Syndrome still creeps in my mind. Which brings me to my next point

When the prof was giving out his lecture, in the form of a recorded YouTube Video for asynchronous purposes of course, I felt as if he read my mind (and others I presume) about how some of us less talented programmers, so to speak, suffer from the infamous "Imposter Syndrome" He elaborated on that topic and was basically ensuring how it's normal for any of us feel that way and that the whole point of this Open Source Dev Community is for the sharing of knowledge and not to be intimidated by your lack-of. That's pretty much when I knew this course was the right decision. It's only been a week and I feel like a way better and motivated programmer than I have been the past few semesters.

I think the past few semesters my ambitions and motivations for programming have been fluctuating. I find that's it definitely got to do with the course and Instructor. A good combination of both can really bring out the best in me and peak my interest. The opposite just makes me treat it as a course I have to pass. A meaningful purpose and interesting topic of a course added up with the enthusiasm and competence of an instructor makes me want to become a better programmer and influences me to follow my curiosity, and Prof H's definitely got both those boxes checked.

Anyways, next post is going to be about a program that he's got us working on for the past week so I'm gonna separate this rambling post with that one.

Thanks for reading :)

Comments

Post a Comment

Popular posts from this blog

HacktoberFest Entry No.2

-
Image
So around last week I found a great github repo of a chrome extension that previews contents of a webpage when you hover over a link. I stumbled upon it after a suggestion from my professor about taking a look at chrome extensions for a possible repo to contribute to. I'm glad I did because this was a chrome extension that was interesting, seemed practical and had a maintainer who was keen on receiving contributions to better his program. The extension is called Survol First I had to install it and test it out first, can't just contribute to a repo meaninglessly just to force a pr. I tested the extension and liked the functionality, it was useful and is well designed. Makes it all the more exciting for me to try and contribute to it. So I read the docs and learned how the extension worked. It uses a javascript file to inject html elements through the dom and uses mousemove event to detect anchor links to request information of a page, and positions and fills the div with conten...
Read more

Lab 1 : Our First Open Source Contributions

-
So for Lab 1 our tasks were fairly simple. Find a partner to review a repo on and make contributions, no matter the scale, to their code. Be it a suggestion for their code, reporting an issue, or even fixing up small details in their readme. So through slack I partnered up with one of my coursemates  Niaz Much like me, he wrote his code in nodejs, so it was perfect since I can go through his code easier through my understanding of node. His code, though written in the same language, differed from mine a lot. For one, he didn't use yargs so he had to process the arguments manually, and secondly he didn't use fetch and opted for a module called linkinator. No problem, in fact it's an opportunity for me to understand the logic and components that he used. I forked a copy of the repo, cloned it and tested it out for myself. The code worked perfectly as intended and processed urls well. Functionally, I couldn't find find anything in the code I could identify as a flaw or imp...
Read more

Hack.... vemberfest.. PR No. 3

-
Image
OK so this is pretty long overdue (sorry Prof!) And I still have one more pull request to go and that's on me yes. BUT, this week I spent working (or should I say learning) on our course's aggregated blog website which coincidentally, our prof is making us work on this week for the lab, so I guess I got a good head start going on.  So I took on an issue that seemed pretty straight forward in the repo. It was to change the functionality of the search bar when filtered by author. Seemed pretty straightforward enough, so I went ahead, forked the repo and cloned it on my computer. Now the reading begins, the lengthy process of coding. And the fact that this was a whole website coupled with different technologies that I'm not familiar with only made it waaayyy longer, which maybe is a sign that I should have started working on this much much earlier. But that's what happens when your time management skills is hot garbage. Anyways, I spent the next few days learning about eac...
Read more