Drew Reed, Period 1 - Trimester 2 Final Presentation Supplement

Content for Quick Review

1. Why was I a good grader on Monday? What will make me a good team member in Tri 3? Is there a relationship between being a good grader and being a good team member?

This was my review on Alex and this was Mr. Mort's feedback.

I'm glad my feedback was a good example. I think that the more direct and perhaps unprofessional wording was a result of having previously worked with Alex. I know how he likes to collaborate and he's very open to taking feedback on his work.

What will make me a good team member in Tri 3?

Scrum Board was used actively and fully. I think I will do a good job keeping organized.
I helped my group work in pull requests.
I've grown extremely comfortable with devops in the most recent trimester, so I'll be able to pull weight in that area next tri.
I have a solid understanding of Java and our Spring backend, which I showed well in my PBL reflection.
My analytics

I think the relationship between being a good grader and a good team member goes the other way around: I think being a strong contributor and team member made it easier for me to give good feedback, because I was constantly doing so with my group members. It also gave me a diverse range of experience within the scope of PBL, which I applied to grading.

2. What did I learn from my grader? What will make me successful on AP topics? On PBL work? Is there a relationship between learning from others comments on my work and being good at PBL?

The most frequent takeaways I got related to my work was moments where my code did not completely align with CB standards, which I hadn't checked directly in much detail. They were mostly small mistakes like declaring class variables public (which is weird, I never do that).

I revised this problem as a result of our review. Details provided in blog. I think a similar degree of interest in and understanding of feedback will help me improve on my work in a larger PBL situation, as I look forward to changing the dashboard frontend design to be easier to interact with and vertically-oriented, for example.

We spent a lot of our time with FRQs discussing different ways that we handled problems. I offered my understanding of the AP Java Quick Resource, which limits our access to certain libraries and class methods that would otherwise be very helpful.

Again, there's definitely a relationship between learning from comments and being good at PBL, since teacher and peer feedback acts as a hugely influential factor in our work.

3. Anything you want to talk about? Recap of Tri 2. Future project excitement.

Our group is really excited about Nighthawk Resources and intends to bring it to a fully complete state.

Look, builder pattern:

Trimester 2, for me, was...

...the first time I truly, fully understood deployment and devops information.
...the first time I facilitated a team environment based around pull requests and a truly active, organized Scrum Board.
...a huge step forward for me in terms of understanding our Spring backend and how it can be utilized.
...a continuation of my excitement to make something truly useful and not game-y.
...finally, a transition to more frequent commits toward meaningful ends, especially due to pull request structure.

Trimester 2, for my group, was...

...the most organized group structure we had created/worked within.
...a period of solid motivation for the majority of our time because our goals were clearly outlined.
...a time when even big problems had clear solutions because discussions were frequent and overall project understanding was shared.
...successful, even among people who don't succeed as often in individual measures.

drewreed2005 / dre2.0

Drew Reed, Period 1 - Trimester 2 Final Presentation Supplement #6

Content for Quick Review