Reading-Notes

code fellows 401

Read: 00 - Prep: Readings … Get Ready for 401

Reading

Solving Problems

Here’s a programmers guide to solving problems.

1. Read the problem completely twice.
2. Solve the problem manually with 3 sets of sample data.
3. Optimize the manual steps.
4. Write the manual steps as comments or pseudo-code.
5. Replace the comments or pseudo-code with real code.
6. Optimize the real code.

How to think like a programmer

“Everyone in this country should learn to program a computer, because it teaches you to think.” — Steve Jobs

1. Understand

• Know exactly what is being asked.
• You should be able to write, draw or explain a problem so that it makes sense to someone else
• Rubber duck method - when you explain the code to an in-animate object, like a rubber duck.

2. Plan

• Write down the steps in order to solve a problem.
• This gives your brain time to think and proccess the information.
• Write it down in comments if you want.

3. Divide

• Create sub-problems.
• Sub-problems do not rely on other sub-problems to be solved.
• Connect the dots when done.

4. Stuck?

• Debug: go through a problem step by step
• Reassass: look at the problem from a diffrent perspective
• Research: basically means to just Google it
• Caveat:

5 Whys

1. Assemble a Team
   • find people who are familiar with the specifics of a problem
2. Define the Problem
   • Create a problem statement
3. Ask the First “Why?”
   • Ask why the problem is occuring
4. Ask “Why?” Four More Times
   • Ask why the previous explanation occured
5. Know When to Stop
   • Find the root cause
6. Address the Root Cause(s)
   • Discuss counter measures
7. Monitor Your Measures
   • See how well your counter measure works