CSU Monterey Bay Learning Journal

Reflecting on the HW1 assignment, I realize that, with the knowledge I have now, I would have conducted research before diving in. This proactive approach proved invaluable, and I plan to adopt it for all future projects. My first victory was configuring the debugger so I could step through my code and inspect variables line by line. That hands-on insight was a major leap in sharpening my programming skills and made tackling homework far more manageable. My second victory was actually finishing the assignments, even when I started them at the last minute. By drawing on what I’ve learned both in class and from my own experience, I’ve been able to deliver on time, and seeing that success has really boosted my confidence. I’ve become much more proficient with Room for local data persistence, I can define @Entity classes, create DAOs, and configure a RoomDatabase so that storing and querying structured data is both clean and type-safe. I’ve also mastered view binding, which allows me to ac...

For week 5 we went over our Markov assignment with our team mates... For this Markov assignment, I worked with two classmates: Kha Ai and Josh. We met up via discord to review our code, discuss challenges, and share ideas on implementing the assignment's requirements.  I began by writing the initial code stubs. Instead of spending too much time on planning with extensive notes or diagrams, I trusted that the assignment prompt provided enough structure. By creating these stubs early, I established placeholders for all the required methods. Kha Ai followed the Markov Intro Video and assignment prompt closely. She mentioned that, similar to me, she did not plan extensively on paper before coding. Instead, she jumped directly into writing code by creating stubs first, following the prompt’s order to define their methods, and running their test to confirm functionality. Much like my teammates, I did not spend a significant amount of time planning on paper. I believe the clarity of the a...

1. I worked with Joshua, Kha Ai, and Vladimir on discord to discuss our LDPM project. 2. For the first lab my strategy was to write out all the stubs and worked through each function/method one by one making sure they pass the test. Some methods that calls on other methods required ensuring those methods were written out correctly first so I made sure those passed before doing any methods that calls other methods. 3. Vlads strategy was to start implementing the methods in the order that they were listed on prompt document. I did not necessarily plan it out, just followed the order. I did not attempt to run the tests until I had a rough draft of how I thought each method should be implemented. Then I began debugging to see what I needed to fix. 4. After working on the assignment, I think learning how to debug properly better next time would make this a lot more easier regarding break points and seeing what the values are as the program runs. 5. My code kind of followed the Java Styl...

For this week, I've worked with Vlad, Josh, and Kha. We exchanged our code files and reviewed each other's work through discord and shared. For the most part a lot of our code seems to be pretty similar. The major differences is the methods/functions we use from other libraries. Some of the feedback I've received from my peers was regarding how I've implemented my methods/functions closely to the prompt. As far as variable names, we've all followed the UML format so it was pretty clear. I went over some of my team mates code and compared them with mine and noticed the difference in some of the coding logic. Some were a bit more stream lined than others. One major trend i've noticed when reviewing the code of my peers was some of them weren't too sure on how to proceed certain methods/functions so we went over the prompt and used the instruction as pseudocode to help them properly implement certain methods. One of the hardest part of the code for me was tryin...