Search Results for: 20 Techie Problems Every Student Can Fix

I’m reposting this for the start of a new school year–as a reminder to all my fellow tech teachers. Go geeks!

If you teach technology, you want to set the lab up so it’s inviting, non-intimidating, but doesn’t hide from the core ‘geek’ theme. In fact, from day one, exclaim that fact, be proud of your nerd roots. Even if you didn’t start out that way–say, you used to be a first grade teacher and suddenly your Admin in their infinite wisdom, moved you to the tech lab–you became a geek. You morphed into the go-to person for tech problems, computer quirks, crashes, and freezes. Your colleagues assumed you received an upload of data that allowed you to Know the answers to their every techie question. You are on a pedestal, their necks craned upward as they ask you, How do I get the Smartscreen to work? or We need the microphones working for a lesson I’m starting in three minutes. Can you please-please-please fix them?

As you organize your classroom, celebrate your geekiness. Flaunt it for students and colleagues. Play Minecraft. Use every new techie device you can get your hands on. That’s you now–you are sharp, quick-thinking. You tingle when you see an iPad. You wear a flash drive like jewelry. When your students walk into your class, they should start quivering with the excitement of, What new stuff will we experience today?

Here’s a summary of what happens your first day with a class. From this, you’ll figure out how to set up your classroom (no owl themes here. It’s all about bits and bytes):

• Introduce yourself—establish your bona fides. Share your blog, your background, your awards. Give them website addresses or post them to the class internet start page. You want to be easy to find.
• Tour the classroom with students. I walk K-2 around—they like getting out of their seats. Demystify any of the tech tools you will expect them to use—where they can get help in solving problems, what’s on the walls, where’s the printer/scanner/iPads/etc.

(more…)

Are you applying to be a tech teacher–wondering whether you know enough or have what it takes? Is it making your stomach churn and your head throb?

I understand–I went through that when I applied. I’ve learned a lot since then and I want to share some tips that will help you with what could be a life-changing conversation.

Before I get into the tips, I want you to remember: Your students will know less than you. You’ll start the year with tech training that provides students with tools for learning, that integrates into the school curriculum. If you are learning these the day before so you can teach them–you will know more. Your adult brain will absorb, sort, problem-solve, connect the dots, develop relationships much faster than the students who sit in your classroom. There are so many tech tools out there, many (many) teachers stay just a step ahead of their students, relying on their ability to see patterns based on the transfer of knowledge from prior learning. Every year after the first, you’ll adapt to what students know–go faster or slower. You will learn along with the students.

Here’s what you do for the interview:

(more…)

Dear Otto is an occasional column where I answer questions I get from readers about teaching tech. For your privacy, I use only first names.

Here’s a great question I got from Terry:

Any help for identifying and re-enforcing tech skills needed to take the online PARCC tests (coming in 2014-15)? Even a list of computer terms would help; copy, cut, paste, highlight, select; use of keys like tab, delete, insert; alt, ctrl and shift. There does not seem to be any guidelines as to prepping students on the “how to’s” of taking an online test and reading and understanding the directions. It would be great to take advantage of the time we have before the PARCC’s become a reality. Thanks!

Between March 24 and June 6, more than 4 million students in 36 states and the District of Columbia will take near-final versions of the PARCC and Smarter Balanced efforts to test Common Core State Standards learning in the areas of mathematics and English/language arts. Tests will be administered via digital devices (though there are options for paper-and-pencil). Though the tests won’t produce detailed, scaled scores of student performance (that starts next year), this field-testing is crucial to finding out what works and doesn’t in this comprehensive assessment tool, including the human factors like techphobia and sweaty palms (from both students and teachers).

After I got Terry’s email, I polled my PLN to find specific tech areas they felt their students needed help with in preparing for the Assessments. I got answers like these:

“They had to drag and drop, to highlight, and they had to compare and contrast. They had to write a letter. They had to watch a video, which meant putting on headphones. They had to fill in boxes on a table. There were a lot of different mouse-manipulation tasks.”

“Students are asked to retype a paragraph to revise. My students can’t type fast enough!”

“…questions [are] a mix of multiple-choice, problem solving, short-answer responses, and other tasks. Students had to drag and drop answers into different boxes.”

It boils down to five tech areas. Pay attention to these and your students will be much more prepared for Common Core assessments, be it PARCC or Smarter Balanced:

Keyboarding

Students need to have enough familiarity with the keyboard that they know where keys are, where the number pad is, where the F row is, how keys are laid out. They don’t need to be touch typists or even faciley use all fingers. Just have them comfortable enough they have a good understanding of where all the pieces are. Starting next school year, have them type fifteen minutes a week in a class setting and 45 minutes a week using keyboarding for class activities (homework, projects–that sort). That’ll do it.

(more…)

When you accepted the job to be your school’s tech teacher, you were probably excited, visions of cutting edge equipment at your disposal, training in the latest Google Apps, and a chance to collaborate with colleagues on extending the reach of education.

