CSU MB

Looking back at HW1 now, my approach would be very different compared to the start of the semester. At that time, I was mostly focused on just getting the code to compile and produce output. Now, I think much more intentionally about structure, readability, and design choices before I even start writing code. One major victory is how much more comfortable I am with object-oriented programming concepts. Early on, ideas like classes, constructors, and encapsulation felt mechanical. Now, I understand why they matter and how they work together. I am confident using access modifiers to protect data and designing classes so that responsibilities are clearly separated. Another big win is my understanding of inheritance and polymorphism. I am now comfortable extending classes, overriding methods, and knowing which method will be called at runtime. This is something that was very confusing at the beginning of the semester but now feels natural when reading or writing code. Finally, my overal...

📘 Week 5 Learning Journal Markov Assignment This week’s focus was the Markov assignment, and it pushed me to think more deeply about how to structure code based strictly on specifications and UML diagrams. At first, the project felt a little overwhelming, but breaking it down step-by-step helped me understand how the logic was supposed to work. 👥 Who I Worked With This week I collaborated with Lee and Brian. We all had slightly different approaches, so talking through our strategies really helped me see where my design was solid and where it needed more clarity. 🧭 My Strategy for Solving the Assignment My approach started with translating the specifications and UML diagrams directly into code. I began by: Declaring all the required variables and method signatures first Leaving each method blank at the beginning Using Android Studio’s shortcut tools to automatically generate getters and setters Then filling in each method by following the logic described in the specs Once ...

What was your group’s strategy for solving the assignment? My group members each had their own approach. Some started coding right away and refined as they tested. Others planned more like I did. Overall, they seemed to rely heavily on incremental testing and verifying that smaller parts worked before moving forward. How would you change your strategy after working with them? I would adopt a more test-as-you-go workflow. Seeing my classmates test frequently made me realize I should have implemented and verified smaller pieces first. With the IDE problems I had, testing early could have helped me realize my setup was failing before the deadline. According to your classmates, how well does your code follow the Google Java Style Guide? Since my code did not compile correctly, my classmates couldn’t fully evaluate it. However, they mentioned that if I continue practicing structured formatting consistent indentation, clear naming, and method organization it will align better with the Goo...

For Project 1, I worked with a couple classmates while I built out my LDPM (Legally Distinct Pocket Monsters) program. We mainly compared structures, talked through our approaches, and made sure everyone’s classes worked cleanly together. Before jumping into coding, I took a minute to look over Morgan’s Hangman program from earlier coursework. Not to copy code just to get inspiration on how to clean up my structure, keep things organized, and upgrade the way I handled methods and class responsibilities. It helped me rethink how I designed the base class and how subclasses should act differently but still fit the same mold. My process was simple: Understand what the base Monster needed Build that first Add each monster subclass with its own small twist Test attacks/defense as I went Keep everything clean and readable My classmates had slightly different approaches one coded right away, one mapped things out and talking through our styles made the whole thing smoother. They sai...

During week 1, I focused on designing and building the Hangman game in Java. This was my first chance to really dust off my object-oriented programming habits and apply encapsulation, creating separate classes and methods that worked together cleanly. I built small reusable methods for guessing letters, tracking hints, and managing the word array, which helped me see how organized code makes debugging far easier. Setting up branches in GitHub and merging changes through IntelliJ was another learning curve but seeing my commits stack up and actually run without breaking anything was rewarding. What challenged me most was managing so many moving pieces at once: creating logical method groupings, documenting them with Javadoc, and writing code that stayed readable. I also learned to appreciate version control having a branch dedicated to experimentation meant I could try risky refactors without fear. Converting everything into a final PDF for submission tested my workflow discipline. Over...

