WEBVTT 00:00:00.000 --> 00:00:02.960 OK, so let's jump into this. We're looking at 00:00:02.960 --> 00:00:06.120 an article you flagged from hackscience .education. 00:00:06.120 --> 00:00:08.699 It's called Ed Tech for Ed Leaders, What We Want 00:00:08.699 --> 00:00:12.259 in IT Systems, by Gary Ackerman. That's the one. 00:00:12.539 --> 00:00:14.919 And our goal here, really, is to unpack what 00:00:14.919 --> 00:00:18.620 the source says about the priorities for IT professionals 00:00:18.620 --> 00:00:21.100 building and running tech in schools. Exactly. 00:00:21.899 --> 00:00:24.879 And the article gets straight to the point. It 00:00:24.879 --> 00:00:27.800 suggests IT pros kind of rally around three core 00:00:27.800 --> 00:00:31.300 ideas, three words. for what they want systems 00:00:31.300 --> 00:00:33.759 to be. Three specific words. Yeah. And these 00:00:33.759 --> 00:00:35.579 seem to be the heart of it, right? What IT leaders 00:00:35.579 --> 00:00:37.439 are aiming for. The first one the article brings 00:00:37.439 --> 00:00:40.439 up is reliable. Reliable, yeah. Fundamentally, 00:00:40.439 --> 00:00:43.320 it's about availability. I mean, can people actually 00:00:43.320 --> 00:00:45.799 use the system when they need it, where they 00:00:45.799 --> 00:00:47.859 need it? Right. The article uses a good parallel. 00:00:48.899 --> 00:00:51.119 Thinking about your internet provider or web 00:00:51.119 --> 00:00:53.380 hosting, they're always talking about uptime. 00:00:53.640 --> 00:00:56.759 Ah, uptime percentages. Like, is it 99 % available 00:00:56.759 --> 00:00:59.530 or 99 %? 0 .9%, that kind of thing. Exactly. 00:00:59.630 --> 00:01:01.890 And for someone in a school, a teacher, a student, 00:01:02.310 --> 00:01:04.569 it's very direct, isn't it? Yeah, totally. If 00:01:04.569 --> 00:01:06.750 the Wi -Fi connects every single time, if that 00:01:06.750 --> 00:01:09.750 learning platform works during class, you just 00:01:09.750 --> 00:01:11.950 think, OK, it's reliable. That's how you perceive 00:01:11.950 --> 00:01:14.629 it. And the source, it does note the challenges 00:01:14.629 --> 00:01:16.609 in schools. You've got all sorts of different 00:01:16.609 --> 00:01:20.849 devices, maybe old wiring, and just tons of connections 00:01:20.849 --> 00:01:23.590 needed all at once. So hitting high reliability 00:01:23.590 --> 00:01:27.390 there, it's a It's a real task. It's not just 00:01:27.390 --> 00:01:29.349 a number. Makes sense. It has to be there when 00:01:29.349 --> 00:01:32.269 needed. OK, so that's reliable. What's the second 00:01:32.269 --> 00:01:35.250 characteristic from the article? Robust. What's 00:01:35.250 --> 00:01:38.390 that about? Robust networks. They're about handling 00:01:38.390 --> 00:01:41.450 the load, you know, capacity. Can the system 00:01:41.450 --> 00:01:44.769 cope when, say, everyone logs on at 9 a .m.? 00:01:44.769 --> 00:01:46.950 Oh, yeah. The article talks about measuring this 00:01:46.950 --> 00:01:49.670 off in a data rate bandwidth, basically trying 00:01:49.670 --> 00:01:53.870 to avoid latency. Latency, the dreaded slowness, 00:01:53.909 --> 00:01:56.370 that spinning icon. Right. We've all been there. 00:01:56.469 --> 00:01:57.890 When you're trying to load a video or something 00:01:57.890 --> 00:01:59.650 critical. And the article makes a good point. 00:01:59.790 --> 00:02:02.670 We often blame our computer, but that lag, that 00:02:02.670 --> 00:02:04.790 latency, it's usually the network struggling. 00:02:04.890 --> 00:02:07.030 So not enough capacity for the traffic at that 00:02:07.030 --> 00:02:09.909 moment. Pretty much. The system can't deliver 00:02:09.909 --> 00:02:12.789 the data fast enough. So robust system is built 00:02:12.789 --> 00:02:15.169 to prevent that bottleneck, keeps things smooth, 00:02:15.169 --> 00:02:17.449 even under pressure. Super important in a classroom 00:02:17.449 --> 00:02:20.110 setting, right? Definitely. OK, so reliable is 00:02:20.110 --> 00:02:23.090 available. Robust is. Performs well under load 00:02:23.090 --> 00:02:25.110 got it. Yeah, what's the third piece? The third 00:02:25.110 --> 00:02:28.629 one is secure This is all about protection protecting 00:02:28.629 --> 00:02:32.310 the system the data Controlling access keeping 00:02:32.310 --> 00:02:34.990 things safe a secure network lets the right people 00:02:34.990 --> 00:02:37.469 in easily But keeps the wrong people and you 00:02:37.469 --> 00:02:39.949 know malware and other threats out does the article 00:02:39.949 --> 00:02:43.669 mention specific threats like hackers. It mentions 00:02:43.669 --> 00:02:46.669 external hackers, yeah, and also malware. But 00:02:46.669 --> 00:02:48.990 importantly, it also stresses that security isn't 00:02:48.990 --> 00:02:52.349 just stopping bad things. It's also having plans, 00:02:52.949 --> 00:02:55.509 solid systems, to restore everything quickly 00:02:55.509 --> 00:02:58.150 if something does go wrong, like a data breach 00:02:58.150 --> 00:03:00.949 or some outage. Ah, the recovery aspect makes 00:03:00.949 --> 00:03:02.590 sense. You need to get back up and running fast 00:03:02.590 --> 00:03:04.930 in a school. Exactly. Minimize that disruption 00:03:04.930 --> 00:03:07.259 to learning. Security in schools must be a bit 00:03:07.259 --> 00:03:09.219 of a balancing act, though. You need it tight, 00:03:09.379 --> 00:03:12.159 but students and staff, they need fairly easy 00:03:12.159 --> 00:03:14.900 access to learning tools. Does the article touch 00:03:14.900 --> 00:03:18.060 on that usability balance? It sort of implies 00:03:18.060 --> 00:03:20.979 it. It doesn't go deep into how, but the focus 00:03:20.979 --> 00:03:24.919 on authorized users getting what they need while 00:03:24.919 --> 00:03:28.319 blocking others, it suggests it can't before 00:03:28.319 --> 00:03:30.219 it knocks. Right. It has to actually enable learning, 00:03:30.319 --> 00:03:32.479 not just block threats. It's a different setup 00:03:32.479 --> 00:03:36.639 than, say, a bank's IT. Context is key. OK, so 00:03:36.639 --> 00:03:39.479 there we have it. Reliable, robust, and secure. 00:03:40.060 --> 00:03:42.740 The three pillars Gary Ackerman outlines in this 00:03:42.740 --> 00:03:45.400 hack science dot education piece. And thinking 00:03:45.400 --> 00:03:48.159 about it, given the source focuses on tech management 00:03:48.159 --> 00:03:50.919 in schools, these three really nail why they're 00:03:50.919 --> 00:03:53.800 so critical for education IT folks. They directly 00:03:53.800 --> 00:03:55.800 shape the day to day experience. Absolutely. 00:03:55.840 --> 00:03:57.759 They're not just tech jargon. They're, well, 00:03:58.000 --> 00:04:00.159 foundational for making education work with today's 00:04:00.159 --> 00:04:01.759 technology. It really does give you a different 00:04:01.759 --> 00:04:04.379 perspective. So for you listening. Think about 00:04:04.379 --> 00:04:06.800 the tech you interact with in your own school 00:04:06.800 --> 00:04:09.919 or learning environment, the Wi -Fi, the online 00:04:09.919 --> 00:04:12.120 platforms, all that stuff. How does thinking 00:04:12.120 --> 00:04:15.240 about reliability, robustness, and security change 00:04:15.240 --> 00:04:17.639 how you view those systems now? And maybe reflect 00:04:17.639 --> 00:04:20.300 a bit. Which of those three feels like the most 00:04:20.300 --> 00:04:22.399 critical for your learning or teaching? Where 00:04:22.399 --> 00:04:24.139 do you feel the pinch most often? Something to 00:04:24.139 --> 00:04:24.500 chew on.