Skip to main content

Getting more difficult?

 

Release 0.2.4

Now I am at almost the end of release 0.2 and I chose the telescope as the final contribution. To be honest, this is huge, well organized and great project and it is first time to take a look. Unlike my previous assignment during the previous terms, there are tons of what I have never seen.

First, docker compose is great and the document for contribution is very clear. Of course, I had no idea when read it first, but every time as my professor mentioned, there was a great guy, helper?, helping me a lot to set up the project. Although I had no idea about Elastic-search and Redis-cache server, I was happy to take a time to look though the codes and to understand.

Again, trying to understand an issue is always hard for me and sometimes I am really not happy when somebody does not understand my question. This happened again.

The reason why I attached the picture is that I am still confused about the whole process of this project especially about why frontend didn't get the error at the time. Hopefully, I will get the idea because I spent more than 4 ~ 5 hours to discuss and I am not really happy.

Backing to the issue, my issue was to reduce amount of JSON data removing text property, which is the biggest amount in the data, and checking score property since it is only used for sort.

Since I didn't get the whole process of the project, I asked a lot to check if I was on a wrong location, which maybe caused a guy frustrated. There were a lot of discussion about miscommunication and it turned out that I did not know about elastic search and it provided sorted data already. I have learned a lot but again it was not easy. Anyway, once I fixed the issue, I made a PR.

Surprisingly, it also provides a template for PR, which is very convenient.

In conclusion, contributing my code online is not easy especially when the discussion is needed.  However, it is true that I have learned a lot from this open source world and I believe that I will be also an helper to help other junior developers like me to improve their skills.

P.S. I am scared of release 3 LOL.


Labels:

Comments

Post a Comment

Popular posts from this blog

Working with telescope

   Starting... This lab is to help students to communicate with a big project, telescope, and understanding how to handle with the set it up. There were a lot of trouble since many of technologies are new for me such as docker, docker-compose, elastic search ladis, pino, and so on. Let's jump in the big project . Progressing... The first step I took is to install wsl 2. It is not very difficult since microsoft provides good instruction, link . Although the telescope provides very good instruction,   here , It was not really easy for me to get a concept and set it up successfully. Therefore, I needed to ask a lot of questions on slack, telescope channel. Some helped me a lot and explained so much and finally I got it work successfully.  After my server was working locally, I didn't have any issue to get the response from the url, http://localhost:3000/posts.  To communicate with the local server, actually I needed to change my code a lot since I wanted to sp...
Post a Comment
Read more

Finally, release my first open source.

  Starting... This lab is to release my product to install easily. Instead of cloning or downloading and setting it up manually, it provides a lot of convenience for users to install it. I chose NPM since I used nodejs. NPM  is a great site to help develpers to release their git repository in the site.  Progressing... First, I signed up on npmjs.com and logged in the site on the console to release my repository. I had to set up a lot of things like 'npm init', modifying readme and package.json to be ready.  Second, I tried to release my repository by the command, 'npm publish --access public'. Unfortunately, the name, http-parser, was already taken, so I needed to change my name. I chose my name as http-checker and tried to release it again. At this time, I got 403, forbidden error. I spent a lot of time to figure out but it was actually due to not verified account. Once I got the verified email account, finally, I got the release version of my repository. Here is my...
Post a Comment
Read more