Category: Problem solving

Here are ideas of apps and websites that teachers in my PLN used successfully in the past during Hour of Code:

Kindergarten

Start kindergartners with problem solving. If they love Legos, they’ll love coding

1. BotLogic–great for Kindergarten and youngers
2. Code–learn to code, for students
3. How to train your robot–a lesson plan from Dr. Techniko
4. Kodable--great for youngers–learn to code before you can read
5. Primo–a wooden game, for ages 4-7
6. Program a human robot (unplugged)
7. Scratch Jr.

1st Grade

1. Code–learn to code, for students
2. Espresso Coding–for youngers
3. Foos–app or desktop; K-1
4. Hopscotch–programming on the iPad
5. Primo–a wooden game, for ages 4-7
6. Scratch Jr.
7. Tynker

(more…)

Coding–that mystical geeky subject that confounds students and teachers alike. Confess, when you think of coding, you see:

…when you should see

December 5-11, Computer Science Education will host the Hour Of Code–a one-hour introduction to coding, programming, and why students should love it. It’s designed to demystify “code” and show that anyone can learn the basics to be a maker, a creator, and an innovator.

(more…)

I took a Classroom 2.0 Live webinar last year on rolling out the Hour of Code in the classroom. There were so many great things about that webinar, but one I’ll share today is why teachers DON’T participate in Hour of Code. Here are what the webinar participants said:

How about you? Why are you NOT doing Hour of Code?

Stay tuned for these Hour of Code articles on how to present coding in your classroom:

1. Hour of Code: What is it? (November 15th)
2. Hour of Code Suggestions by Grade Level (November 16th)
3. 10 Projects to Kickstart Hour of Code (November 17th)

(more…)

Here are the top ten problem-solving tips according to Ask a Tech Teacher readers:

• Tech Tip #108: Got a Tech Problem? Google It!
• What to do when your Computers Don’t Work
• 25 Techie Problems Every Student Can Fix–Update
• How to Teach Students to Solve Problems
• I Can Solve That Problem…
• Let Students Learn From Failure
• Let’s Talk About Habits of Mind
• Computer Shortkeys That Streamline Your Day
• #81: Problem Solving Board
• 5 Ways to Cure Technophobia in the Classroom

(more…)

Creating a shortkey for a program will quickly become a favorite with your students. I use it for the snipping tool–because we use that a lot in class–but you can create one for any program you use a lot. Then I discovered how to create a shortkey for it:

• Go to Start
• Right click on the desired program
• Select ‘properties’
• Click in ‘shortcut’
• Push the key combination you want to use to invoke the snipping tool. In my case, I used Ctrl+Alt+S
• Save

Here’s a video to show you:

(more…)

Every week, I share a website that inspired my students. This one is perfect for Hour of Code. Make yourself a hero for an hour:

Age:

Grades 3-8 (or younger, or older)

Topic:

Problem-solving, critical thinking, building

Address:

Minecraft

Review:

(more…)

Here are ideas of apps and websites that teachers in my PLN used successfully in the past during Hour of Code:

Kindergarten

Start kindergartners with problem solving. If they love Legos, they’ll love coding

1. BotLogic–great for Kindergarten and youngers
2. Code–learn to code, for students
3. Daisy the Dinosaur—intro to programming via iPad
4. How to train your robot–a lesson plan from Dr. Techniko
5. Kodable--great for youngers–learn to code before you can read
6. Move the Turtle–programming via iPad for middle school
7. Primo–a wooden game, for ages 4-7
8. Program a human robot (unplugged)
9. Scratch Jr.

1st Grade

1. Code–learn to code, for students
2. Hopscotch–programming on the iPad
3. Primo–a wooden game, for ages 4-7
4. Scratch Jr.
5. Tynker

(more…)

I took a Classroom 2.0 Live webinar last year on rolling out the Hour of Code in the classroom. There were so many great things about that webinar, but one I’ll share today is why teachers DON’T participate in Hour of Code. Here are what the webinar participants said:

How about you? Why are you NOT doing Hour of Code?

(more…)

Coding–that mystical geeky subject that confounds students and teachers alike. Confess, when you think of coding, you see:

…when you should see

December 7-13, Computer Science Education will host the Hour Of Code–a one hour introduction to coding, programming, and why students should love it. It’s designed to demystify “code” and show that anyone can learn the basics to be a maker, a creator, and an innovator.

(more…)

Too often, students–and teachers–believe learning comes from success when in truth, it’s as likely to be the product of failure. Knowing what doesn’t work is a powerful weapon as we struggle to think critically about the myriad issues along our path to college and/or career. As teachers, it’s important we reinforce the concept that learning has many faces.

