Arch's reflection:
(+) User Input - Each FRQ has User Input, as well as explanations for 99% of what the user should input.
(+) Wiki Page - My analysis and reflections on the FRQs were detailed and highlighted key learning points and various bugs encountered.
(+) Easy to execute runtime - Menu is easy to navigate and easy to run each FRQ, all FRQs were in the same place.
(-) Program has little to no error handling. Data type boolean input has error handling, String can handle whatever, but integers and doubles give errors if provided with a String or other misc. characters. A way I could fix this is by using try/catch statements in order to prevent the user from mis-inputs.
(-) No testers. Entire program must be run in order to run each FRQ. There isn't a good way to run each FRQ individually.
Nolan's grading:
To be graded by @nolanplatt
9.85/10
-.15->
(-) Program has little to no error handling. Booleans do, but integers and doubles don't. A way he could fix this is by using try/catch statements in order to prevent the user from mis-inputs.
(-) No testers. Entire program must be run in order to run each FRQ. There isn't a good way to run each FRQ individually.
Direct link to Arch's FRQs - replit.com
GitHub Wiki that guides user through FRQ experience Easy to execute runtime - All FRQs in one Replit embedded on website Replit Revision History 1 minute video
Arch's reflection: (+) User Input - Each FRQ has User Input, as well as explanations for 99% of what the user should input. (+) Wiki Page - My analysis and reflections on the FRQs were detailed and highlighted key learning points and various bugs encountered. (+) Easy to execute runtime - Menu is easy to navigate and easy to run each FRQ, all FRQs were in the same place. (-) Program has little to no error handling. Data type boolean input has error handling, String can handle whatever, but integers and doubles give errors if provided with a String or other misc. characters. A way I could fix this is by using try/catch statements in order to prevent the user from mis-inputs. (-) No testers. Entire program must be run in order to run each FRQ. There isn't a good way to run each FRQ individually.
Nolan's grading: To be graded by @nolanplatt
9.85/10 -.15-> (-) Program has little to no error handling. Booleans do, but integers and doubles don't. A way he could fix this is by using try/catch statements in order to prevent the user from mis-inputs. (-) No testers. Entire program must be run in order to run each FRQ. There isn't a good way to run each FRQ individually.