CS373 Spring 2021 Week 3: Vishal Tak
Week 3: Progress in Software Engineering.
1. What did you do this past week?
This past week, I started working on the Collatz Conjecture project and got my implementation to pass the first two tests on HackerRank. I wrote unit and acceptance tests to test my implementation at every stage to ensure the code was correct. I also familiarized myself with the workflow of the projects.
2. What’s in your way?
Honestly, there’s nothing major in my way except some other assignments that I have due around the same time as the Collatz project. I hope to finish the Collatz assignment by tomorrow to give myself some time to work on other classes.
3. What will you do next week?
Next week, I plan on learning more about Docker and passing the last test on HackerRank for the Collatz assignment. I’ve been messing around with some of the features of Docker and hope to familiarize myself with it by the time we get to work on the group projects.
4. If you read it, what did you think of Continuous Integration?
I think Continous Integration is a great tool to find bugs and integrate layers of code when working with multiple people. I think that for CI to be useful developers working on the project need to commit changes multiple times daily to ensure that everything is working properly. I’m excited to use CI on future group projects.
5. What was your experience of Collatz?
I think the Collatz Conjecture is an intriguing problem and solving it was a fun experience. The only thing I have left is optimizing the code using different methods of caching to pass the HackerRank tests.
6. What was your experience of exceptions?
I really enjoyed going through the process of checking different scenarios that could happen with exceptions with Professor Downing. I was able to grasp the concept through the different worked examples explained by Professor Downing.
7. What made you happy this week?
Seeing progress in the process of taming by pet budgies made me really happy this week. I was able to feed them with my hand without them getting scared and flying off.
8. What’s your pick-of-the-week or tip-of-the-week?
You can close issues on GitLab when committing and pushing changes directly from the command line. Simply add “-m Closes #Issue,” where “#Issue” is the issue number, within the commit message.
git commit -m "Finished" -m "Closes #11"
git push
