Telescope 2.7 and a long overdue blog post

-

What's up gang, sorry it took me a while to get back at writing this post. This one's gonna be a 2 part-er. This one's regarding my time as Sheriff during week 5 (Feb 5 - 12)

Sheriffin

Last week, as I mentioned in my previous blog post, Kevan and I had to sheriff the telescope repo for a week. And it was a great experience in taking charge of an open source project. 

From having to look through release-scheduled PRs and Issues, to leading a meeting and speaking for 1 hour and 40 minutes (Felt like forever!), and really treating the Telescope project as your own, carrying the responsibility of maintaining and managing it.

OUR Telescope

As a Sheriff, you have to have some sort of ownership to the issues and PRs at hand. Even understanding only 50% of it is enough since the assignee should most definitely be able to explain the issue for you. (Big props to Dave, who would often clearly explain most of the issues in telescope right now) Once you know the context of the issue/PR it gets easier to ask the questions and pointing out code in reviews.

Being Sheriff really encouraged me to step out of my comfort zone, speaking on issues that I'm not even sure if I understand correctly and asking questions to better make sense of them. Part of the journey of being a better developer is learning more things, and admitting not knowing everything. (Dave will always just admit when he doesn't have knowledge on issues or topics and I think that's quite relieving to hear for us developers who suffer from chronic imposter syndrome 😁)

Communication

It was really great, leading a meeting really pushed me to take initiative being vocal to get the other people to talk. I really hate the awkward silences that happen mid meetings (even though sometimes people definitely need breathers) I just have a personality that get a little anxious about them so I felt like I was moving at a fast pace in the beginning, but slowly and surely adjusted to the rhythm at which people were speaking and taking part in the conversation.

Planning

And since last week only involved planning and issue backlog updates, we were relieved of having to take care of the Release this past Thursday and handed that to our fellow peers Tue and Francesco :) (who happened to break production on Thursday... 😅 Not the Sheriffs' fault! in fact props to them and Dave for amending the situation quickly 🙌) So thanks guys. They've definitely done a much better job than I would have releasing it.

Conclusion

All in all it was really great experience leading a meeting and managing a project even if it's just a little taste. Obviously still getting used to the ropes of it but it definitely gave me lots of insight on how to be a better developer as a leader or in a team.


Will speak more on the Telescope 2.7 developments in the next post!

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