$ cat programme
My programme
This page gives you the overview of the programme you are enrolled in: its curriculum, your lesson calendar, the parts of your grade, the rules and the documents.
Register once
Register with the email address you gave your course organiser.
The site finds your group
The site reads your institution and group from the list your teacher keeps.
Your programme opens
This page shows your programme, and the 4 sections show your lessons, modules, projects and exam.
example screenthe overview of a programme
Holon Institute of Technology · group 62121-31
Agentic software engineering
next lesson [date]
Lesson 9 · Cognified products and agent economics
The warm-up quiz opens before the lecture starts. Keep Learn in class open beside Zoom during the lesson.
your group
- institution
- Holon Institute of Technology
- group
- 62121-31
- teacher
- Mikael Gorsky
- signed in as
- student@gmail.com
The site placed you in this group from the list your teacher keeps.
About the programme
The course teaches you to build software by directing AI agents and checking what they produce, instead of typing most of the code yourself.
In this way of working you frame the problem, write the specification and judge the result, and the agent writes the code. The course calls your side of this work equipping and verifying. Equipping means giving the agent the right problem, specification, project context, tools, permissions and limits. Verifying means checking the agent's output against a defined standard before you accept it. Every module covers one part of equipping, one part of verifying, or the cycle that connects them.
The course teaches a discipline and not a single tool. Agents now produce code faster than people can review it, and much of that code is not ready to merge. What separates professional from casual use of the same agent is the structure around its work: specification, context, version control, verification gates, review and an audit trail. These methods rest on long-standing ideas from software engineering and design, so they stay useful when the tools change.
You run your projects as a spiral of improvement and not as a single delivery. You revise the specification each time the agent's output shows something new about what is needed. You practise this on 2 projects that run through the semester: the Tribunal, which the whole class builds, and an individual project of your own design.
what you will be able to do
Frame a software problem with a problem statement, a testable definition of done and an out-of-scope list.
Write a specification that an agent can act on without constant intervention.
Set up an agent's context files, tools and permissions for a given task.
Use version control as a safety layer, with commits before agent runs and clear atomic messages.
Design verification gates that catch real failures, and review agent-written code against a merge-readiness standard.
Break a task into parts for several agents and judge whether the extra cost is justified.
Identify security risks specific to agentic systems, such as prompt injection, and limit them through least privilege and an audit trail.
Run a project through several turns of the specification spiral and leave a trail that another engineer can inspect.
Evaluate new agentic development tools by how they handle transparency, control and permissions.
You need programming and software engineering knowledge at the level of a third-year computer science student. The course does not teach programming or software engineering basics. Set up accounts for the course tools before the first lesson.
class engagement 33% of the grade
Reading the textbook, doing the exercises, substantial questions and answers in class, live demonstrations of your own workflow, and material you send the lecturer from following the field.
the Tribunal 33% of the grade
The charge sheet written as a specification, the 7 versioned agent prompts, a protocol that reports the 3 verdicts side by side, and the progression from 1 model toward several.
individual project 33% of the grade
The framing document and at least 3 turns of the specification spiral.
after you sign in
Sign in to see your programme.
the curriculum, part by part and module by module
your lesson calendar and the Zoom link
the parts of your grade and the rules for projects
the programme documents
Register once, with the email address you gave your course organiser.