AP CSP Retrospective: Learning, Building, and Growing Together

October 12, 2026

Biggest takeaway: CSP has taught me that building software isn’t just about writing code. It’s also about communicating ideas, listening to others, testing assumptions, and improving through feedback.

At a glance

1. My CSP journey so far

From setup to building

Getting my tools and portfolio ready was an important first step. It taught me that even before writing code, software development requires organization, patience, and troubleshooting. I am more comfortable navigating my project, keeping work documented, and treating my portfolio as a record of my progress.

As I worked through programming topics such as variables, lists, Boolean expressions, conditionals, loops, procedures, and abstraction, I began to connect individual lessons to the bigger picture of creating functional programs. Sass activities also helped me think about how a user interacts with an application, not just how the code works behind the scenes.

Learning through teaching

Preparing and teaching the Sass inputs lesson was different from completing an assignment myself. I had to consider the perspective of someone seeing the material for the first time, organize the concepts, and make my explanation understandable. It reminded me that knowing something and teaching it effectively are different skills. I want to get better at including clear examples, checking for understanding, and adapting explanations to the audience.

Learning through PVO ideation

Our PVO ideation work showed me that developing software starts with defining a meaningful problem. Rather than immediately choosing features or writing code, I am learning to consider who will use the product, what they need, and what a realistic first version should do. This has helped me become more open to revising ideas instead of treating the first idea as the best one.

2. How I have grown

As a person

The most important growth has been in my mindset. I am becoming more patient when things do not work immediately and more willing to learn through trial, feedback, and revision. Teaching and group discussions have also helped me practice expressing ideas clearly and accepting that someone else may see a better approach.

I am learning to be more adaptable, accountable, and reflective. Instead of treating a mistake as the end of a task, I want to understand why it happened and what I can change the next time. I also want to become more confident in contributing ideas while remaining open to criticism and different perspectives.

As a collaborator

I am learning that good collaboration is not just dividing up tasks. It also means making sure everyone understands the goal, listening actively, communicating progress, and following through. Working on PVO and preparing a lesson have reminded me to consider other people’s viewpoints rather than only my own.

My next step is to be more proactive: clarify tasks early, ask for feedback before the last minute, and document decisions so teammates can build on one another’s work.

How our team has grown

Our team has been moving from individual contributions toward a shared process. Through lessons, discussion, and ideation, we are building a stronger understanding of one another’s strengths and how different perspectives contribute to an idea. Explaining concepts to each other and discussing PVO have given us opportunities to practice communication and shared decision-making.

We still have room to improve. We can be more consistent about dividing responsibilities, making our plans visible, and checking in on progress. I think a stronger team is not one that agrees on everything, but one that can respectfully discuss differences and turn them into a better result.

3. Growing with AI and the software development life cycle

Using AI more responsibly

My goal is to use AI as a learning and development assistant, not a replacement for my own reasoning. It can help me brainstorm, explain unfamiliar concepts, compare possible approaches, and troubleshoot code. But I am realizing the importance of questioning its output: Does the explanation make sense? Can I verify the code? Can I explain the solution on my own?

I want to improve the quality of my questions to AI and spend more time testing its suggestions. That way, using AI helps build my understanding rather than hide gaps in it.

Seeing the full development process

The software development life cycle (SDLC) now feels less abstract because I can connect its stages to what we have done:

I am starting to see that these stages are iterative. Testing may reveal a design problem, feedback may change a requirement, and a better idea may emerge after a first version.

4. College Board MCQ reflection

My results

The Big Idea breakdown below is calculated from my question-level College Board report.

What I am doing well

My strongest result was in Impact of Computing. I feel most confident reasoning about how computing affects people, including privacy, security, ethics, and the broader use of technology. I also showed solid overall understanding in Data and Algorithms & Programming, which suggests that the programming lessons and practice have built a useful foundation.

Where I want to improve

The results show that I need to strengthen my development and testing habits. I want to become more systematic about checking whether a solution works in different situations, instead of only deciding whether it looks correct.

I also want to improve at tracing unfamiliar algorithms step by step, especially when multiple conditions or iterations interact. In data-related questions, I can work on interpreting what information actually supports a conclusion. Finally, I want to review networking concepts and become more consistent about pacing myself through longer assessments.

These percentages are useful indicators, but the topics had different numbers of questions, so one practice assessment is not a complete measure of my understanding.

5. What comes next

My priorities for the next stage of CSP are simple:

1. Practice testing and debugging: use normal and edge cases to check my reasoning.
2. Slow down on complex algorithms: trace program state instead of guessing.
3. Collaborate more intentionally: communicate ownership, progress, and feedback.
4. Verify AI-generated suggestions: test results and explain solutions independently.
5. Keep iterating: use the SDLC to improve PVO ideas and future portfolio work.

Final reflection

Looking back, I see growth in more than my technical knowledge. I have become more conscious of how I learn, how I communicate, and how I contribute to a team. My team is learning how to combine ideas into a shared direction, and I am learning how to balance independent thinking with collaboration and AI assistance.

The MCQ results are encouraging, but more importantly, they give me a direction for improvement. Going forward, I want to focus not just on getting an answer or a program to work, but on understanding why it works, how to make it reliable, and how to build it with others.