Open Source Development Diary

Sorry my blog hasn't been updating recently, Im so busy getting ready to get in the groove back at home. Im not going to lie the vacation life is great! Waking up at 3pm, taking baths, and the food is ready when I sit down at the table. It's a privilege I take for granted.  Since writing a blog post helps me take a minute to reflect on the experiences I have been going through, I will keep making these blog posts. In addition, I noticed these blog posts encourage me to acknowledge the accomplishments of today, keep me focused on the progress I am making, and finally.. I must work on articulating sentences. Here is a visualization of myself:  An update on what I have been doing. I moved back home for Christmas, I started working on my pool hall app, and Ive been applying to positions. With Christmas break upon us I would like to get some personal projects going. This will give me the opportunity to solidify my knowledge of what I have learned so far. I started working on this po

     If you haven't read the previous blog you can read up about it here .    It was a long 2 days where I had nearly convinced myself I wasn't getting anything done, except for searching for a new repository to work on for my final project. However, after p ushing this pull request I got a burst of confidence in my abilities to work on front end development using React. Finishing this project gave me the confidence to create my own Website using React! You can check it out here, its called the  PoolHallApp . I decided to create this project, since I realized the Pool halls in Toronto use pen and paper to keep track of their customers play time. So I thought they would benefit from a web application to keep track of their customers tabs. I plan to make this a free application for all pool halls to implement into their daily schedule. I will litter it with ads soon. .. Check back in a month.      After completing the task at hand, I believe that I have successfully achieved the

This week I decided on a repository to work on, the telescope repository. I was excited since this was a front end development issue. I had never created my own component before, however, I have some prior experience using React. I started by creating a bottomBar component and locating where I should add this component. I located the PageBase.js, the mobile application interface, and added the component to the bottom of the page. I started by creating a div with a red background to make sure I was on the right track. since it has been a couple months that I have not worked with React, I started with the most basic tasks, such as, creating a react component, a  div element, and rendering the component I made.     After confirming that I did not break anything, I started designing the layout of the desired BottomBar. The idea was created by  agarcia-caicedo,   proposed a bottom app bar t o improve mobile usability. If you're curious on the original idea you can check out his 

     For my 0.4 release I will work on a Python repository called Tweepy. Tweepy is A repository about a Twitter for python. At the beginning of the semester I thought it would be a great challenge to learn a new language that language I chose was python. This release is a chance for me to test my abilities and knowledge about this language.        Reflecting on my previous contributions to open source has helped me become a better python developer.        I chose this project, Tweepy, for two reasons, in my other professional course TEC 70 to our professor taught us the importance of social media. Accentuated the importance of having an online presence. I thought why not kill two birds with one stone. This project will not only create a python but that will create tweets for me but also help me test my python abilities.      I will start by creating a simple Tweepy bot. It seems like a very simple thing to do since it is the most common use of the repository. Next I will see the c

     This week our task was to add tests to our Command Line Interface repository we have been working on this semester. The first thing I did was to read my README.md. This was the first thing I did because it has been a while since I have worked on this repository. Reading this document helps me remember where I left off and remind me off. In addition, I try my best to make small updates to the README file every time I read it. This helps keep the documentation up to date while refreshening my memory on how to use my program.        The framework that I chose to set up for my testing was Unittest. I chose unit test because, while I was researching, I read that developers use unit test since it is easy to read, write, and reliable. The tutorials and steps given on the document were very straightforward and allowed me to start writing my test with little effort. Although, this was my first time writing tests, by reading the documentation I was able to create two tests that checked

Internal Project Contribution In the past and currently, I have worked on several issues within the Telescope community. At first I was worried about understanding other peoples code. However, after looking at a few issues and spending some time on Telescopes repository, I noticed that I could contribute to some of the issues that our community was facing. In total, I worked on three different issues all ranging from different skill levels, the easiest being the documentation update. You can check out the changes that were implemented here . In order to update the documentation, I had to read up on all the different types of logging. I excluded the unnecessary information from Telescopes documentation to accentuate the important details about how to implement the logger. The documentation update got merged fairly quickly, this gave me a sense of relief since I was worried that I would not be able to get a commit in before the due date. Completing the required pull requests for Rel