CST 338 - Week 1

 Hey everyone! 

I am back with another update on my online learning journey. This week we started coding in Java. We used Coding Bat to help develop our skills, and I must say, it was quite a challenge.

    Java was a new programming language for me so it took me some time to get the hang of the language. I had a lot of fun because it was like a challenging puzzle. First, I started by understanding each problem, identifying the expected inputs and outputs. The I started writing the code, implementing one step at a time. Sometimes, I wrote a bit of code to see if it actually works, then moved on to the next part of the problem. Other times, I would write the code how I see fit and then end up debugging one step at a time. 

    For me, what worked was incremental development. Writing a little bit at a time and testing each part as I progressed helped in isolated issues quickly and made debugging easier. Reading the problem carefully, especially giving attention to the variables was an important factor as well. Sometimes I would use the wrong variables for the right code, resulting in errors. 
    However, one thing that did not work for me was diving right into the code. Sometimes, I would not read the problem properly, or pay attention to syntax, resulting in silly mistakes and errors. 

    Rarely did my solutions work perfectly on the first try. It often took multiple iterations to get the code right. Here’s a typical pattern:

  • First Attempt: A rough version of the code that might work for simple cases but fails for more complex cases.
  • Refinement: Identifying the shortcomings of the initial solution and adding necessary conditions.
  • Optimization: Once the code works correctly, optimizing it for better performance and readability.

    •     Although it was quite a challenge, it was fun and I definitely learned a lot. I even learned how to use GitHub, IntelliJ, and Android Studio. I am looking forward to another week of more coding!

    Comments

    Post a Comment

    Popular posts from this blog

    CST 334 - Week 6

     Hey everyone!      This week we submitted our research collab project. It was quite interesting and fun. I learned a lot and our team bonded more as well. We also learned many new things through our lectures and labs.       Concurrency is a critical concept in computer systems, enabling multiple processes to execute simultaneously. However, with great power comes great complexity.       A semaphore is a synchronization primitive that helps manage access to shared resources in a concurrent environment. Semaphores can be thought of as counters that control the number of processes allowed to access a resource. They come in two main types :             - Counting Semaphores : These can have values greater than one and are often used to manage a   pool of resources, such as threads or connections.           - Binary Semaphores : These function like locks and c...
    Read more

    CST 334 - Week 4

    Hey everyone!       This week, I learned about how operating systems manage memory, which is one of their most important jobs. One topic was free space management , where the system keeps track of memory or storage that isn’t being used. Two common methods are bitmaps (using bits to mark if memory is free or taken) and linked lists (connecting free memory blocks together). Each method has its pros and cons, like how much space they use or how fast they work.      I also studied paging , which splits memory into small chunks called pages. These pages are mapped to physical memory, keeping processes separate and organized. However, this mapping can slow things down because the computer has to translate addresses often. To make it faster, Translation Lookaside Buffers (TLBs) store recent translations in a small, quick cache. I also learned about advanced page tables , which are smarter ways of organizing these mappings to save memory.    ...
    Read more

    CST 370 - Week 1

     Hey everyone, This week, we learned several important topics that form the foundation of computer science and programming. We started with GitHub and practiced using manual commands like git init, git add, git commit, and git push to manage our code. This helped us understand version control and how to keep track of changes when working on projects, especially when collaborating with others. We were also introduced to algorithms and learned what they are—step-by-step methods for solving problems. One example we focused on was Euclid’s Algorithm for finding the greatest common divisor (GCD) of two numbers. It uses a simple but powerful idea: repeatedly replace the numbers with GCD(b, a % b) until the second number becomes zero. We also practiced writing pseudocode, which helped us plan out algorithms in plain language before coding. We also had a homework assignment to help us further understand GitHub commands. Later in the week, we learned about graphs, both weighted and unweight...
    Read more