Week 3

 Part 1 – Study Tip Reflection

One of the areas that I recognized was a weakness for me was being consistent with the SQ3R Method. After reviewing the strategies through www.academictips.org, I understood that my biggest gap is with the Recite and Review phases. I find that I often read and highlight, but I do not actually engage with the content out loud in the Recite phase, and that I do not go back to the text after I have read it the first time unless a test is looming. From the tips I learned it is so important to make reviewing a habit and not just a hurried attempt when you need to prepare for assessments. I will start summarizing readings in my own words, and will review them constantly so that I can hopefully build better retention. 

An area that I am actively working on is not being a passive reader. I tend to over-highlight thinking that will help me later, then I forget why I highlighted what I did. I am going to start  shifting from longer cramming sessions to shorter study blocks with breaks, it means study for 40 minutes and take 10-minute breaks. 

Part 2 – Ethics Material Reflection

This week's ethics materials made me think about the responsibility we are going to carry as future computer scientists. The talk about ethical frameworks helped me understand that people think about justifying their decisions very differently, such as who is affected by the decision and outcomes, duties, or self-interest. For example, in my ethics essay about self-driving cars, I will write on why some people might support or argue from a Utilitarian point of view (maximizing safety for everyone), while others might argue from the one of Egoist self-interest (companies wanting to maximise their own freedom of innovation). 

Part 3 – Reflection on "What a CS Major Needs to Know"

Reading "What a Computer Science Major Needs to Know" was an eye-opener. It helped me understand computer science is not only about coding, rather it is more about thinking deeply, solving problems, and having a lifetime of continued learning. Algorithms, data structures, and version control are not particularly easy topics, but they are the foundation upon which real software development is built. I also understood the amount of self-teaching we will need to do as well. 

Part 4 – Reflection on the CSUMB Code of Integrity

When I read the CSUMB Code of Integrity, I thought about what kind of student and professional I wanted to be. In a major like computer science where collaboration is common and the internet is full of helpful resources, it's really easy to want to cut corners or "borrow" ideas, but it's not only damaging from my experience and learning, but it also destroys the credibility I might have as a future professional. I want to be the kind of person that others would trust, ask for help when I need it, and even ask for an opinion. Academic integrity is much more than a rule, it is at the foundation of everything we create.