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

Week 4 Learning Journal

 Part One: Educational Goals The biggest goal I have is to graduate from the CSUMB CS Online Program at the end of 2025 and receive my diploma. I plan on attending the graduation ceremony in person and walking across the stage to receive it. I feel that continuing to envision the actual diploma will help to continue to inspire me to work towards that goal. Part Two: Career Goals One of my biggest career goals is to find employment as an iOS mobile app developer after graduation from the CSUMB CS Online program. I feel this is possible and in addition to the degree I plan on releasing at least three more apps to the app store before graduation.  Part Three: ETS Computer Science Test After reviewing the overview and the sample ETS test I feel that I would likely score in the 50th percentile. I am not too worried about my score because I know I can improve it by reviewing the topics listed in the test. Most of the information on the test I am familiar with but I know I will need ...
2 comments
Read more

CST 338: Week 4 Learning Journal - Markov Project Peer Review

For the Markov code review I worked with my teammate Brandon Hoppens. My strategy for the Markov assignment was to first read through the entire prompt and ensure that I had a general idea of what the program was supposed to do. I then worked through the prompt building each method before moving on to the next. I built all of the methods and then ran the test after my initial build. I was able to pass a few of the test and failed others. I then went back to the individual tests I failed and manually debugged them. This was in contrast to how Brandon tackled the prompt as he was implementing the methods as they were needed. He worked to ensure each piece that he added worked with the existing code base. I think I would change my strategy to adopt some of his methods and use an incremental approach. I relied on building the entire program before running the first test, and I can see how on bigger projects this could lead to some frustration.  The feedback I received from Brandon was ...
Post a Comment
Read more

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