Week 6 - My CSUMB Journey

Develop Capstone Ideas:

Our team met on Zoom this week to brainstorm possible capstone ideas and help each other shape early concepts. It was a relaxed but productive conversation where everyone shared what kind of problems they would like to solve and what skills they hope to use. The idea that stood out to me the most was creating a community needs matching app that connects people seeking help like food assistance, tutoring, or transportation, with local organizations that can offer support. I really liked this concept because it feels meaningful, realistic, and something that could genuinely help others while still being achievable within the capstone timeline.

Another idea that caught my attention was a nonprofit directory that allows users to search for organizations by cause or location, learn about their missions, and easily find ways to get involved through volunteering or donations. It could have filters for categories like education, environment, or health, and include verified information so users know they can trust what they find. I can see how this type of project could grow over time but still start small with a simple, working prototype.

Talking through these ideas as a team helped clarify what makes a capstone project successful. Something that is practical, purposeful, and possible within the time we have. It also reminded me how valuable collaboration is, even at the idea stage. Everyone brought a different perspective, and by the end of the meeting, we had a stronger sense of direction and a few clear possibilities worth developing further.

Summary of week 6:

This week felt like a turning point from gathering resources to putting myself out there. I wrote my first internship-ready resume and I pushed myself to speak in a completed-bachelor's voice. That shift made a big difference: instead of “I’m learning,” I framed what I can deliver. Instead of listing tools, I told the story of how I approach problems and explain results. By the final draft, the tone felt right; clear, confident, and genuinely mine.

I watched a mock technical interview and Gayle Laakmann McDowell’s talk for the first time. The biggest takeaways were more about habits than algorithms: slow down at the start, ask clarifying questions, think out loud, and test with a tiny example before committing to code. Hearing strong candidates narrate their reasoning made the process feel less mysterious and more coachable. I’m setting a simple routine; two short practice blocks a week, so these habits become automatic.

I also built the shell of my ILP portfolio website. The goal was momentum, not perfection: a clean home page with my name, a short bio, program outcomes, and goals, plus a tab for each course with space for the official description and a final project. Getting the structure in place took the pressure off; now I can drop in artifacts and quick reflections as I go instead of cramming everything at the end. 

To get ready for the next class (Software Design with Java), I previewed the syllabus and starter materials and sketched a gentle ramp-up: get comfortable with classes, methods, objects, and the everyday collections I’ll use most. My plan is to keep the practice small and steady, daily syntax reps and a couple of mini exercises once the course starts, so I build confidence without burning out.

Overall, I am ending the week with polished materials I can stand behind and a portfolio scaffold that will grow with my coursework. For now, I am letting the work breathe and taking a moment to appreciate the progress.