reflections

reflection 1

To revise my work, I’m planning to go through my draft carefully and figure out what’s working and what’s not. I want to make sure my ideas actually make sense and that each paragraph connects to the one before it. Sometimes I feel like I jump around too much, so I’ll focus on keeping everything organized and making sure my main point stays clear from start to finish. I’ll also check my sentences to make them flow better and fix any grammar or word choice issues that might make my writing harder to follow. Another big part of revising is adding more support for my arguments. I know I can strengthen some points by bringing in more evidence or examples that I might have missed the first time.

For secondary sources, I think I need to look at more scholarly articles, books, or reliable websites related to my topic. These will help me back up what I’m saying and show that I’ve done solid research. I might also check out some newer articles if my topic is connected to current events, because that will make my work feel more relevant and up to date.

I’m writing for the JJK, and that really impacts how I revise. I’m giving them information they need, and at the same time, they’re giving me information I can use to improve my understanding. That means I have to be very clear and thorough, making sure the points I include are useful for them, while also paying attention to what I’m learning from their feedback. It changes how I think about my audience because it’s not just a grade or a general reader—I’m working with people who are directly connected to my topic, and that makes me want to make my work as accurate and helpful as possible.

Overall, my goal with these revisions is to make my paper clearer, stronger, and more useful for the JJK. By improving structure, adding better evidence, and keeping their needs in mind, I can turn my draft into a polished final piece that really shows my understanding and effort.

Reflection #2

For this project, I want my work to reach the next class of CODES scholars. My goal is for what we create and contribute now to serve as a guide and foundation for those who come after us. I do not want the next group of scholars to feel confused, overwhelmed, or lost when they begin. Instead, I want them to have clarity, direction, and confidence because of the groundwork we helped lay. If our work is thoughtful, organized, and intentional, it can make their transition smoother and more meaningful. The most relevant stakeholders in this project are JJK Fan and the team who originally designed and launched this initiative. They are the ones who developed the vision and structure for the project and invited us to contribute to it during our time in college. Because they created the framework, their expectations, guidance, and information shape the direction of our work. They provide the resources, background knowledge, and instructions that allow us to complete the project effectively and align it with its original purpose. Their role is important because they understand the broader goals of the CODES program. By clearly communicating what is needed, they help ensure that what we produce will truly benefit future scholars. At the same time, we also carry responsibility. As current participants, we understand what it feels like to be in this position, so our perspective should influence how we approach the project. Ultimately, this work is about collaboration between vision, guidance, and lived experience. If we approach it seriously and intentionally, our contribution can positively impact the next generation of CODES scholars.

reflection 3

For me, giving and receiving feedback is lowkey a growth test. When I give feedback, I genuinely want to help people level up, not tear them down. I’m big on encouragement, so I usually highlight what someone did well before I say what could be better. But if I’m being real, sometimes I soften it too much or don’t say everything I’m thinking because I don’t want to come off harsh. I’m learning that clear is kind. If I really care about someone’s growth, I have to be specific and honest, not vague. When I receive feedback, it depends on the day. Sometimes I take it well and see it as an opportunity to sharpen myself. Other times, especially if I already feel pressure or insecurity, it can hit my pride a little. But I’ve realized feedback isn’t an attack, it’s information. It reveals blind spots I can’t see on my own. I’m working on pausing before reacting, really listening, and asking questions so I fully understand what’s being said instead of getting defensive. I can improve by separating my identity from my performance. Just because something I did needs work doesn’t mean I’m not capable. Moving forward, I want to be more intentional: when I give feedback, I’ll be direct, specific, and solution focused. When I receive it, I’ll write it down, reflect on it, and actually apply it instead of just saying bet and forgetting. At the end of the day, feedback is sharpening. It’s uncomfortable sometimes, but it stretches me. And I know if I stay humble and teachable, I’ll keep growing not just in skill, but in character too.