Yajat FRQ Showing 2 (Reflection and Crossover Feedback)

[yajatyadav]

FRQ

9/9 FRQs completed, 5 have input/output (U2Q1, U3Q1, U3Q2, U4Q1, U4Q2, U5Q1, U5Q2, U6Q1, U6Q2)

Analysis and Reflection (Partner- Harry Li):

Overall- I completed 9/9 of the FRQs, 5 have input/output. While I used a Repl and embedded it on my About Page, Harry implemented his FRQs to receive inputs/ display outputs directly onto his PBL.

FRQs compared: Unit 6 Q1, Unit 4 Q1, Unit 6 Q2

Unit 6 Question 1:

• Harry utilized HTML to have users input values using a form. I used the Repl command line for a similar result.
• Harry had a predefined list of words that the code would check for ending in -ing. However, I made it so that users could enter words separated by commas, and then I would perform String operations on the input to split up the response (using the comma) and create a list of words
• For the for loop, me and Harry had similar implementations. We both used enhanced for loops to check each String in the ArrayList, as well as the substring function to check the word's end.
• However, I had an extra feature: I used Math.abs to ensure that an error isn't thrown if the word input is smaller than 3 characters (since "ing" is 3 long) and instead the function simply returns false

Unit 4 Question 1:

• Me and Harry had similar implementations for this FRQ
• We both had input that asked for a String of letters, and an output that returned two values: most common letter, and its length
• Harry had this FRQ in his PBL, while I used Repl
• Our algorithms were also similar. We tracked the longest occuring string using a "current" variable, and if the current variable exceeded the "longest" variable at any point, longest was overwritten. This process was repeated while iterating through the entire String, resulting in the longest streak of consecutive letters being returned
• While I used the substring() method with the arguments x and x+1, Harry simply used the charAt() method. While I had to provide a starting and ending point, using charAt() allowed Harry to simply obtain the value from the String via a single index.

Unit 6 Question 2:

• While I had the user input the list of items sold as a comma separated list in the terminal, Harry used multiple text boxes on his PBL. While Harry's method is more aesthetic and easy to input, it limited the user to a list of size 10 while in my case, the list of items sold could be as long as needed.
• Me and Harry both had two prompts, one asking for the fixed wage and another asking for the wage per item
• In addition to returning all the wages, Harry also printed out the Bonus Threshold. This is a nice addition that I can implement too because having the bonus threshold also printed would allow the user to quickly tell which salaries were high enough
• Me and Harry had different approaches to calculating the bonus threshold: Harry had a for loop that would iterate through the list and check each value and update the min and max variables accordingly. I sorted the entire list first, and then retrieved the first value for the min and the last for the max
• for the computeWages function, me and Harry had a similar approach: a for loop to set the value at each index and if the condition (more than bonus threshold) is met, to multiply the wage by 1.1
• However, while Harry multiplied the wages high enough by 1.1, I instead used a variable. This would allow the user to change the bonus rate to any value other than 10% if they wanted to do so.

Summary Reflection : Overall, I think that I did a good job effectively constructing algorithms to accomplish a certain task in all of my FRQs. I also had easy-to-follow user inputs and outputs. I also gave the user more freedom than Harry's FRQs, such as inputting a list of any size, and having the option to change variables like the bonus rate. An area I could improve upon is the presentation. I used a Repl menu for my FRQs, and it would instead be more user-friendly and aesthetic to integrate my FRQs directly into my PBL and use Java and HTML to have features such as forms for user input, a submit button, tables to display final results, etc.

Links: All FRQs Wiki with Key Learnings for each FRQ Crossover Grading of Harry (link to issue) Github source of FRQs About Page w/ embedded Repl

[wiz124]

Score 10/10

9/9 FRQs completed All nine FRQs can be found in one replit project.

5 have input/output on the menu, I checked FRQ3 and 6 which both are running correctly with user inputs.

There is an FRQ wiki page with the code for each completed FRQ. Showing the tangibles is neat. It is solid evidence that you did them in which your bullet points helped to clarify the purpose behind your code. One thing I noticed is that you should add deeper reflections for each FRQ. Some of your bullet points don't make it clear that you learned something.

The Github of source for every FRQ can be found under one link. Very convenient.

---

Grows: When I was prompted to enter an input on 6, I was confused at first as to what input to give which caused an error in replit when I entered a string. Maybe next time clarify on your frqs what kind of input you would want from the user or have your code be able to handle more types errors. Having FRQ 1 in there was kind of confusing as well. I tried to test the test the first frq but ended up spamming one. If you want to avoid user confusion, I would suggest you remove the FRQ1 from the menu. Another thing you could do is implement a wait because when the user is done inputting the values, the program gives no time for the user to see the results. It just goes straight back to the menu.

Glows: One thing I thought was cool was being able to embed Replit with your about page. I thought that it was very convenient thing to do since it saves the user some time. Your menu and inputs were easy to manage as well. It was great that you had your code be able to handle some common errors that might happen like choosing 7 when it has only 1,2,3,4,5,6.