Getting Unstuck

"Every great developer you know got there by solving problems they were unqualified to solve until they actually did it." - Patrick McKenzie

"Failure is instructive. The person who really thinks learns quite as much from his failures as from his successes." - John Dewey (Read: Failure ~ Bug)

"One of the best programming skills you can have is knowing when to walk away for awhile." - Oscar Godson

1. Context

1. Getting It Done vs. Learning
2. Solution Finding vs. Problem Solving
3. Performance Zone vs. Learning Zone
4. Energy Direction: External (Product/Result) vs. Internal (Self)
5. Stack Overflow Syndrome - Copy-and-paste programming
6. Automation - Working Memory - Cognitive Load
7. Growth Mindset

2. Avoiding Plagiarism

3. What not to do?

1. Random-walk programming

2. Not taking breaks

3. Frustration and/or rage

4. What to do?

1. Embrace the Challenge

2. Ask Yourself 3 Questions:

   1. What is your problem? Describe it with as much details as you can.
   2. What have you tried so far?
   3. In which problem solving phase do you think you are? Are your actions fit to that phase?

3. Use External Resources

   • Stack Overflow - Mindfully
     • Rule of Thumb #1: The purple link
     • Rule of Thumb #2: Is it part of my core tasks?

4. Ask Others - Use Minimal, Complete, and Verifiable Example

5. Take a break and have a walk, or try tomorrow after a good sleep