Chuseok and Udacity

Soeun/Sona Lee
4 min readOct 10, 2017

--

*이제 부터 medium 블로그는 영작 연습도 할 겸, 영문으로 쓸 예정입니다. 한국어 버전은 다음링크에서 확인해 주세요 :)

*From now on, I will use this blog to practice writing in english. You can check this link for the Korean version

Korea’s biggest holiday (Chuseok — Thanksgiving Day) is ending. This time is for making Songpyeon (a type of rice cake) using new crop rice, eating freshly picked fruits, making wishes and spending happy times with family

Since this break included other holidays like Hangul Day, I had 10 days off. Because I didn’t have any special travel plans, I wanted to spend this time being productive. I thought about work and projects I put off that I could work on during the holiday. I came up with three things I wanted to work on above all.

Firstly, submit the initial project for Udacity React Nanodegree.

Secondly, write on my blog

Thirdly, work on side projects that I have to finish by December.

The highest priority work is submitting the first project for the Udacity React Nanodegree. Since they are using React at my new company, I want to quickly learn. I registered for the Udacity React Nanodegree course because they held a promotion for DiscoveryWeek

The course consists of React, Redux and React Native. I also have to submit a React related project. I delayed working on this project because I was busy but that was just an excuse. So during the holiday, I decided to spend time working on Udacity. I have to make a bookshelf app that can move books between shelves and add books after searching for books

The first time I worked on this project, I didn’t architect my code, so the structure became stranger and stranger. So I deleted all of my code and restarted the project. I wondered if even this structure was correct, so I discussed this structure with friends.

While eating Songpyeon and fruits, watching the full moon and sometimes doing side projects, I submitted this project

l was really looking forward to getting my project code reviewed.

First review

The first review let me know that I had good parts and bad parts. There were 12 specifications and I had bugs on two of them.

Requires Changes
2 SPECIFICATIONS REQUIRE CHANGES
Well done on your first try!
You did a really good job with your components, they look extremely well written and your code architecture is well structured.
Anyone can see how much of React you are grasping.
There are a few bugs in your code, but from what you have shown so far you’ll fix them in no time (I hope my comments are helpful.).
Keep up the good work!

The detail reviews are shown below.

Also there were suggestions on how to improve my code. I didn’t pass the first project because I didn’t fulfill the specifications.

After the review, I fixed the code, refactored and submitted again as soon as possible.

Second review

The second review is shown below.

Meets SpecificationsCongratulations, your project looks great and you have met all the specifications!
There are no longer issues with your search functionality and you have handled the components’ states perfectly. You have been making a great use prop-types, as well, it will come handy when dealing with redux.
Good luck on your next projects!

Also, they let me know about parts I did well and suggestions on how to improve my code.

Finally. I completed and passed the project. Now I’m preparing for the second project which includes Redux.

Because of Udacity, I avoided being lazy and spent this holiday coding and learning. I’m proud of myself since I started an online course, had my code reviewed, and successfully passed my first project. I hope I get my Nanodegree soon!

--

--