Skip to main content

Week 3 Learning Journal Post

 Part 1

From my previous post I need to improve on making every hour count. After reviewing the website AcademicTips.org I learned some good strategies on the Time Management page. I have started to really lean on making a weekly schedule and allocate my time for the week. I like to be able to visually see my schedule in google calendar and this helps me stay on track to prioritize my work. Having the schedule also helps me to have a reason to say no to unnecessary activities. I find that I have a reason to say no, such as I unable to attend because that time has already been allocated for studying. I do leave some room for flexibility however, because the plan is for the week I find that I sometimes need to make adjustments to fit unforeseen events into the schedule. I try to focus on consistency and not perfection.

Part 2

This week we learned a great deal about ethics. What I found most helpful was the ethics frameworks. I can understand ethics in general terms, but having the frameworks really helped me understand how to define specific ethical ideas. I find that I am able to better articulate why I think something is ethical when I categorize it into one of the frameworks. I can use care ethics to explain why people believe it is right for them to prioritize their own family members over strangers. The ethical frameworks will be incredibly useful as we start to write our Ethics Arguments papers in CST300.

Part 3

This week we also read an article about what every Computer Scientist needs to know. I will say it was a large amount of knowledge. I can understand why the topics are important. For myself, I had considered knowing how to code as the only thing Computer Science major's needed to know. However, this article highlights how being a Computer Science major is more than just being a coder. Coding is the action but it is supported by the knowledge gained thorough studying additional topics such as Mathematics and even effective communication. I intend to use this article as a guiding document of sorts to point me to areas where I can continue my learning and what areas I can consider when trying to improve in my career. 

Part 4

During this module we also reviewed the CSUMB CS Online Code of Integrity document. It contained guidance for integrity while working through the CSUMB CS Online Program. I think it is important to maintain integrity while completing the CSUMB CS Online program because it is the right thing to do, but also because the most benefit will be gained by completing the work on my own. I also think that earning it while maintaining my integrity will reflect better on myself, the CSUMB CS Online Program and my friends and family. 

Comments

Post a Comment

Popular posts from this blog

CST 363 - Learning Journal Week 7

This week we learned how to implement a different type of database using MongoDB. For our group project this week we changes the SQL code to MongoDB code. Both of these database applications do a fine job of working with data and saving it to a database. I did find that MongoDB seemed more streamlined than working with SQL. With SQL there seemed to be more setup as in creating prepared statements, and then executing queries. With MongoDB it seemed like a good chunk of the code was abstracted away and this made for cleaner looking code at the call site. If I had to choose I would likely go with MongoDB as it seemed more approachable.
Post a Comment
Read more

CST335 Week 7 Journal Entry

 This week I learned about input/output (I/O) devices and their interactions with the operating system (OS). Two types of devices I learned about were block and character devices. Block devices, like hard drives and SSDs, store data in fixed-size blocks and allow random access, making them ideal for large data transfers. Character devices, such as keyboards and mice, handle data streams one character at a time, supporting sequential access. The OS play a crucial role in managing these devices through device drivers that provide a standard interface to interact with the hardware. Performance characteristics of hard drives, such as seek time, rotational latency, and transfer rates, are pivotal in determining overall system efficiency. By calculating transfer rates for different workloads, I learned how disk access patterns significantly impact performance. Additionally, understanding RAID levels provided insights into how redundancy and striping enhance data reliability and performan...
Post a Comment
Read more

CST363 Learning Journal Week 4

 This weeks learning journal prompts are: 1.  Briefly summarize 5 things what you have learned in the course so far.   2. List at least 3 questions you still have about databases. 1. SQL - Learning how to use SQL was great for me. I had never previously used SQL and I found it to be a very approachable and simple programming language. I learned how to perform queries and build tables to organize data in a manner that was accessible and practical.    Entity Relationship Diagrams - These diagrams I found to be very useful in the initial build out of a database and helps create a visual representation of entities, their attributes and relationships. The ERD can also be used to generate the code required in SQL to model the ERD.   Database Design Process - The text and lectures provided some good guidelines on the process to create a database. I learned how to understand the database requirements by speaking with the end users and also the process of analy...
Post a Comment
Read more