Release 0.2

Hello everyone again,

So, I have been thinking about the project that I am working on, and I saw that the projects that I chose was quite hard, so I decided to chose other projects to work on, which is about C++ and Java mostly. More update will be coming by the end of this week. I am working hard to solve the issues due to the busy of this week’s tests and exams. I am sorry for the delay.


Lab 3

Hello everyone

So It has been a while since I started learning about Open Source Development, and of course being open also means you can help contribute to other people’s project too. I have always love to coding with JavaScript and C++ and doing Front-end development in general. After a long time searching through collections in GitHub, I have finally chosen BananaBread, Command & Conquer and Untrusted as project that I am interested in

1. BananaBread

BananaBread is a compact and efficient 3D game engine according to the author that use JavaScript and WebGL, with it programmer can build a First Person Shooter game in web browser. I chose it because I am interesting in the idea of an 3D game engine and shooter game, it also uses C++ language, which is one of my favorite language and the one that I am familiar with. I would like to help with any issues that was posting, or even test the project and post issu by myself. I think I need to dive deeper into JavaScript and C++ language to be able to contribute.

2. Command & Conquer

This is one of my favourite, because it is my favorite Real Time Strategy game that are made in HTML5 and Javascript. I have been learning some Web’s language, so that is why I would like to have project that I can contribute to. I will also try to support this project with my knowledge, although it maybe not enough.

3. Untrusted

This is an interesting one, becasue it is an Meta-JavaScript Adventure Game that is running on Javascript, and the gameplay is really interesting. It is running on Javascript, so I can learn alot from this project, and also help with whatever I can.

So that is it folks, I hope that you are interesting in these projects just like I do, see you later in the next lab, cheers.

Lab 2

Hello everyone,

So I have been using Git for about 3 weeks now, and frankly, I still feel like I got a lot to learn in order to fully use Git’s potential. This week’s lab is to find some new Git’s command to work on, and I found out some interesting commands to learn and apply. This blog will introduce how to use git-grep and git-show.


git-grep is used to print lines matching a pattern and easily search through anything. It will try to look through the files in the current working directory.


Search working tree for text matching regular expression regexp:

git grep <regexp>

Search working tree for lines of text matching regular expression regexp1 or regexp2:

git grep -e <regexp1> [--or] -e <regexp2>


+git-grep doc link:

+git-grep references:


It is used mainly to shows one or more objects (blobs, trees, tags and commits). This command can be useful when you want to search for some elements


Shows the tree pointed to by the tag v2.0.0

git show v2.0.0^{tree}

Shows the contents of the file Documentation/README as they were current in the 10th last commit of the branch next

git show next~10:Documentation/README


+git-grep doc link:

+git-grep references:

Overall, these commands can prove useful to me in the future for me. In the mean time, I will try to use these commands more to understand them properly. Thank you for reading.

Release 0.1

This is my first large project for OSD600, so I am still pretty bad at fixing the code and use git features. It is also my first open source contribution ever for Github. So I will tell you how I got it all figured out.

1. Process

+Firstly, I need to pick a file to work on. By the time I started to do the assignment, a lot of files has already been chosen, so I finally decided to choose fs.lstat.spec.

+After I have chosen the file I wanted to work with, I forked the Filer directory.

+When I had made sure the forked repository is in my GitHub account, I started to clone the repository on my laptop to work with the project locally with the “git clone” command line.

+ I tried to install the npm first by typing npm install, then I ran the test to get the result.

+After I made sure that everything runs fine, I went to the issues tab and posted my issue there.

+I tried to create a branch with my issue number and then edit the Github repository file with my local machine file.

+Lastly, I pull a request to the original repository, set a name for it and added description.

-My issue link:, I tried to fix the var into let and const in a correct way and added strict mode in.

-My pull request link:

-My review’s link:, I found out that he forgot to change some let into const.

That was all the steps that I needed to do this project.I did have a look back at the review comment and changed what I needed. l I did learn a lot about editing code, finding mistake and understand more function on GitHub.I would try to pull the request by command line next time to know how to to it differently. I thought it would be easy but turns out it was quite time-consuming. Thank you for going through all of this with me, I will see you on the next post.

First Blog!

Hi whoever come here,

I have been coding for quite long, and this is the first time I created a blog for my studies. Here are some of the results of my researches and learning hours on the subject of Node js fs module.

1. fs.unlink(path, callback)

This function is used to deletes a file or symbolic link Asynchronously. When a callback is done, no argument except a possible exception will be given. It will not block your code, and will call a callback function once the file has been removed.

// Assuming that 'path/file.txt' is a regular file.
fs.unlink('path/file.txt', (err) => {
if (err) throw err;
console.log('path/file.txt was deleted');

2. fs.unlinkSync(path)

Not like unlink, fs.unlinkSync(path) delete file synchronous manner.It is synchronously, so the synchronous call will cause your code to block and wait until the file has been removed.

const fs = require('fs')

const path = './file.txt'

try {
} catch(err) {

+ References: