My CS Degree Journey

First Steps in CST338: Java, Git, and Coding Challenges This week, we started a new class: CST 338: Software Design. It is exciting, and I like it so far. In this class, we are using the Java programming language along with IDEs like IntelliJ and Android Studio. These tools are new to me, but I haven't experienced any major difficulties yet - Java feels quite similar to other languages I've worked with, and the IDEs are intuitive once you get used to them. Dr. C. also introduced us to version control using Git and GitHub through the integrated terminal. He showed us how to use basic Git commands such as git status, git add ., git commit -m "message", git checkout -b branchname, and git merge. We also learned how to set up .gitignore files using a plugin and how Git tracks file changes locally until they are pushed to GitHub. The lectures provided helpful context on using Gradle as a build system and how we can structure our Java projects cleanly with folders for main,...

Part 1: Review Other Teams' Final Video Projects The first video I will review is " Digital Immortality" by the group Fantastic 4.  The video fully meets and exceeds the evaluation criteria. The topic is timely, deeply relevant, and impressively well-researched, with strong supporting evidence throughout. The presentation is clear, logically structured, and engaging from start to finish. The narration is professional, and the use of visuals and sound effectively enhances the message. The pacing and tone are balanced, holding attention without overwhelming the viewer. The ethical considerations and legal implications are thoughtfully explored, making the content suitable for both general and technical audiences. Team collaboration is evident in the cohesive production quality and depth of information. My only concern is that the footage and visuals appear sourced from the web, which may raise questions about proper licensing or usage rights. The next video is " Drones...

 Part 1: Final Research Video Project Planning Collaborating on our Final Research Video Project was a dynamic and mostly smooth experience, thanks to the tools and strategies we used to stay connected and organized. Most of our collaboration happened over Zoom, where we held regular meetings to brainstorm ideas, assign roles, and check progress. These live sessions were essential for real-time feedback and coordination. Outside of Zoom, we relied heavily on Discord for daily communication. It was a central hub where we could casually share updates, exchange ideas, and upload draft files or reference materials. For document sharing and group editing, Google Drive and its suite of tools (docs, slides, and sheets) were incredibly useful. Having the ability to co-edit files in real-time kept everyone on the same page and eliminated version control issues. We aimed for consistency in the video production aspect by using the same virtual background across all our individual recordings. ...

Part 1: Help Your Teammates to Develop Capstone Ideas Our team met last Friday during our regular team meeting to discuss possible capstone ideas. One thing that stood out during our conversation was how diverse our individual skill sets and career goals are. I am primarily focused on software development - especially full-stack applications with database integration - while my teammates are leaning more toward cybersecurity. This difference in focus has shaped the direction of our initial brainstorming. While Jose mentioned ideas related to cybersecurity applications, such as tools for detecting threats or simulating phishing attacks, my interests lie in designing and building scalable applications with a strong backend. Maria hasn't finalized her ideas yet, but her interests seem to align closely with Jose's. Despite these differences, I see a great opportunity for collaboration. I suggested that if we decide to pursue the capstone as a team, we could create a project that br...

Introduction For this assignment, I interviewed Richard Madrid, a Senior Software Engineer at CONNECT by American Family. I chose to speak with Richard because I eventually replaced him in my current position when he transitioned to his new role at CONNECT. I found it valuable to learn from someone who previously held the same responsibilities and has since advanced into a senior role in a larger organization. His journey and experience offer insight into both where I am now and where I might go professionally. Summary of Key Takeaways Richard shared that his path into software engineering was not traditional. He graduated with a degree in Computer Engineering, which focused more on hardware, circuits, and mathematical concepts than on software development. After experiencing a personal loss, he decided to remain in the Central Valley rather than relocate, and he began his career as a Database Developer. He taught himself SQL and programming fundamentals on the side, eventually landing...

 Part One: Support and Comment on Teammates' Goals My first comment is here and the second one is here . Part Two: Possible Capstone Ideas Three possible capstone projects I might pursue include a web-based incident reporting system, a performance tracking dashboard, and a scheduled report delivery platform. The incident reporting system would allow users to submit, review, and manage incident reports through a secure web interface. The performance tracking dashboard would present key employee or departmental metrics using interactive charts and tables, helping managers analyze trends over time. The report delivery platform would let users configure recurring report schedules and automatically generate and send formatted reports via email. Each project would be built using modern web technologies and structured to support real-time data interaction, role-based access, and reporting capabilities. These ideas would allow for the creation of functional, scalable systems that address r...