Helping Teachers Teach Technology
We love to help our community – especially through our schools. We work career days and STEM fairs, we’re on curriculum committees and school tech committees. We truly enjoy working with younger students – perhaps it brings us back a few years, which is a great feeling. : )
We’re often asked what we look for in the people we hire; what skills should technology teachers give their students to help them succeed; what are the skills that are most important to us.
It’s a really good question. Technology advances so rapidly that technology curriculum taught to a 7th grader is ancient history by the time they reach working age.
But, when I sit down and think about what teachers should teach, there IS an answer to be found – one that makes sense.
Technology Seed works in IT. We’re challenged to proactively minimize IT problems, and fix the others.
What does it take to do that?
What can teachers teach that won’t be outdated by tomorrow’s technology? What do we, as a technology-focused organization, value in our employees?
Troubleshooting is at the core of what we do.
There are problems we need to fix and problems we want to prevent. Troubleshooting skills helps us understand the root cause of an issue.
We make up all kinds of snazzy names for troubleshooters: Help Desk, Network Engineering, IT Technician, Tier 2 Technician, etc. But it’s all troubleshooting. Those that are better at it tend to earn the more glamourous titles and work on more difficult but rewarding tasks.
How do we define troubleshooting? Good question.
Troubleshooting is the ability to quickly determine the root cause of an issue.
Great troubleshooters are what we look for.
Though I’m writing through a very narrow view of the business world – that of an IT tech – I’d bet a few cups of coffee that troubleshooting is at the basis of many jobs outside of technology – perhaps by a different name.
Hospitals have been shut down. The ones operating on sick people.
How does this happen?
Because those hospitals LET IT HAPPEN.
Our solution for controlling 100+ WAPs was to configure the Access Points to talk to one central cloud controller.
Mirroring your server allows you to maintain a EXACT replica of your data. If your server should fail, you can roll-over to the replica with near zero downtime.
The biggest mistake you can make in IT is not being involved.