Week 3: Weekly Learning Post

 

Part 1

Last week I chose to improve my late study times. However, I think sometimes I overstudy or worry too much about assignments. I decided to explore general stress reductions tips. I agree and I believe I am starting early so I won’t be pressed for time. I also agree that long hours of studies sometimes aren’t as productive, and I will work on taking more breaks in between study sessions. I will add more exercises routines in between study hours.


Part 2

This week we explored the different ethical frame works. It’s interesting what motivates people to do one thing in case but another person the opposite. I found it fascinating to reflect that sometimes there is no “right” or “wrong” answer but instead to view from a different angle, on what is the rational or motive behind the reasoning a decision. Social and culture influences us a lot of our decisions on what is moral or not.    

Part 3

A Computer Science Major needs to know various things to be successful not only in the studies but for the future. There is a wide area of information to learn as a computer science major, such as math and engineering principles down to be better able to communicate with non-computer scientists. One thing that stood out was making a profile and keeping projects in it. Sometimes, we get caught with assignments and forget to look at the bigger picture. After we are finished here, we need to present future potential employers of our work.

 

Part 4

Personal integrity and collectively equalities to reputation. Some one can put the illusion of having integrity but sooner or later it will be discovered. Submitting solutions or program codes that are not one’s own work will possibly help to pass an assignment or even a class. However, this person will be doing serious damage to himself or herself if discovered. In addition, not doing it on one’s own leaves out important skills that one cannot gain from cheating.  

Comments

Post a Comment

Popular posts from this blog

CST438 Software Engineering: Week 8 (Final week)

 One of the most important things I learned is that software engineering is about much more than just writing code. While coding is a big part, there's a strong emphasis on documentation, understanding client needs, and getting continuous feedback. It’s about designing systems so others can easily improve them and applying principles like "low coupling and high cohesion" to keep things modular and maintainable.      Another key lesson was understanding the entire development process from end to end. This was the first time I worked with both the front end and back end together, fully grasping the HTTP protocol (including how methods like POST work), how JSON is used, and how the front end communicates with the back end. Seeing how everything fits from database interactions to deploying the app online—gave me a fascinating glimpse into the full workflow and a lot of practical experience.      Another important lesson was learning how to work as part of ...
Read more

CST438 Software Engineering: Week 1

What did you expect a course in Software Engineering would cover? I expected it to cover how to build applications from the ground up and the design behind application development. I thought we would look at other things we’ve been learning in this program, like database management, front end development, and back end work, and then put it all together into one complete project. After completing week 1, how has your opinion changed? Well, I never really thought much about keeping an application’s design maintainable for future improvements or changes. There is a lot more that goes into software engineering than just simple programming. It is  about planning ahead, documenting your work, checking for errors, and testing properly to avoid issues later. I’ve also realized software engineering looks at the big picture it is not just about coding and design but about how software impacts people and how teams work together to build it. Developers need to stay motivated, think critical...
Read more

CST370 Week 5

Hello everyone,  This week we studied binary‑tree traversals preorder, inorder, and postorder but I kept mixing them up. I finally got it when I attended TA office hours, and it clicked. Walking through Quick Sort step by step helped me see how the Decrease and Conquer approach works by breaking problems into smaller chunks. Then we looked at Kahn’s algorithm, and watching it remove nodes with no incoming edges reminded me of picking a pivot in Quick Sort. Seeing these patterns repeat helped me realize that many algorithms work by simplifying things piece by piece. 
Read more