New Beginnings


    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 capabilities of what this repository is capable of. I will also research what Twitter Will allow me to do. I have already read stories about people being blocked on the Twitter API due to following too many people in a short amount of time. Finally once I have an understanding of some of the code I will attempt to solve an open issue.


    After examining the architecture of this repository, I noticed that the code came with a learning curve. The builder of this repository had architected this repository in such a way that was very difficult for me to understand. In order to reduce the lines of code needed, in order to build this project, The repository owner nested classes within functions that also included other functions. After a painful four hours of reading and understanding how the code worked, I took a look at the open issues on this repository. It turns out that I could not find a single issue that I could contribute to. Although my ambition was high, I decided to swallow my pride and give up on this repository. I decided to tackle an issue in the Telescope project that was within my skill range and test my abilities and knowledge.


    I started by looking at the open issues on the telescope repository. I found this issue with the following tags "css styling",  "enhancement", and "nice to have". This sparked my interest since I knew I would not have to fully understand the back and development of this project, but still be able to make a meaningful contribution. his also gave me the opportunity to apply my previous semesters experience in development using React. The repository asked that I make a bottom bar for users using telescope on their mobile device. I have never created anything using React and thought it would be a wonderful experience to fully create a component myself. 


    In order to accomplish my goal of creating a react component for the telescope repository, I have decided to re-learn the basics of react and how I am able to use the built-in components, state, routing. I will keep my blog updated with my continuous progress and the challenges that I encounter.









Comments

Post a Comment

Popular posts from this blog

Working with others

     This week our course was given the task of creating a cli command, which included our code being reviewed by one of my classmates. Initially, this gave me some anxiety as sharing my work with others is not my strongest suit. Nonetheless, I created a post asking if anyone was looking for a partner and Michael Appeared.      It turns out that having someone look over my work was much less scary than I had initially anticipated. Working with Michael was actually fun, and having the opportunity to look over someone else's work was a great learning experience for me.       With another pair of eyes looking at my code, Michael noticed errors and instructions that I was not addressing. Some instructions I had forgot to mention include the fact that my program requires bash. It did not occur to me that most of us live in a Windows Operating System. Another missing component was my Blog link in my READme. I had forgotten to include a link to my blog! As soon as Michael notified me he w
Read more

The Progress

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 
Read more

We are off! V0.1

Initial Release V0.1  Our first Assignment was to create a command-line tool to check and report dead links in a file. Status code 200 would be considered "Good", 400 and 404 is "Bad", and all other status codes are considered "Unknown." My first experience creating a release was nerve racking. With no instructions on how to approach this problem, I started to brain storm ideas, and eventually started questioning my abilities. Inevitability, I chose to do my assignment in bash since it would allow me to colour my code, as well as create a command line tool. Overall, the first assignment was fairly simple to use. Simply clone or fork the repository, open up bash, and run the command. Command : ./cliCommand <filename> NOTE: This project will need Bash installed on your machine. Mac OS has bash built in, however, Windows OS may need to install Bash. Please feel free to play with codes, if you have a crazy idea, then pull request :) Usage and Features Us
Read more