Nathan Capstone Blog

I suppose my greatest success was finally figuring out how to get to use GitHub to have code I was working on locally get committed and pushed on to GitHub, and how to pull and merge my branch with the main branch. Because it’s been more than two years since I used to GitHub, and even at that time it was not done in a collaborative setting, so when starting this project I really did not know what I was doing, and when I tried to make a pull request I would feed back from teammates saying how my code was not up to date, and how I had erased some of their code, and there were merge conflicts. So finally, after not doing it right for so long, I was able keep my code up to date and resolve merge conflicts. This may sound trivial, but I think reacquainting myself with the tools was probably quite useful.

As far as SWOT goes, I suppose the strength of the course is that it introduces you to working in a collaborative environment, and the tools that are necessary for that, which was not something that I otherwise had. Furthermore, the project may have served as a good opportunity to learn something that was not really addressed in the course. I also thought that the course was good in that in encouraged students to do things to prepare for finding a job. Also, because of the collaborative nature of the project, there was some networking opportunities. I guess the weakness was the short amount of time we had to do it. Otherwise there are not really any threats I could come up with. From a purely personal perspective, I think it would have been good if perhaps there were more projects related to systems programming, but that is just a personal preference.