Final Research Video Project Reflection For our final research video project, my team kicked things off by organizing all our software info and ideas in shared forms. That gave us a clear starting point. Once everything was pulled together, we moved into production with Adobe Premiere Pro. I was in charge of creating the slides, layering in visuals and GIFs, and syncing up the audio with the visuals so things flowed. Overall the process went pretty well. The only real hiccup was toward the end when Brian wasn’t able to contribute, so we had to pick up the slack last-minute. It did get a little stressful, but we pulled through and got it submitted on time. Personally, I ended up uploading right near the deadline, which taught me a valuable lesson: next time, I’ll build in internal deadlines and check-in points so we’re not scrambling the final day. Part Two – Weekly Reflections and Learning This week turned out to be pretty meaningful for me. The first video, Luis von Ahn’s TED Talk...

Weekly Learning Journal CST — October 14, 2025 Part 1: Helping My Teammates Develop Capstone Ideas This week our team met to brainstorm capstone directions. We first kicked around ideas in quantum computing —especially how it could reshape security and processing at scale. It was exciting, but we decided it might be too broad for our scope and timeline. We then explored Neuralink , focusing on how neural interfaces could work with auditory/ear-related data. That generated a lot of interest, but as we compared options (and saw what other groups were selecting), we pivoted to something more grounded and immediately impactful: DeepFake detection . Our working direction is to analyze video authenticity identifying whether a clip is a DeepFake or not. The topic hits a timely intersection of AI, ethics, and security, and it gives us a clear technical problem to prototype and measur...

Industry Expert Interview – Exploring Career Paths and Industry Trends For this assignment I interviewed John Silva, a software engineer who has worked at several well-known companies. I chose John because he has moved around the industry, tried different roles, and built a lot of experience along the way. He’s also been something of a mentor for me we’ve bounced ideas off each other as developers, and I’ve looked to him for advice as I’ve been shaping my own career path after moving to California. John started by sharing how his career developed. He didn’t follow one set path but moved through different companies and projects, each time picking up new skills. He explained that while it’s important to know the technical side, being adaptable has been the real key. In tech, new frameworks and tools come out all the time, and he said you’ll drive yourself crazy trying to master everything. Instead, he focuses on learning the fundamentals, problem solving, and keeping up the ability t...

My Educational Goal in the CS Program My goal is to gain a deeper understanding of the software lifecycle so I can confidently plan, design, implement, and maintain projects from start to finish. I also want to strengthen my knowledge of databases and algorithms, so that I can not only understand the theory but also apply it effectively in real situations. Along the way, I will develop projects that showcase both lifecycle principles and solid use of databases and algorithms, giving me tangible work to highlight my skills. My Career Goals My career goal is to transition into a software development or DevOps role where I can apply my knowledge of the software lifecycle, databases, and algorithms to build efficient, reliable systems. I want to earn certifications in cloud computing (AWS or Azure) and use those skills to design and maintain scalable solutions that make a real impact in an organization. Within the next few years, I envision myself working as a developer or DevOps engi...

This week I tried a new study tip: avoiding food at least 30 minutes before studying. I noticed that when I followed this, I felt more awake and alert during my sessions. Normally, eating right before made me sluggish and less focused, but giving my body time to settle meant I could concentrate better and retain more information. It was a simple adjustment, but it improved the quality of my studying and made my time more productive. From this week’s ethics lessons, I focused on three main points: moral reasoning and decision-making, responsibility and accountability, and integrity and consistency. In my work for local government, these show up daily whether I’m weighing how to balance efficiency with protecting sensitive data, taking accountability when a system impacts staff or the public, or maintaining consistency in how I apply rules and communicate with coworkers. These frameworks remind me that even small choices in my role can build trust and make a difference for the communit...

 What are the top 3 items that you are good at, and what are the top three areas you feel you are weak in?   Weakness  When I reflect on my study skills, I can see areas where I am developing strengths as well as places I still need improvement. One of my current weaknesses is my study space. While I know it should be a quiet and comfortable place, I am still transitioning from my house setup and often find myself distracted, which makes it harder to stay focused.  Another weakness is my note-taking. Although I do take lecture notes, I realize they could be improved. For example, during a group project, I created some HTML and JavaScript for our website, but I should have taken better notes earlier in the process to manage my time more effectively.  A third weakness is staying consistent with organizing my study sessions; while I gather materials before writing, sometimes I delay starting, which slows down my momentum. Strength  Weekly Ac...