Here are ten ways to teach through failure:

Use the Mulligan Rule

What’s the Mulligan Rule? Any golfers? A mulligan in golf is a do-over. Blend that concept into your classroom. Common Core expect students to write-edit-resubmit. How often do you personally rewrite an email before sending? Or revise instructions before sharing? Or have ‘buyer’s remorse’ after a purchase and wish you could go back and make a change? Make that part of every lesson. After submittal, give students a set amount of time to redo and resubmit their work. Some won’t, but those who do will learn much more by the process.

Don’t define success as perfection

When you’re discussing a project or a lesson, don’t define it in terms of checkboxes or line items or 100% accuracy. Think about your favorite book. Is it the same as your best friend’s? How about the vacation you’re planning–would your sister pick that dream location? Education is no different. Many celebrated ‘successful’ people failed at school because they were unusual thinkers. Most famously: Bill Gates, who dropped out of college because he believed he could learn more from life than professors.

Education pedagogists categorize these sorts of ideas as higher-order thinking and Habits of Mind–traits that contribute to critical thinking, problem solving, and thriving. These are difficult to quantify on a report card, but critical to life-long success. Observe students as they work. Notice their risk-taking curiosity, how they color outside the lines. Anecdotally assess their daily efforts and let that count as much as a summative exam that judges a point in time.

Let students see you fail

One reason lots of teachers keep the same lesson plans year-to-year is they are vetted. The teacher won’t be surprised by a failure or a question they can’t answer. Honestly, this is a big reason why many eschew technology: Too often, it fails at just that critical moment.

Revise your mindset. Don’t hide your failures from students. Don’t apologize. Don’t be embarrassed or defeated. Show them how you recover from failure. Model the steps you take to move to Plan B, C, even X. Show your teaching grit and students will understand that, too, is what they’re learning: How to recover from failure.

Share strategies for problem solving

Problems are inevitable. Everyone has them. What many people DON’T have is a strategy to address them. Share these with students. The Common Core Standards for Mathematical Practice is a good starting point. Mostly, they boil down to these simple ideas:

• Act out a problem
• Break problem into parts
• Draw a diagram
• Guess and check
• Never say ‘can’t’
• See patterns
• Notice the forest and the trees
• Think logically
• Distinguish relevant from irrelevant info
• Try, fail, try again
• Use what has worked in the past

Post these on the classroom wall. When students have problems, suggest they try a strategy from this list, and then another, and another. Eventually, the problem will resolve, the result of a tenacious, gritty attack by an individual who refuses to give up.

Exult in problems

If you’re geeky, you love problems, puzzles, and the maze that leads from question to answer. It doesn’t intimidate or frighten you, it energizes you. Share that enthusiasm with students. They are as likely to meet failure as success in their lives; show them your authentic, granular approach to addressing that eventuality.

Assess grit

Success isn’t about right and wrong. More often, it’s about grit–tenacity, working through a process, and not giving up when failure seems imminent. Statistically, over half of people say they ‘succeeded’ (in whatever venture they tried) not by being the best in the field but because they were the last man standing.

Integrate that into your lessons. Assess student effort, their attention to detail, their ability to transfer knowledge from earlier lessons to this one, their enthusiasm for learning, how often they tried-failed-retried, and that they completed the project. Let students know they will be evaluated on those criteria more than the perfection of their work.

Let students teach each other

There are many paths to success. Often, what works for one person is based on their perspective, personal history, and goals. This is at the core of differentiation: that we communicate in multiple ways–visually, orally, tactally–in an effort to reach all learning styles.

Even so, students may not understand. Our failure to speak in a language they understand will become their failure to learn the material. Don’t let that happen.  Let students be the teachers. They often pick a relationship or comparison you wouldn’t think of. Let students know that in your classroom, brainstorming and freedom of speech are problem solving strategies.

Don’t be afraid to move the goalposts

Even if it’s in the middle of a lesson. That happens all the time in life and no one apologizes, feels guilty, or accommodates your anger. When you teach a lesson, you constantly reassess based on student progress. Do the same with assessment.

But make it fair. Let students know the changes are rooted in your desire that they succeed. If you can’t make that argument, you probably shouldn’t make the change.

Success is as much serendipity as planning

Think of Velcro and post-it notes–life-changing products resulting from errors. They surprised their creators and excited the world. Keep those possibilities available to students.

Don’t reward speed

Often, students who finish first are assigned the task of helping neighbors or playing time-filler games. Finishing early should not be rewarded. Or punished. Sometimes it means the student thoroughly understood the material. Sometimes it means they glossed over it. Students are too often taught finishing early is a badge of honor, a mark of their expertise. Remove that judgment and let it be what it is.

(more…)