Going Further With Project and Portfolio II at Full Sail University

This post covers my experience with Project and Portfolio II: Web Development at Full Sail University. If Project and Portfolio I was about learning how to approach a project with structure, this course was about actually building one. Not a guided exercise or a set of isolated assignments, but a real application built from scratch over four weeks using React, external APIs, CSS libraries, and MongoDB. The milestones were real, the pressure was real, and by the end, I had something I was genuinely proud of. Below is a breakdown of each week and what it meant for my development.

---

Week 1: Choosing an API and Building the First Prototype

My thoughts at the time

The first week set the tone for everything that followed. Selecting an API that aligned with the project I had in mind was harder than I expected. There are thousands of public APIs available, and narrowing it down to one that was both interesting and practical for a React application required more research and planning than I anticipated. Once I had settled on a direction, the prototype work began, and that process was its own challenge entirely.

Prototyping forced me to stop thinking in terms of individual features and start thinking about the full shape of the application. What pages would exist, how users would move through them, and what data the API would actually power. It was the first time in the program where the design and development decisions I made directly affected the scope of work waiting for me in the following weeks.

Retrospective insight

Looking back, this week taught me how important the planning phase is in real project work. A poorly chosen API or a vague prototype creates compounding problems in every week that follows. Taking the time to prototype carefully and think through the data flow before writing production code is a habit I carried forward into every professional project I have worked on since. The API selection process also introduced me to reading technical documentation critically, which turned out to be one of the most transferable skills of the entire course.

---

Week 2: Building the React Foundation and Learning to Debug With Intention

My thoughts at the time

Week two was heads-down development. The goal was to have the foundational structure of the React project in place by the end of the week, which meant building out the component architecture, wiring up navigation, and making sure the application had a working skeleton before adding more complex features. Milestone two being tied specifically to navigation made sense because routing is one of those things that is easy to retrofit badly and much cleaner when it is built in from the start.

The debugging exercise was the part of the week that surprised me the most. I went into it expecting a straightforward bug hunt and discovered how easy it is to convince yourself that you understand what your code is doing when you actually do not. The library tutorial assignment also helped me think more carefully about how to evaluate and communicate about tools, which was a different kind of thinking than just using them.

Retrospective insight

This week gave me a more honest relationship with my own code. Debugging is not glamorous, but the ability to identify the source of a problem quickly and fix it cleanly is one of the things that separates a functional developer from a frustrated one. The library tutorial also planted the idea that understanding something well enough to teach it is a different level of understanding than just knowing how to use it. That idea has shown up in how I approach documentation and knowledge sharing in professional environments.

---

Week 3: Connecting Everything and Adding the Database

My thoughts at the time

Week three was the most technically demanding week of the course. The milestone required a fully functional React application connected to the API I had chosen in week one, integrated with multiple CSS libraries, and backed by a MongoDB database for persistent data storage. Each of those pieces was manageable on its own. Making them work together smoothly was a different challenge entirely.

The MongoDB integration was where the database knowledge from my CTI3622 course became directly practical. I was not learning how to use MongoDB for the first time. I was applying it under deadline pressure to a project with real requirements. That distinction mattered. Having the foundational knowledge already in place meant I could focus on the integration rather than the fundamentals, which made a noticeable difference in my confidence and the quality of the result.

Retrospective insight

This week reinforced something that the program kept implying but rarely stated directly: courses build on each other, and the value of earlier material compounds over time. Understanding how to model data in MongoDB, how to fetch and transform API responses, and how to manage state in React all needed to function as a cohesive system rather than isolated skills. Week three was the first time I truly felt the payoff of that accumulated learning. It also confirmed for me that full stack development is not just about knowing both sides of the stack. It is about knowing how to orchestrate them together.

---

Week 4: The Final Polish and Presenting the Work

My thoughts at the time

Week four was about finishing well, which is harder than it sounds. There is a tendency near the end of a project to declare it done before it actually is, especially after a few weeks of intense building. The milestone structure pushed me past that instinct by requiring a polished, user-friendly application rather than just a functional one. The gap between those two descriptions is larger than it sounds when you are the one sitting in the gap.

The presentation showcase was a requirement I initially viewed as secondary to the actual development work. By the time I was putting it together, my perspective had shifted. Having to create a video that walked through the journey from prototype to finished product forced me to look back at the decisions I had made across four weeks and articulate why I made them. That kind of reflection surfaces things that just writing code never will.

Retrospective insight

The presentation component of this course has had lasting influence on how I approach the end of any project. Writing up decisions, documenting tradeoffs, and being able to explain the arc of a project from idea to execution are things that matter in every professional context I have encountered. Finishing strong, presenting clearly, and being able to defend your design choices confidently are skills the industry expects. This week gave me early practice with all three, and I was better prepared for professional work because of it.

---

Closing Thoughts

Project and Portfolio II was one of the most complete learning experiences in the program. It asked me to use everything I had learned up to that point, not in isolation, but all at once, with a deadline and a public showcase waiting at the end. React, MongoDB, APIs, debugging, documentation, presentation. Every piece had to work. The milestone structure kept the project moving forward at a pace that felt demanding but manageable, and the end result was something that genuinely reflected the growth I had made across the program. This course showed me what it feels like to build a real application, and that experience is something no amount of isolated assignments can fully replicate.

Credits and Collaboration

A huge thank you to Esther Allin for designing the blog banner art! If you're looking for a professional digital media specialist, Connect with her on LinkedIn!