Final Reflection

    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 pushing 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 goal of creating a bottom bar for mobile usage. By starting with the most basic components necessary in order to build my bottom bar, I was able to quickly and efficiently decipher which components needed to be built first.

    The most difficult part that I had to implement was probably the toggling of icons if the use was logged in. I had completely forgotten how to use the useState & useContext. Using the tools provided by the framework react I was able to find an efficient solution to display the correct component when necessary. Looking back, it might’ve been more efficient if I had asked the slack community to provide me with some guidance on the steps I should’ve taken. Thankfully, google had my back and I found all the necessary information I needed. Next time when I encounter a situation I will consult others on their opinion on the matter at hand.






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

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

Lab 2

     Started my morning a little rough, however, I managed to get online to start my lab 2. I randomly selected  https://github.com/yuanLeeMidori/OSD600.GoodLinkOrBadLink as a repository to begin with. As I kept reading I noticed this project was not for me, I have never worked on .NET platform and do not plan to anytime soon. However, upon reading the READme file I noticed some sentences that could use some grammatical help. I took this opportunity, to practice how to create a pull request. I knew this wouldn't count for my lab 2, however, decided it was worth the experience. I followed the given instructions and successfully created a pull request. Later on I'll talk about all the requests that have been accepted or not. Here's the rest of my story: Who did I help? Roger.  What was Rogers Project? Roger was working on Cligon a program that stands for Check if Link Is Good Or Not. how did I contribute to Cligon? I added a requirements.txt file to Rogers Repository. This r
Read more