Problem SolvingThe key skill of problem solving involves pupils developing the skills and strategies that will help them to solve the problems they face in learning and in life. Problem solving includes the skills of identifying and understanding a problem, planning ways to solve a problem, monitoring progress in tackling a problem and reviewing solutions to problems. All subjects provide pupils with opportunities to respond to the challenge of problems and to plan, test, modify and review the progress needed to achieve particular outcomes.

DfES/QCA 1999

Two men went into a restaurant. They both ordered the same dish from the menu. After they tasted it, one of the men went outside the restaurant and shot himself. Why?

Logical problemsAlgorithm

Story problemRule-using problem

Decision makingTrouble-shooting

Diagnosis-solutionStrategic performance

Case analysisDesigns

Dilemmas

Case based instruction“Teaching begins not with a theoretical exegesis of domain concepts but with a real problem… rather than learning (and forgetting) all about a field before being allowed to solve a meaningful problem, case-based instruction is based on the belief that what you learn while trying to solve a complex problem you will better comprehend and retain much longer… The most important rationale for case-based instruction is that it at least simulates the kind of activity that students are preparing for.”

Jonassen 2004, pp 52-53

Problem based learning

In professional vocational training

In teacher training

In the classroom

TroubleshootingTroubleshooting is among the most commonly experienced kinds of problem solving in the professional world… the problems that are most completely and accurately recalled are those that are most difficult to solve, because the problems solver was more conceptually engaged in the process.

Jonassen 2004, p13

• Identify the fault

• Construct a mental

model

• Diagnose the problem

• Implement the solution

• Record the results

Pragmatic programming tips

Stay aware of what you're doing.

Don't code blindfolded.

Proceed from a plan.

Rely only on reliable things.

Document your assumptions.

Test assumptions as well as code.

Prioritize your effort.

Don't be a slave to history.

Is there an easier way?

Am I solving the right problem?

Why is this a problem?

What makes it hard?

Do I have to do it this way?

Does it have to be done at all?

http://www.codinghorror.com/blog/files/Pragmatic%20Quick%20Reference.htm

Advice on programming in Scratch

(from a 12 year old)

Start simple

Work on things that you like

If you have no clue what to do, fiddle around

Don't be afraid to experiment

Find a friend to work with, share ideas!

It’s OK to copy stuff (to give you an idea)

Keep your ideas in a sketch book

Build, take apart, rebuild

Lots of things can go wrong, stick with it

L Mode

Verbal

Analytic

Symbolic

Abstract

Temporal

Rational

Digital

Logical

Linear

R Mode

Holistic

Intuitive

Spatial

Non-rational

Analogic

ConcreteSynthetic

Non-verbal

Williamson 2009