“For weekly documentation, consider the following learning points:

Computing for Design Reflection Essay

Welcome

I’m always trying to improve the way I’m doing my documentation, so will be trying to be more concise and trying not to add things for the sake of adding things. If there are weeks that are empty, its because I don’t think there is much that is needed to be said. Concepts are also kept as brief as possible and it assumes some prior knowledge to my projects and ideas

Here’s some general things before I get into the weekly stuff:

Lessons

I was able to follow along every lesson and understood the concepts taught. The only lesson I felt was slightly confusing was the one about classes and constructors, but I eventually got it. There will not be much about what we did during lessons (except for consults).

ChatGPT

I found that using ChatGPT was more difficult, because it added things in my code that I didn’t understand, or would approach things using a different logic. Ultimately it was easier for me to construct the code myself as opposed to trying to restructure what ChatGPT would give me.

Based on what I observed, using ChatGPT once would create a code that only ChatGPT could “fix’’, because constantly feeding ChatGPT code back into ChatGPT creates more problems and makes the code even longer and more undecipherable, it seemed like ChatGPT only added more variables on top of what it already added as opposed to altering the initial logic that it had.