Daily Problem Solving Practice
Throughout the rest of this inning, you’ll have time carved out in most days to practice the skills we learned today. For each challenge, you’ll spend 15 minutes planning and pseudocoding. You will not actually solve or code anything. You will use the following prompts to flex and strengthen your problem solving skills, not your coding knowledge or syntax.
Focus on running through steps 1-5 for each prompt.
Problem Solving Process
- Restate the goal in your own words. Take note of EXACTLY what the final output(s) should be.
- Consider the data that you’re working with. What data types are you working with? Are there any parameters/arguments? What data in particular do you need access to?
- Ask clarifying questions that you have about the goal and/or the data. Is there anything that still unclear? It is critical that you have a complete and accurate idea of the goal and data before you move on.
- Pseudocode the steps needed to get to the goal. Write out your plan, with specific steps, in plain English. What will you need to do first? Then what?… Note: You may only be able to pseudocode out the first couple of steps - that’s okay! Plan out as much as possible now.
- Research what you don’t know. Is there something you’ve noted in your pseudocode that you don’t know how to do? Take note of that and google.
- Start coding by referencing the pseudocode you’ve written.
- Stuck? Go back to step 4 and repeat steps 4-6 until you’ve reached your goal.
- Refactor your code, if necessary. You should not be worried about writing the “best” code possible while solving the problem. Get it to work, then you can work on improving the code.
Day 1
Do NOT write any code! Practice planning out how you would approach the prompt. Your planning process should include thorough pseudocode.
Day 2
Do NOT write any code! Practice planning out how you would approach the prompt. Your planning process should include thorough pseudocode.
Day 3
Do NOT write any code! Practice planning out how you would approach your code to pass the tests listed in the tests.js file. Your planning process should include thorough pseudocode.
Day 4
Do NOT write any code! Practice planning out how you would approach the user stories listed in the JS file. Your planning process should include thorough pseudocode.
Day 5
Do NOT write any code! Practice planning out how you would approach the prompt. Your planning process should include thorough pseudocode.
Day 6
Do NOT write any code! Practice planning out how you would approach your code to pass the tests listed in the tests.js file. Your planning process should include thorough pseudocode.
Day 7
Do NOT write any code! Practice planning out how you would approach the user stories listed in the JS file. Your planning process should include thorough pseudocode.
Day 8
Credit Card Mask (Code Challenge)
Do NOT write any code! Practice planning out how you would approach the prompt. Your planning process should include thorough pseudocode.
Day 9
Do NOT write any code! Practice planning out how you would approach your code to pass the tests listed in the tests.js file. Your planning process should include thorough pseudocode.
Day 10
Guess That Number (FE Feature)
Do NOT write any code! Practice planning out how you would approach the user stories listed in the JS file. Your planning process should include thorough pseudocode.