Well, maybe that happened, but so did a whole lot more. I sat down with about twenty of my ecolleagues over a virtual cuppa and asked them, really, what do they do all day? The answers may surprise you:

• teach classes, anywhere from 22-35 a week (that’s right–35. I offer up a little prayer for that colleague every morning), 30-45 minutes per class.
• grade assignments
• run the school’s tech-based programs (i.e., report cards, grade books, Everyday Math Online, Type to Learn 4 Online, Fountas and Pinnell, the online writing program)
• set up online accounts for teachers (on websites like KidBlogs, wikis, Google Apps, online tools)
• try–and fail–to get teachers to troubleshoot their own problems
• help faculty teach tech in their classes (because they don’t quite understand the geeky stuff)
• help faculty write lesson plans that integrate tech
• troubleshoot tech problems for teachers: tech teachers are the first stop with tech problems. It may start with fellow teachers running into the tech teacher’s class–even if s/he has students–and begging for help. If they can’t solve it (after they’ve spent an unspecified amount of time trying), it gets bumped up.

(more…)

Most of the teachers I know didn’t set out to be a tech teachers. They got here via the PE department or the 4th grade classroom or when laid off as an IT manager at some small company. Few took college classes to teach K-12 technology, nor did they say, “Gee, I have all the skills to be a top-notch tech teacher at my son/daughter’s elementary school. I think I’ll apply.” Most of us got here because 1) our current job disappeared (the Brits call it ‘made redundant’–isn’t that cool?) and this was the better alternative to unemployment, 2) our Principal offered us what Oprah calls a ‘life-defining moment’.

So here we are, doing our best, minute to minute hoping we can solve whatever catastrophe the Universe throws our way, usually with a solution that has something to do with servers and permissions. Fifteen years into it and still flummoxed on a daily basis, there are a few details someone should have told me when I first crossed the tech lab threshold. I mean, who forgot to mention these:

1. You don’t need to know everything. Do what you can and the rest gets kicked upstairs. That’s right. You are human. You don’t wear a cape and you can’t leap tall buildings.
2. You can make mistakes in front of the students. Really. Common Core is about problem solving–show how you work through a problem like sound doesn’t work or website won’t load. They’ll see your calm approach and emulate it when solving their own problems
3. Tech isn’t a digital puzzlebox, the end of a Mobius strip, or the solution to an irrational number. There are only about twenty problems that occur 80% of the time. Know them and know how to solve them. I’d include them here, but that would make this a massive article. I’ll cover it in my next series (stay tuned)
4. Common sense isn’t common. Don’t expect it to be. When a teacher frantically tells you their Smartscreen doesn’t work, start at the beginning: “Is it plugged in?” Every techie I know starts there and after fifteen years, I know why: It works.
5. When you wake up in the morning, remind yourself that no one can scare you–you’re the tech teacher. You do know more than the teachers. Don’t start by apologizing because you don’t know what you’re doing or telling her/him how you’ve never seen this problem before. Take a deep breath, think about it, consider the options, and start. Chances are, you’ll figure it out.
6. Tech works better integrated into classroom inquiry. Sure, you can create fun projects that use cool tech tools, but learning will be more authentic and scalable if students see you working with the classroom teacher. I use that term loosely–‘working with’. Sometimes, grade level teachers barely have time to breathe, much less meet to discuss tech tie-ins. I’ve been known to chat up parents about what’s happening in class, wander through and read room walls, ask students. I’m not above interrupting a teacher’s lunch with ‘just a few questions’.
7. Don’t jump in to solve student computer problems. If they’ve already seen a solution, let them work it out on their own. I have three extra computers in my lab and parent helpers always want to move students to a new computer when their usual seat is ‘broken’. I don’t let them. I have the student explain what the problem is and think through solutions. Only if none of them work do I allow switches.
8. There are days when coffee and aspirin count as two of the four food groups. Don’t let it bother it. It will pass. Your job as Go-to Geek requires you are always available. Tech teachers don’t get lunch hours or set breaks. When someone has a computer emergency, they need it taken care of NOW. Respect that. They’ve tried to make a tech lesson and now something doesn’t work and they’re frantic. Take care of them. It doesn’t happen that often. I promise.
9. Let students redo and make up work. Without taking points off. Wait, you say–I’ll have double the work! Truth, I’ve been doing this since I started and get only a handful of redos for each project. Sometimes I grade it with students and use the opportunity for teaching. The students who really care will really benefit. The others won’t take you up on it.
10. There will be days when you and Anything Tech are barely on speaking terms, when you wouldn’t fix another broken digital device if it came with a free puppy. When that happens, talk to other tech teachers. Online is a great way to do that. Join tech teacher groups, share problems, offer suggestions. You will feel brilliant and thankful for the kindness of others.
11. A feature is not a bug. The computer or the iPad or laptops aren’t broken when doing what they’re supposed to do, even if the user doesn’t like it. Gently point that out.

(more…)

The Number One reason–according to students–why their computer doesn’t work is… It’s broken. Can I move to a different computer??? Doesn’t matter why they’re wrong. My teacher’s job is to provide strategies so they can independently solve problems like these.

