code ai

AI at Work Without Leaking the Company

Somebody has handed you "sort out our AI policy". Your staff are already using these tools on personal accounts with company data, and have been for months. This segment gets you from that position to three artefacts you can put in front of a director: a one-page acceptable-use policy that is true today, a data-class table, and a vendor question set.

  • trending_upIntermediate
  • schedule6h 56m
  • menu_book12個のレッスン
  • publicEnglish
  • workspace_premiumBasic
AI at Work Without Leaking the Company

ブリーフィング

The request arrives with no budget and no scope. It lands on the security lead, the IT lead, or on whoever in the company has actually read a set of terms all the way through. That is usually you. The first thing to accept is that you are not at the start. You are somewhere in the middle. People in your company have been pasting work into chat windows on personal accounts since long before anyone asked whether they should, and the question in front of you is not whether to allow it. It is what is already leaving, on which accounts, under which terms, and what you are going to do about it this month. Across four modules you will run a discovery that tells you what is actually in use rather than what you assume, work out precisely what leaves the building when somebody pastes, build an approved tool set short enough that people follow it, learn to test a vendor's retention and training claims instead of accepting them, sort your company's data into three classes concrete enough to print on one page, and decide which decisions in your organisation may never be handed to a machine — and how you would prove a human actually looked. The method for the policy itself is borrowed wholesale from the compliance segment, B1, and it is the same rule for the same reason: write the policy to the state you are actually in today, then improve it. An aspirational AI policy is a signed, dated description of your own non-compliance, and it is worse than having no policy at all. Segment A1, AI Without the Hype, covers how the tool works and the personal habit of redacting before you paste. This segment does not repeat either. It is the organisational version: the controls, the written evidence, and the accountability when work produced this way goes out under your company's name. **This is not legal advice.** Where UK GDPR or the EU AI Act touch what you are doing, this segment describes the direction those obligations point in and stops there. Your data protection officer and your lawyer decide the rest, and the sentence "our security lead read a course" has never once helped anybody in a regulatory conversation.

コースアウトライン · 4個のモジュール

lockアクセスで解放
  1. 01 It Is Already Happening
    3個のレッスン·1h 46m

    You do not have a decision to make about whether to allow this. That decision was made months ago by about forty people independently, none of whom told you. Your first job is to find out what they…

  2. 02 Tools, Vendors and Written Controls
    3個のレッスン·1h 36m

    A ban list is a list of things to route around. Every name you add to it makes the list less likely to be read and more likely to be treated as a challenge. The control that works is the short list…

  3. 03 What May Be Pasted, and What May Go Out
    3個のレッスン·1h 31m

    A rule that requires judgement at the moment of pasting is not a rule. It is a hope. This module produces a table somebody can read in four seconds while holding a customer's file.

  4. 04 The Policy, the Human, and the First Hour
    3個のレッスン·2h 3m

    The rule is borrowed from B1 and it does not change because the subject is AI. Write the policy to the state you are actually in today. Then improve it, and change the page on the day the work lands.

よくある質問

AI at Work Without Leaking the Companyでは何を学べますか?
Somebody has handed you "sort out our AI policy". Your staff are already using these tools on personal accounts with company data, and have been for months. This segment gets you from that position to three artefacts you can put in front of a director: a one-page acceptable-use policy that is true t
事前の経験が必要ですか?
AI at Work Without Leaking the Companyを開始する前に、ある程度の事前知識が推奨されます。
AI at Work Without Leaking the Companyはどのくらいの時間がかかりますか?
AI at Work Without Leaking the Companyには4個のモジュールと12個のレッスンが含まれています。自分のペースで学習できます。
アクセスするにはどうすればよいですか?
AI at Work Without Leaking the Companyは任意の有料サブスクリプションに含まれています。

プログラミングのその他

Python From a White Sheet
Beginner Python From a White Sheet The exact sequence nine students have already walked, from a blank file to a program that asks questions, checks the answers and refuses bad input. No prior programming. No maths. You will break it repeatedly, on purpose.
AI Without the Hype
Beginner AI Without the Hype What the model is actually doing when it answers you, why that produces something that looks like thinking, why it invents citations, and the cost mechanic almost nobody explains: a chat resends the entire conversation on every single turn. You will do the arithmetic yourself.
First Program — Scratch for ages 5–9
Beginner First Program — Scratch for ages 5–9 Nine Scratch blocks, three sessions of about twenty-five minutes, and one small program a child of five to nine builds themselves. Written for the parent sitting beside them: what to click, what they will get stuck on, what to say when it goes wrong, and when to keep your hands off the mouse.
Binary, Hex and Data Units
Beginner Binary, Hex and Data Units The topic that costs more marks than any other on the paper, taught by hand. Bits and bytes, binary and hex in all six directions, the 1000-versus-1024 trap, file sizes, transmission times, overflow, two's complement and character sets. Every module ends in a timed drill marked the way an examiner marks it.
IGCSE and GCSE Computer Science — Theory That Actually Gets Marked
Intermediate IGCSE and GCSE Computer Science — Theory That Actually Gets Marked The theory half of the paper, taught so it survives the exam room. The memory hierarchy and what actually happens at boot. Compilers, interpreters and assemblers, including the answer that sounds right and scores nothing. Databases from a spreadsheet up to keys and normalisation. DNS and the full path between pressing Enter and seeing the page. Systems software, and the ethical and legal section that is the easiest ten marks on the paper.
Programming for the Exam — Python Answers That Score
Intermediate Programming for the Exam — Python Answers That Score The programming half of the paper, taught at exam pitch. Pseudocode translated both ways, because the mark scheme is written in a notation nobody practises. Trace tables done column by column, including the ones with a loop and a condition inside it. Linear and binary search, bubble and insertion sort, what each costs and the comparison questions boards love. Validation against verification, and the boundary test data everybody forgets. Procedures against functions, and a systematic method for finding your own error with four minutes left.