WEBVTT 00:00:00.000 --> 00:00:03.419 Welcome to the deep dive. Today, we're getting 00:00:03.419 --> 00:00:05.059 into something really critical in the digital 00:00:05.059 --> 00:00:07.940 age. The professional contract basically, how 00:00:07.940 --> 00:00:10.279 it changes. Yeah, when everything runs on networks 00:00:10.279 --> 00:00:12.519 and devices, right? What is being responsible 00:00:12.519 --> 00:00:15.220 actually? look like. Exactly. So we're diving 00:00:15.220 --> 00:00:17.620 into the framework for ethical, legal, and responsible 00:00:17.620 --> 00:00:20.820 computing. They call it ELR. And we're specifically 00:00:20.820 --> 00:00:23.579 drawing on Gary Ackerman's work over at hackscience 00:00:23.579 --> 00:00:26.780 .education. And it's a solid framework because 00:00:26.780 --> 00:00:29.519 it really targets the professional user. It has 00:00:29.519 --> 00:00:33.200 a strong focus on educators, sure. But honestly, 00:00:33.439 --> 00:00:36.159 these ideas apply pretty broadly to anyone handling 00:00:36.159 --> 00:00:39.939 tech resources and sensitive info. And we absolutely 00:00:39.939 --> 00:00:41.799 have to start with the stakes here. Because one 00:00:41.799 --> 00:00:44.719 of the biggest things from these sources, it's 00:00:44.719 --> 00:00:47.439 a stark legal point, really. When a professional, 00:00:47.600 --> 00:00:50.240 say an educator, violates professional standards, 00:00:50.579 --> 00:00:54.179 or worse, the actual law, the school, the organization, 00:00:54.479 --> 00:00:56.880 they have zero legal obligation to protect that 00:00:56.880 --> 00:00:59.359 person. You could be found personally liable, 00:00:59.579 --> 00:01:02.039 full stop. That really hammers home that this 00:01:02.039 --> 00:01:05.260 isn't just like, Good advice. It's your personal 00:01:05.260 --> 00:01:07.400 standard of care, legally speaking. Absolutely. 00:01:07.519 --> 00:01:09.459 And that totally flips the script, doesn't it? 00:01:09.500 --> 00:01:11.799 You're not just following rules because HR put 00:01:11.799 --> 00:01:14.099 out a memo. Right. You're doing it to protect 00:01:14.099 --> 00:01:16.680 yourself fundamentally. And also, you know, the 00:01:16.680 --> 00:01:18.780 mission of the place you work for, that threat 00:01:18.780 --> 00:01:21.459 of personal liability, that's what gives these 00:01:21.459 --> 00:01:24.019 duties real teeth. OK, so let's unpack this framework 00:01:24.019 --> 00:01:26.700 then. The source breaks it down into six core 00:01:26.700 --> 00:01:29.599 duties, and the first three are all about protection. 00:01:30.379 --> 00:01:33.170 Protecting systems. data, and intellectual property. 00:01:33.829 --> 00:01:36.510 Let's start with the system itself. Seems basic, 00:01:36.569 --> 00:01:38.549 but. Well, yeah. Basic, but complex. Partaking 00:01:38.549 --> 00:01:40.750 the system isn't just putting a password on your 00:01:40.750 --> 00:01:43.310 laptop. It's about governance. Governance. Yeah. 00:01:43.650 --> 00:01:45.609 Keeping the technology safe from threats, both 00:01:45.609 --> 00:01:48.650 inside and out. That means things like preventing 00:01:48.650 --> 00:01:51.290 unauthorized configuration changes, thinking 00:01:51.290 --> 00:01:54.629 about insider threats, and dealing with shadow 00:01:54.629 --> 00:01:58.049 IT. Ah, shadow IT. That's when people bring in 00:01:58.049 --> 00:02:00.409 their own apps or devices onto the network without 00:02:00.409 --> 00:02:03.620 approval. Exactly. So system protection is about 00:02:03.620 --> 00:02:05.900 maintaining the integrity and security of the 00:02:05.900 --> 00:02:08.020 whole shared system, not just your little corner 00:02:08.020 --> 00:02:11.240 of it. If you skip security updates or install 00:02:11.240 --> 00:02:13.819 something that creates a vulnerability, well, 00:02:14.000 --> 00:02:16.180 that's a failure on your part. Gotcha. It's about 00:02:16.180 --> 00:02:18.819 the professional's duty to the shared infrastructure, 00:02:19.360 --> 00:02:21.439 which, okay, leads naturally to the next thing. 00:02:22.179 --> 00:02:24.479 protecting what's on that infrastructure, the 00:02:24.479 --> 00:02:27.159 data, precisely. If step one is the hardware 00:02:27.159 --> 00:02:29.780 and network, step two is the information itself. 00:02:29.840 --> 00:02:31.800 And the source makes a really important distinction 00:02:31.800 --> 00:02:34.539 here. Which is? You have to protect data against 00:02:34.539 --> 00:02:37.520 damage or destruction that's purposeful, obviously, 00:02:37.580 --> 00:02:39.599 but also against damage or destruction that is 00:02:39.599 --> 00:02:41.439 inadvertent. Inadvertent. OK, that word jumps 00:02:41.439 --> 00:02:43.879 out. Why the emphasis there? Well, because that's 00:02:43.879 --> 00:02:45.860 often where the biggest risks lie, especially 00:02:45.860 --> 00:02:48.520 with things like PII, personally identifiable 00:02:48.520 --> 00:02:51.759 information and compliance rules like GDPR. Hmm. 00:02:52.020 --> 00:02:54.139 Your intent doesn't really matter if you accidentally 00:02:54.139 --> 00:02:56.319 cause a data breach or lose critical records. 00:02:56.680 --> 00:02:58.919 Inadvertent could be anything from, you know, 00:02:59.240 --> 00:03:01.659 bad data lifecycle management for getting backups 00:03:01.659 --> 00:03:04.159 or just, oops, delete in the wrong folder. No 00:03:04.159 --> 00:03:06.759 malice needed. Huh. But how do you even defend 00:03:06.759 --> 00:03:09.360 yourself if someone says you lost data inadvertently? 00:03:09.960 --> 00:03:11.680 It sounds like you're judged just on the outcome. 00:03:11.800 --> 00:03:15.080 Well, yes and no. It forces you to show you did 00:03:15.080 --> 00:03:17.819 your job properly. You need to demonstrate due 00:03:17.819 --> 00:03:22.199 diligence. So documentation. documentation, following 00:03:22.199 --> 00:03:23.740 procedures, showing you have the right training, 00:03:24.020 --> 00:03:28.139 keeping records. The question becomes, did you 00:03:28.139 --> 00:03:30.800 act reasonably? Did you take the proper precautions? 00:03:31.460 --> 00:03:35.080 It demands a level of care that's maybe, well, 00:03:35.219 --> 00:03:36.800 maybe more than people are used to. That makes 00:03:36.800 --> 00:03:38.800 sense. Like if you were sloppy with sensitive 00:03:38.800 --> 00:03:40.319 student files, even if you didn't mean for them 00:03:40.319 --> 00:03:42.930 to get out, the failure is still on you. OK, 00:03:43.009 --> 00:03:45.069 and that flows right into the third protection 00:03:45.069 --> 00:03:48.030 pillar, intellectual property. Ah, yes, IP. This 00:03:48.030 --> 00:03:50.330 is really the legal bedrock of using digital 00:03:50.330 --> 00:03:52.689 stuff professionally. And it's way beyond just 00:03:52.689 --> 00:03:55.689 not pirating software. It means really understanding 00:03:55.689 --> 00:03:58.430 and sticking to software licenses. Is it proprietary? 00:03:58.849 --> 00:04:00.650 What are the rules? Is it open source? What are 00:04:00.650 --> 00:04:02.870 those obligations? Creative Commons, each has 00:04:02.870 --> 00:04:05.379 specific conditions. And those conditions can 00:04:05.379 --> 00:04:07.520 get really tricky, especially in schools, right? 00:04:07.919 --> 00:04:10.300 Right. Using a single user license for a whole 00:04:10.300 --> 00:04:13.460 lab or photocopying chapters from a digital textbook 00:04:13.460 --> 00:04:16.339 without permission. Exactly. And doing that directly 00:04:16.339 --> 00:04:19.379 exposes you, the professional, to legal trouble. 00:04:20.060 --> 00:04:21.839 It doesn't matter if your department head said, 00:04:22.060 --> 00:04:24.439 just make it work, save some money. Wow. If there's 00:04:24.439 --> 00:04:26.540 an audit or a lawsuit, the fact that someone 00:04:26.540 --> 00:04:29.310 told you to do it... Legally, that's often irrelevant. 00:04:29.790 --> 00:04:31.990 The liability snaps right back to the person 00:04:31.990 --> 00:04:34.129 who actually violated the copyright or license. 00:04:34.410 --> 00:04:37.250 Okay, so those first three duties, protect system, 00:04:37.709 --> 00:04:41.709 protect data, protect IP, they're heavily focused 00:04:41.709 --> 00:04:44.709 on the individual's legal responsibility. Almost 00:04:44.709 --> 00:04:47.149 like self -preservation in a way. Yeah, you could 00:04:47.149 --> 00:04:49.589 see it like that. Legal and physical protection. 00:04:49.889 --> 00:04:52.129 But ELR computing, according to this source, 00:04:52.589 --> 00:04:54.610 it's more than just covering your bases legally. 00:04:54.810 --> 00:04:56.769 It's also about how you interact within your 00:04:56.769 --> 00:04:59.329 community, how you teach. Right. This is where 00:04:59.329 --> 00:05:01.990 it shifts quite profoundly, I think, from just 00:05:01.990 --> 00:05:05.410 protecting assets to actively building a responsible 00:05:05.410 --> 00:05:08.589 community. Which brings us nicely to duty number 00:05:08.589 --> 00:05:12.870 four, share common resources. Now, on the surface, 00:05:13.230 --> 00:05:15.269 this sounds like, you know, don't be a jerk. 00:05:15.449 --> 00:05:17.709 Let other people use the printer. Why is this 00:05:17.709 --> 00:05:20.910 elevated to a core duty? Because it's not just 00:05:20.910 --> 00:05:22.730 about politeness. It's about keeping the whole 00:05:22.730 --> 00:05:26.050 operation running smoothly. Think about shared 00:05:26.050 --> 00:05:28.350 resources, maybe specialized software, network 00:05:28.350 --> 00:05:30.670 bandwidth, even physical devices like 3D printers 00:05:30.670 --> 00:05:33.050 or projectors. They're finite. If one person 00:05:33.050 --> 00:05:35.649 uses them wastefully or selfishly or even breaks 00:05:35.649 --> 00:05:38.529 them through misuse, it directly harms everyone 00:05:38.529 --> 00:05:40.490 else who relies on that resource. It hinders 00:05:40.490 --> 00:05:42.970 the team or the class or the whole school's mission. 00:05:43.509 --> 00:05:46.470 Ah, I see. So hogging the high speed color printer 00:05:46.470 --> 00:05:49.089 for a massive rough draft isn't just annoying. 00:05:49.339 --> 00:05:51.920 Right. It's arguably an ethical lapse because 00:05:51.920 --> 00:05:54.899 you're depleting a shared asset inefficiently, 00:05:55.240 --> 00:05:56.600 potentially blocking someone else who really 00:05:56.600 --> 00:05:59.699 needs it. Precisely. And acting like that directly 00:05:59.699 --> 00:06:02.279 undermines the next duty, which is maybe the 00:06:02.279 --> 00:06:04.620 most crucial one for educators, but really for 00:06:04.620 --> 00:06:07.920 any leader. Duty number five, model responsible 00:06:07.920 --> 00:06:11.680 use. The source puts it so simply and powerfully, 00:06:12.079 --> 00:06:14.399 our students will do as we do. Mm -hmm. Mm -hmm. 00:06:14.600 --> 00:06:17.439 Modeling is everything. Because students or junior 00:06:17.439 --> 00:06:19.600 colleagues or whoever you influence, they watch 00:06:19.600 --> 00:06:21.959 and they copy, often without even thinking about 00:06:21.959 --> 00:06:24.439 it. If you cut corners on licenses, if you're 00:06:24.439 --> 00:06:26.399 careless with pathways, if you waste resources, 00:06:26.819 --> 00:06:29.699 you're implicitly teaching that behavior. You're 00:06:29.699 --> 00:06:31.660 setting the standard. So modeling isn't just 00:06:31.660 --> 00:06:34.220 about reciting rules. It's about living the professional 00:06:34.220 --> 00:06:36.339 ethic you want others to adopt. It builds that 00:06:36.339 --> 00:06:37.839 culture of governance we talked about earlier. 00:06:37.980 --> 00:06:40.160 OK. So modeling sets the behavioral standard. 00:06:40.300 --> 00:06:43.259 Yeah. The final duty, number six, seems to define 00:06:43.259 --> 00:06:46.100 the core ethical obligation regarding who gets 00:06:46.100 --> 00:06:48.660 to participate. This is ensure equitable access. 00:06:49.000 --> 00:06:51.399 And this is where the source uses that really 00:06:51.399 --> 00:06:55.420 strong word. It does. Duty six, ensuring equitable 00:06:55.420 --> 00:06:58.839 access for all students to use computers. This 00:06:58.839 --> 00:07:01.540 is where the author argues that educators using 00:07:01.540 --> 00:07:04.870 computers just for enrichment or as a reward, 00:07:05.389 --> 00:07:08.050 they're guilty of malpractice. Malpractice, wow. 00:07:08.310 --> 00:07:11.430 That's a heavy charge. Let's dig into that. Why 00:07:11.430 --> 00:07:15.170 is using tech as a reward considered malpractice? 00:07:15.310 --> 00:07:17.750 What's the reasoning? It goes back to what technology 00:07:17.750 --> 00:07:19.970 is today. Digital literacy, being comfortable 00:07:19.970 --> 00:07:22.769 with these tools, it's not an extra anymore. 00:07:22.930 --> 00:07:25.589 It's fundamental. Like reading or writing. Pretty 00:07:25.589 --> 00:07:28.009 much. It's a basic requirement for participating 00:07:28.009 --> 00:07:31.449 in society in the economy. So if you treat computer 00:07:31.449 --> 00:07:34.470 access as a prize for good behavior or only for 00:07:34.470 --> 00:07:37.209 the advanced students, you risk making the digital 00:07:37.209 --> 00:07:39.610 divide even wider. You're essentially giving 00:07:39.610 --> 00:07:41.970 vital preparation mainly to kids who might already 00:07:41.970 --> 00:07:44.629 have advantages while potentially shutting out 00:07:44.629 --> 00:07:46.990 the students who need that tech rich education 00:07:46.990 --> 00:07:49.790 the most to catch up or get ahead. So it shifts 00:07:49.790 --> 00:07:52.110 technology from being a standard tool like, I 00:07:52.110 --> 00:07:54.149 don't know, like textbooks or lab equipment that 00:07:54.149 --> 00:07:56.899 everyone gets. to being a conditional privilege. 00:07:57.699 --> 00:07:59.519 And if the students who are maybe struggling, 00:08:00.000 --> 00:08:02.319 who aren't hitting certain benchmarks, never 00:08:02.319 --> 00:08:04.980 earn that computer time, wow, the professional 00:08:04.980 --> 00:08:06.699 is actually failing in their duty to prepare 00:08:06.699 --> 00:08:08.920 all of them. That's the argument. If you connect 00:08:08.920 --> 00:08:11.500 all these dots, this principle demands integrating 00:08:11.500 --> 00:08:13.980 technology meaningfully into the core curriculum 00:08:13.980 --> 00:08:16.339 for every student, regardless of where they're 00:08:16.339 --> 00:08:18.939 starting from. It really elevates the whole conversation 00:08:18.939 --> 00:08:21.160 beyond just following rules into active social 00:08:21.160 --> 00:08:24.399 responsibility. Okay, wow. That was quite the 00:08:24.399 --> 00:08:27.379 deep dive into those six duties. So just to quickly 00:08:27.379 --> 00:08:31.500 recap, we had protect the system, protect the 00:08:31.500 --> 00:08:33.320 data, and protect intellectual property, the 00:08:33.320 --> 00:08:36.220 sort of legal and security foundations. The individual 00:08:36.220 --> 00:08:38.200 liability pieces. Right. And then the community 00:08:38.200 --> 00:08:41.019 ethics side. Share common resources, model responsible 00:08:41.019 --> 00:08:43.960 use in that really powerful one. Ensure equitable 00:08:43.960 --> 00:08:46.179 access. And you know, even if you listening aren't 00:08:46.179 --> 00:08:48.080 an educator, these principles, they still land. 00:08:48.639 --> 00:08:50.980 Protecting IP, modeling good digital conduct, 00:08:51.179 --> 00:08:53.039 sharing resources fairly, understanding data 00:08:53.039 --> 00:08:55.220 responsibility. That applies in pretty much any 00:08:55.220 --> 00:08:57.080 professional setting today. Your reputation, 00:08:57.360 --> 00:08:59.580 maybe even your job, could hinge on getting this 00:08:59.580 --> 00:09:01.840 stuff right. Yeah. It really brings it back to 00:09:01.840 --> 00:09:03.600 that core idea from the source. It's not just 00:09:03.600 --> 00:09:05.580 about the company policy. It's about your personal 00:09:05.580 --> 00:09:07.919 compliance with ethics and the law. Absolutely. 00:09:08.179 --> 00:09:10.820 That personal liability piece is key. So here's 00:09:10.820 --> 00:09:13.820 something to chew on. How does your own sense 00:09:13.820 --> 00:09:16.259 of responsibility shift when you realize that, 00:09:16.379 --> 00:09:18.139 at the end of the day, it's your adherence to 00:09:18.139 --> 00:09:20.340 the law, not just the organization's policy, 00:09:20.980 --> 00:09:24.419 that protects you? When you understand that the 00:09:24.419 --> 00:09:26.840 company or school might not have your back legally 00:09:26.840 --> 00:09:29.440 if you mess up, what steps do you need to take, 00:09:29.580 --> 00:09:31.379 maybe even starting today, to make sure you're 00:09:31.379 --> 00:09:34.240 not just compliant, but genuinely acting ethically 00:09:34.240 --> 00:09:36.600 and responsibly online? Something to think about 00:09:36.600 --> 00:09:37.539 next time you log in.