What did you do this past week?
In the past week, I finished all my homework and practiced coding almost every day. I managed to keep up with my schedule and became more punctual. I’ve been trying to build up some little habits, which would help balance work, study, and life.
What’s in your way?
I struggled to get enough sleep for the past week. There have been some projects in different classes, and at times I will forget when I should go to sleep. I slept pretty late for the past week, which harmed my concentration during the day time. In retrospect, there are things I can do better.
What will you do next week?
For the next week, after I finish up the Collatz project, I will keep on doing what I’ve been trying to do. I may have to be more strict with myself as there will be more projects and homework incoming.
If you read it, what did you think of Continuous Integration?
I learn that continuous integration is an extremely important practice in the software engineering world. It can effectively reduce time spent on the development and elevate the coordination of the engineering team.
What was your experience of Collatz? (this question will vary, week to week)
I built a similar Collatz project in CS373. However, doing it in C++ and Python is kinda different, as there are more details to look into for C++. Overall I understand the concept of the project.
What was your experience of exceptions? (this question will vary, week to week)
I knew about exceptions, but I can’t say I am good at it as I rarely used them whether during building the project or during debugging the code. It would be great to use it a bit more.
What made you happy this week?
It’s been a while since I touched on C++, so I am happy to work on this project just to refresh my memories of the past C++ knowledge and learn more during its development.
What’s your pick-of-the-week or tip-of-the-week?
I read an article https://www.freecodecamp.org/news/how-to-write-a-good-software-design-document-66fcf019569c/, which is about writing software documents. It kinda reinforces my understanding of the importance of good software docs. I had not yet got the chance to write a lot of software documents because I had not been in such a position for a while, and I found the article interesting. It is very informative and has many critical points about documentation laid out. I guess I will look into it again once I have the need to write software documents.
