AI Developer · Module 6 · The Developer as a Person

Competences and Developing the Developer

The lesson treats the competences that all five developer functions demand. Its claim is that a developer's competence is a claim that needs evidence: a record of judgement exercised, separating assisted from unaided performance, assessed by a second assessor outside the line, dated and with an expiry. Participants work with six competence groups, the kinds of evidence, frameworks, career ladders and hiring, and write a competence record and development plan.

Lesson 27 of 33Chapter 2775 minutes

Read the chapterThe whitepaperThe slides

All courses / AI Developer / Module 6 / Chapter 27

Learning objectives

After the lesson the participant can:

Key concepts

Six competence groups
Frame and specify; design and system thinking; read, review and verify; delegate and bound; steward; and AI literacy for the role. They are the book's own synthesis, and no research-based taxonomy for a workplace that uses AI broadly has been tested against outcomes.
Attendance is not competence
Neither attendance at a course nor tool use shows competence, and confidence is not evidence. Self-assessment, acceptance rate and completion of a module are listed in the evidence table as not evidence.
The lower figure governs
Evidence must separate assisted from unaided performance, and where both figures exist the lower governs. A group whose evidence has lapsed is shown as lapsed, not as the last level reached.
Second assessor
A person outside the line who observes or checks the exercises and writes what was seen. A record assessed by the line manager alone is exposed to the pressures of appraisal, and one assessed by an assistant to the failure the record exists to detect.
Competence record
The artefact CMP: level per group with evidence date and expiry, the developer's own comment and a development plan with one or two gaps and protected time. It is personal data, limited by stated purpose and reader, and it does not rank the developer.

Interactive exercises

Do them here and get feedback at once. Choose a card and then where it belongs, or drag it.

Interactive exercise 1 · Match

What each kind of evidence shows

Match each kind of evidence of competence to what the chapter's table says it shows.

Interactive exercise 2 · Scenario

Two results for one developer

Apply the chapter's rules for setting a level in a competence record.

Teaching plan

15 minLecture on the six groups and on AI literacy under Article 4 of the AI Act as the floor, with the competence record as the instrument.
15 minParticipants take the evidence table and choose, for one post, which evidence would serve each group and which familiar measures are not evidence.
10 minThe teacher walks through CMP-NR-2030-DEV-01 for a mid-level developer and the three-part interview with its rules that protect candidates.
25 minExercise: pairs write a competence record and development plan for a mid-level developer.
10 minPlenary on ladders: what changes when the gate moves from tenure to evidence, and where a second assessor is found in a small team.

Discussion

  1. In the worked example the lower figure came with the assistant's comment in view. What does that say about the condition under which the developer usually works?
  2. A common framework gives comparability and risks a form that does not fit a local post; a grade structure tied to a collective agreement fits and changes slowly. Which trade-off does your organisation face?
  3. The panel does not use an AI system to filter, rank or evaluate candidates. How does that follow from the prohibitions of Chapter 4?

Written exercise

Exercise · 25 minutes

A competence record for a mid-level developer

Write a competence record for a mid-level developer you know (anonymised), or for a developer in the integration and data team of Nordvik Region. State the purposes, the readers and what the record is not used for. Choose the groups the post needs. For each group choose evidence from the chapter's table, for example a seeded-defect review with and without the assistant's comment visible, an unaided explanation of a module and a revert drill. Name the second assessor. Set the level per group from the lower of the assisted and unaided evidence, with evidence date and expiry. Leave space for the developer's comment and set a plan with one or two gaps, the means, the date and protected time.

Deliverable: A competence record with purposes, readers, groups, evidence, second assessor, levels with dates and expiries, and a development plan.

Self-test

Choose an answer to see whether it is right, or open the answer below each question.

  1. Which expiry does the chapter use for competences that decay with disuse, such as reading and verification without the tool?

    Show the answer

    B. 90 days
    The chapter uses 90 days for competences that decay with disuse and 180 days for the revert drill, because a record true in January says little about a developer in July who has not done the task since.

  2. What does a seeded-defect review, done with and without the assistant's comment visible, show?

    Show the answer

    C. Whether the developer finds defects, and whether the assistant's comment changes that
    The evidence table lists it as the check on verification: a change with a known number of defects reviewed in both conditions. It is also the first part of the interview the chapter proposes.

  3. How is a competence group shown when its evidence has passed its expiry?

    Show the answer

    A. As lapsed, not as the last level reached
    Step seven of the practical guide: review at expiry, and show a group whose evidence has lapsed as lapsed. Evidence expires, and the record should not carry forward a level nobody has recently seen.