AI in software development
M27
Review generated code and catch hallucinated dependencies.
Online10–15 min
Training by function
Software development
Coding assistants speed up your teams, and introduce flaws, hallucinated dependencies and secret leaks. This path makes critical review a reflex.
Why this path
Generated code is never ready without review.
An assistant can suggest a dependency that does not exist (typosquatting), reproduce a vulnerable pattern or prompt you to paste a real secret. Responsibility for the deliverable stays with the developer. This path anchors dependency verification, flaw hunting and secret hygiene.
The module dedicated to your function
The common core for everyone
The baseline reflexes your whole team shares, whatever the job.
Understanding generative AI
M01
Demystify the probabilistic engine and distinguish it from predictive AI.
Online10–15 min
A probabilistic engine predicts the most plausible word without understanding meaning: brilliant, but sometimes wrong. Never feed it confidential data in a public tool.
RegisterHallucinations
M02
Identify fabricated information and how to verify it at the source.
Online10–15 min
A hallucination is fabricated information presented confidently. The risk is real on expert tasks (figures, citations): every output must be verified at the source.
RegisterUsing an assistant well
M03
Structure your prompts (Role + Context + Task + Format) and iterate.
Online10–15 min
Good results come from a structured prompt and an iterative approach. Providing examples of the desired output markedly improves quality.
RegisterConfidential data: the basic reflexes
M04
Sort your data and de-identify rigorously before every prompt.
Online10–15 min
Anything entered into a public AI can be retained and reused. Never client names, salaries or API keys; removing just the name is not enough.
RegisterApproved tools and "shadow AI"
M05
Recognize shadow AI and have tools approved by IT.
Online10–15 min
Shadow AI is the use of unapproved tools, often free and poorly protective. The reflex: check the IT allowlist and get the tool approved before using it.
RegisterYou remain responsible: the human role
M06
Apply "human-in-the-loop" and the "four eyes" method.
Online10–15 min
AI is a gifted junior assistant with no judgment: final responsibility stays human. Review and validate every deliverable as if you had written it yourself.
RegisterGo deeper for your context
The modules most relevant to the risks specific to your function.
Prompt injection and AI agent risks
M13
Understand hidden instructions and apply least privilege.
Online10–15 min
An injection hides instructions in content read by the AI (email, PDF, web page). Protect against it with least privilege and human validation of sensitive actions.
RegisterData leaks: what you must never paste
M11
Identify the blacklist never to submit to a public AI.
Online10–15 min
Never internal source code, salary data or active API keys. Default terms allow retention; "keep this to yourself" has no technical effect.
RegisterIntellectual property and generated content
M17
Grasp the copyright grey zone and the risk of infringement.
Online10–15 min
A creation from a simple prompt is generally not protectable, lacking human input. Legal value comes from creative contribution, not prompt length.
RegisterReady to equip your team?
Enroll your teams in our AI-literacy and governance training paths, from the common core to function-specific use cases.
Immediate access · 100% online · at your own pace