Introduction

-

 Hi, my name is Hyunji Lee and I am taking OSD600 (Open Source Development) course which is one of the professional options at Seneca, CPAC (Computer Programming and Analysis with Co-op) diploma program. Currently, I am located in Toronto. I do not go outside like before due to COVID-19. It is a little bit boring but I think it is a good chance to improve my developing skills in this situation.

I have developed a variety of programming skills at college and am trying to improve my skills. Specifically, I have an interest in web development. This website named BookEat is the one I have created with my team a few months ago. We used a MERN (MongoDB, Express, React, and NodeJS) stack application with a platform named Heroku. We managed our codes using git and that was impressive. As I usually manage my codes of my personal project using git & GitHub, I thought I know how to use git. However, when I was using a git for the team project, it was totally different. I should think about the collision, merging, branches, etc. I got I need more experience with the git.

This semester, I saw a course related to learning about the open-source is open. When I checked the course outline, I feel this course is the one I want to. I can learn about the git, how to contribute open-source, and how to find a bug in a huge project. I believe these skills will be great assets in the future.

The Github repository I forked from trending repositories is named generator-jhipster. When I looked around the jhipster’s website, it said JHipster is a development platform to quickly generate, develop, & deploy modern web application & microservice architecture. As the most interesting subject for me these days is a web application, I picked this open-source. I would like to look around this project later on. This is the repository I forked generator-jhipster.

Comments

Post a Comment

Popular posts from this blog

Lab 8: Automated Testing and Continuous Integration

-
When I developed a program, it was time-consuming to test all the functions I created when I add a feature. I needed to run each feature, check whether it gives expected output or not, and check all the output. It is possible I forgot to test a feature and later on, I realize I did not test the feature. I wonder if there any ways I can do it automatically. Now, I got the way how to do that. There is automated testing for it! To begin with it, I started searching the testing framework to apply my command-line tool named url-fi. There are some testing frameworks for Node.js such as Jest, Mocha, and AVA. The testing framework I chose is  Jest  which is a testing framework developed by Facebook. I've installed Jest running 'npm install --save-dev jest' and test whether it works properly or not.  This document  is the way I followed to install the Jest testing framework. After I've installed the Jest testing framework, I worked on separating functions. As my tool contains al
Read more

Project: Final

-
Introduction In this post, I will describe the summary of how I have done each stage. The purpose of this post is for wrapping up this project. The purpose of the project is the optimization of one open-source project. I need to compile, benchmark, profiling, and optimize the software. The detailed information about the project is described in the  SPO600 winter project .  Previous posts related to this project The previous posts for this project are listed below. You can read the detailed steps of how I have done each stage. Stage 1 Project Stage 1 - Compiling and Benchmark Butteraugli Stage 2 Project Stage 2 - Profiling Butteraugli Project Stage 2: Profiling (x86_64) The links for the results Project: Organize the Results Stage 3 Project Stage 3: Optimization Stage 1 Stage 1 is for building and benchmarking the performance of an open-source software package. There are some requirements for the open-source package I need to consider. Firstly, the time for testin
Read more

Open Source Project: Lab2 (Pull Request)

-
Image
 Introduction In this lab, I practiced contributing and submitting pull requests to other repositories I don't own. Following the lab instruction , the things I plan to practice are the following: forking and cloning other projects creating branches to work on new features and fix bugs working on code I didn't write, trying to maintain the original style and not break things creating pull requests collaborating with other developers on GitHub updating my pull requests to include fixes for review comments The Project I picked for pull request ( https://github.com/lixiaoqity/testLink/pull/7 ) I looked around the classmates' open source project and picked the project named testLink. The GitHub repository link is the following:  https://github.com/lixiaoqity/testLink/pull/7 .  I picked this project because it also uses the NodeJS which I picked for my project. It was really interesting to see how code can be written differently for the same subject. When I look over the project
Read more