As a tech teacher, I know that half the problems that stop students short in their tech lessons are the same few. Once they’ve learned the following twenty-five trouble shooting solutions, they’ll be able to solve more than half of their ongoing problems.

In the three years since I first posted this, I haven’t changed my mind about these problems. These transcend platforms, curricula, and Standards. When your youngest students can’t double click that tiny little icon to open the program (because their fine motor skills aren’t up to it), teach them the ‘enter’ solution. When somehow (who knows how) the task bar disappears, show them how to bring it up with the ‘flying windows’ key. When their monitor doesn’t work, go through all possible solutions together (monitor power on, computer power on, plugged into duplex, etc.)

(more…)

If you teach technology, you want to set the lab up so it’s inviting, non-intimidating, but doesn’t hide from the core ‘geek’ theme. In fact, from day one, exclaim that fact, be proud of your nerd roots. Even if you didn’t start out that way–say, you used to be a first grade teacher and suddenly your Admin in their infinite wisdom, moved you to the tech lab–you became a geek. You morphed into the go-to person for tech problems, computer quirks, crashes, and freezes. Your colleagues assumed you received an upload of data that allowed you to Know the answers to their every techie question. You are on a pedestal, their necks craned upward as they ask you, How do I get the Smartscreen to work? or We need the microphones working for a lesson I’m starting in three minutes. Can you please-please-please fix them?

As you organize your classroom, celebrate your geekiness. Flaunt it for students and colleagues. Play Minecraft. Use every new techie device you can get your hands on. That’s you now–you are sharp, quick-thinking. You tingle when you see an iPad. You wear a flash drive like jewelry. When your students walk into your class, they should start quivering with the excitement of, What new stuff will we experience today?

Here’s a summary of what happens your first day with a class. From this, you’ll figure out how to set up your classroom (no owl themes here. It’s all about bits and bytes):

• Introduce yourself—establish your bona fides. Share your blog, your background, your awards. Give them website addresses or post them to the class internet start page. You want to be easy to find.
• Tour the classroom with students. I walk K-2 around—they like getting out of their seats. Demystify any of the tech tools you will expect them to use—where they can get help in solving problems, what’s on the walls, where’s the printer/scanner/iPads/etc.

(more…)

If you teach technology, it’s likely you’re a geek. Even if you didn’t start out that way–say, you used to be a first grade teacher and suddenly your Admin in their infinite wisdom, moved you to the tech lab–you became a geek. You morphed into the go-to person for tech problems, computer quirks, crashes and freezes.

Overnight, your colleagues assumed you received an upload of data that allowed you to Know the answers to their every techie question. It didn’t matter that yesterday, you were one of them. Now, you are on a pedestal, their necks craned upward as they ask you, How do I get the Smartscreen to work? or We need the microphones working for a lesson I’m starting in three minutes. Can you please-please-please fix them?

Celebrate your cheeky geekiness. Flaunt it for students and colleagues. Play Minecraft. That’s you now–you are sharp, quick-thinking. You tingle when you see an iPad. You wear a flash drive like jewelry. The first thing you do when you get to school is check your email

(more…)

If you teach technology, it’s likely you’re a geek. Even if you didn’t start out that way–say, you used to be a first grade teacher and suddenly your Admin in their infinite wisdom, moved you to the tech lab–you became a geek. You morphed into the go-to person for tech problems, computer quirks, crashes, and freezes.

Overnight, your colleagues assumed you received an upload of data that allowed you to Know the answers to their every techie question. It didn’t matter that yesterday, you were one of them. Now, you are on a pedestal, their necks craned upward as they ask you, How do I get the Smartscreen to work? or We need the microphones working for a lesson I’m starting in three minutes. Can you please-please-please fix them?

Celebrate your cheeky geekiness. Flaunt it for students and colleagues. Play Minecraft. That’s you now–you are sharp, quick-thinking. You tingle when you see an iPad. You wear a flash drive like jewelry. The first thing you do when you get to school is check your email

(more…)

If you teach technology, it’s likely you were thrown into it by your Admin. You used to be a first grade teacher or the science expert or maybe even the librarian and suddenly, you walked into school one day and found out you’d become that tech person down the hall you were always in awe of, the one responsible for classroom computers, programs, curriculum, and everything in between. Now that’s you–the go-to person for tech problems, computer quirks, crashes and freezes, and tech tie-ins for classroom inquiry.

You have no idea where to begin.

Here’s a peek into your future: On that first propitious day, everything will change. Your colleagues will assume you received a data upload of the answers to every techie question. It doesn’t matter that yesterday, you were one of them. Now, you will be on a pedestal, colleague’s necks craned upward as they ask , How do I get the Smartscreen to work? or We need microphones for a lesson I’m starting in three minutes. Can you please-please-please fix them? You will nod your head, smile woodenly, and race to your classroom for the digital manuals (if you’re lucky) or Google for online help.

Let me start by saying: Don’t worry. Really. You’ll learn by doing, just as we teach students. Take a deep breath, engage your brain, and let your brilliance shine.

(more…)