Week 3 (1/22/2025 - 1/28/2025)

(Click on READ MORE for better formatting)

    Hi everyone, welcome to my third blog! This week I will be reflecting on a few resources that I read in the Module 3 lecture material of CST 300 Major ProSeminar.

  • Part 1: Reflection of Learning Strategy
    • For the document I read in Module 2, I listed the top learning strategy that I am weak in as being "Religiously maintaining a schedule." On this website, there are some additional tips on how to make a good schedule. For example, the site provides a "study hour formula" that is used to determine how many hours you need to allocate for studies every week. And no, it's not the typical per unit formula. Instead, it is based on the perceived difficulty of a course since there are easy 4 unit courses and hard 4 unit courses. Some find certain courses more difficult than others, so this type of calculation is tailorable to the individual. It also provides advice on how to create a daily schedule, such as engagement books, a piece of posterboard, or 3x5 cards. Next, it suggests that you put down all necessities, then study time based on the formula mentioned earlier. It mentions the importance of study breaks, about 10 minutes an hour. It also mentions that perfectionism often gets people nowhere, along with learning how to say no when things conflict with your schedule. All of these skills will certainly help improve maintaining a schedule more than I currently do.
  • Part 2: Summarization of the week
    • In addition to the material learned through this week's lecture material, Week 3 also introduced the discussion on ethics, alongside wrapping up the Industry Analysis paper. The presentation on ethics outlined several different key frameworks, including Ethical Relativism, Utilitarianism, Care Ethics, Ethical Egoism, Divine Command Theory, Natural Law Theory, Kant's Ethics, and Virtue Ethics. Like the weeks prior, I also furthered my learning on teamwork and groups via OLI.
  • Part 3: Reflection of "What a Computer Science Major Needs to Know"
    • The website first starts with the idea of portfolios vs resumes. The author claims that resumes, alongside GPAs, cannot allow employers to directly judge the abilities of applicants. Instead, it is recommended to create a portfolio with open-source projects that demonstrate an applicant's skill. Oftentimes, GitHub is used for this endeavor. Next, the author outlines the importance of technical communications for computer science majors, stating that they must practice persuasively and clearly communicating their ideas to non-programmers. They also underscore the importance of having taken a relatively substantial amount of mathematics and physics in order to work better with engineers, as computer scientists do work with them sometimes. Due to the prevalence of Unix systems, they also recommend that computer science students become familiar with Unix systems and the philosophies named after it. Finally, he suggested to gain some understanding of discrete structures, data structures, theory, computer architecture, operating systems, networking, security, cryptography, software testing, user experience design, visualization, parallelism, software engineering, graphics, simulation, robotics, artificial intelligence, machine learning, and databases. Certainly, it is a lot to cover, but a general computer science degree such as the one offered by the CS Online program is expected to deliver at least a surface level amount of knowledge in most of these areas. The program's course lineup reflects this as well.
  • Part 4: Reflection of CS Online Integrity Code
    • Academic integrity is a serious discussion regardless of discipline, and computer science is no exception. However, due to subject's nature, academic dishonestly appears in different ways than other fields. For instance, plagiarizing in computer science is typically in the form of one who submits program code they did not create without the proper credit or authorization to do so. In most fields, plagiarizing is most common when writing papers or scientific journals. There are three basic rules, those being to not submit solutions or program codes that are not your own, sharing solution code with other students, and indicating any assistance received. To conclude, the CS Online Integrity Code upholds student honesty and the CS program/CSUMB's reputation as a whole.
That is all for this week, see you in my Week 4 post!

Comments

Post a Comment

Popular posts from this blog

Week 32 (8/13/2025 - 8/15/2025)

     (Click on READ MORE for better formatting)      Hi everyone, welcome to my 32nd  blog!  This is the Week 8 post for CST 334 Operating Systems. Write a 1-2 paragraph journal post, of at least 250 words, summarizing what your biggest takeaways from CST334 were, including any major challenges or topics you found particularly interesting. One of the major challenges in this class (at least for me) was wrapping my head around some of the long math-style problems that have been seen throughout the course. Thankfully, I was able to get a lot of practice with these through labs, ungraded practice quizzes, Midterm Preparation Quiz, and Final Exam Preparation Quiz. In addition, members of my team were able to help me better understand what was needed to tackle these problems. For example, Wootark Kim (Tom) made a step by step video for me and the rest of Silicon Surfers that explained how to do CPU scheduling problems featuring the RoundRobin policy. V...
Read more

Weeks 41 - 48 (10/26/2025 - 12/19/2025)

     (Click on READ MORE for better formatting)      Hi everyone, welcome to my 41st-48th  blogs!  This is the Week 1-8 post for CST 336 Internet Programming. Similarly to CST 311 Introduction to Computer Networks, while journal entries were not required  for this particular course, I wanted to document the concepts and assignments from each week of class. If you would like to see some of these projects for yourself, this link acts as a homepage to visiting all of the projects described below! https://bevans34.github.io Week 1: HTML and CSS This week's primary focus was on learning/practicing creating a website using H yper T ext M arkup L anguage (HTML) and C ascading S tyle S heets (CSS). Highlights from this week included centering a <div>, which is probably one of the biggest memes to ever come out of web development. Labs: 1 - ePortfolio Site In this lab, I created a site hosted on GitHub Pages that features a homepage, about page,...
Read more

Week 24 (6/18/2025 - 6/22/2025)

       (Click on READ MORE for better formatting)      Hi everyone, welcome to my 24th  blog!  This is the Week 8 post for CST 363 Introduction to Database Systems. Briefly summarize what you consider to be the three (3) most important things you learned in this course. How to query in MySQL and MongoDB, including select, insert, update, and delete. This also includes advanced querying techniques, such as subselect. Understanding schema structure of MySQL and MongoDB. After all, for the above to work you need a schema to create/use the database and establish table structures! Creating EER diagrams can also be bundled into this section as it is related to schema creation. How to take database systems and turn them into real-world solutions. For instance, using the JDBC API to create a webapp with a MySQL or MongoDB foundation. This was explored in group labs 19 and 21. That is all for this week, see you in my Week 25  post! Onwards to CST...
Read more