Week 6 - Session 1 - Getting Unstuck
blog image source |
Read the error message; error messages are used when user intervention is required, to indicate that the desired operation has failed, or to relay important warnings. Remember, an error message is a good thing since you find it during development and not on a live release by a user.
Challenge your assumption; what do you think is going on? If you make too many assumptions, you are bound to build an application where the requirements are off, or the user experience is bad. Always take the time to review the requirements and make sure you fully understand them.
Create and test the hypothesis; a hypothesis is a prediction you create prior to running an experiment. It states clearly what is being changed, what you believe the outcome will be, and why you think that’s the case. Running the experiment will either prove or disprove your hypothesis. Use development tools like console log, command line, node etc…
Tighten the loop; Does it work? Another error message? More assumption.
Don’t get stuck - https://codewithoutrules.com/2016/12/08/how-not-to-get-stuck/
What I tell all new programmers - https://josephg.com/blog/what-i-tell-all-new-programmers/
Rubber duck debugging - https://en.wikipedia.org/wiki/Rubber_duck_debugging