Lab 5

  

    While closely examining my open source repository, I noticed that I had many unnecessary lines of code. Although program worked, the code was not as good as it could be. Having these unnecessary lines of code had lead my program to be prone to errors. After identifying these issues, I removed them and thus my code was concise and efficient.

    

Me trying to fix bugs in code

    A bug was also found while inspecting my previous code. I had forgotten to implement the function that allows users to choose "-all", "-bad", or "-good". To solve this bug I invoked the function that was already declared. 

   The final improvement was my terrible variable names. While implementing my "--ignore" functionality I used the variables url and url2 to hold the values of the url currently being checked and the url to be ignored. These variables had no description of the values they were holding. I replaced my old variable names with ones that accurately describe their purpose.


    Refactoring my code in small commits has given me the opportunity to work with little to no anxiety. Making small commits reminds me of saving my progress in a RPG game before tackling a hard task. Hitting the save button allows me to try different tactic without worrying about losing the progress of my project.

    After solving some bugs and naming conventions we can run the "git rebase -i" command that allows us to squash all your commits into one commit. Some projects consider this a normal process to keeping their master branch clean. Once this step is complete, I took a look at all of the commit messages by executing "git commit --amend" command. This had allowed me to edit my commit message into a single message.

    Making small commits allows me to take small steps towards a solution. If I make a mistake I can always come back to the place I saved. Whenever I have something that solves a problem in my code, I create a commit on a branch to ensure my previous solution is safe.






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