Morning! Your plan for the week is on the board now, thank you.
A quick look back at Day 1: our rule says crashes first, then bugs that many players see, then new features, and you decided where T-106 belongs, the ticket that sends players' email addresses to an advertising partner. Then we read the METR study: experienced developers were 19% slower with AI tools, but they believed they were faster.
You also met AutoDev, an AI assistant that writes code, and Emre, our youngest developer. He started here in April and learns by fixing small bugs, so he worries that AutoDev takes exactly these tickets.
Today we check AutoDev with numbers, test it ourselves, and then you write our rule. On Wednesday I'll take your rule to the team. Before that, you prepare a short statement about it for your classmates. Let's start with Step 1.
Open your workbook for Development & IT and go to Day 2. Keep this page open next to it.
Download your workbook for Development & ITThis file is for your internship in Development & IT, with one part for Day 1 and one part for Day 2. Download it once and use it on both days. The file lands in your Downloads folder. If you missed Day 1, download the workbook now and go straight to Day 2: the check on this page only looks at your answers for Day 2.
Calculate and check
Kai collected the facts about AutoDev in M6. Use them and the ticket board from Day 1, which you find again below, to find out what AutoDev really saves. Round every result to one decimal place.
AutoDev at Respawn: the facts
Collected by Kai| Facts | |
|---|---|
| AutoDev | costs €39 per developer per month; Respawn has 3 developers |
| Promise of the company | routine tickets are done 30% faster, so they need 30% fewer hours (× 0.7) |
| Kai's worst case | routine tickets are 30% faster, but complex tickets take 19% longer (× 1.19), like the average in the study in M5 |
| Routine tickets in M3 | T-102, T-103 and T-104 (tasks like these exist in almost every game) |
| Complex tickets in M3 | T-101, T-105 and T-106 (you need to know Respawn's own code well) |
| One working hour of a developer | costs Respawn €45 in staff costs |
The ticket board
Open tickets this week, from Day 1| Ticket | What happens | Type | Players affected | Estimate |
|---|---|---|---|---|
| T-101 | The game crashes in level 12 when a player opens the shop. | Crash | about 40,000 | 12 h |
| T-102 | The shop shows the wrong price for the “Gold Pack”: €0.99 instead of €1.99. | Bug | every player who opens the shop | 3 h |
| T-103 | New feature: a dark mode for all menus. | Feature | none yet | 10 h |
| T-104 | The achievement “Speedrunner” does not unlock. | Bug | about 10,000 | 4 h |
| T-105 | Players with very old phones cannot start the game at all. | Crash | about 5,000 | 16 h |
| T-106 | A log file (Protokolldatei: a list of what happens in the game) that goes to an advertising partner contains the email addresses of players. | Bug | none see it | 6 h |
This week, the three developers have 40 h for tickets together. The rest of their time goes to meetings, tests and the servers.
- a) Add up the hours of the routine tickets in M3. Then calculate the hours with AutoDev: routine tickets need 30% fewer hours. Write down both calculations.
- b) Add up the hours of the complex tickets in M3. Then calculate Kai's worst case with AutoDev: complex tickets take 19% longer. Write down both calculations.
- c) Kai's worst case: add your results from a) and b) with AutoDev and write down the calculation. Compare the result with all six tickets without AutoDev. Then answer in one sentence: Does AutoDev save time in this case?
- d) Best case: routine tickets are 30% faster, and complex tickets stay the same. Write down three calculations: the hours the team saves in one week, what these hours are worth in staff costs (Personalkosten) in one week, and what they are worth in one month (count one month as four weeks). Then answer in one sentence: Is AutoDev worth its monthly price for the team (3 × €39)?
a) 3 + 10 + 4 = 17 h; 17 × 0.7 = 11.9 h.
b) 12 + 16 + 6 = 34 h; 34 × 1.19 = 40.46 h, rounded 40.5 h.
c) Without AutoDev: 51 h. With AutoDev in the worst case: 11.9 + 40.46 = 52.36 h (rounded 52.4 h). That is about 1.4 h more, so AutoDev saves no time in this case.
d) 51 − 45.9 = 5.1 h per week; 5.1 × €45 = €229.50 per week, about €918 in four weeks, against 3 × €39 = €117 a month. In the best case, the tool pays off clearly.
Test AutoDev yourself
The company behind AutoDev promises that routine tickets get 30% faster. In Kai's worst case, complex tickets take 19% longer (M6). Move the slider slowly from 0 h to 51 h: it changes how many of the 51 h of tickets are complex. Watch when AutoDev makes the week shorter and when it makes it longer. The week from Day 1 has 34 h of complex tickets. Then switch to the best case and compare.
| Complex tickets this week | Without AutoDev | With AutoDev, worst case | With AutoDev, best case |
|---|---|---|---|
| 0 h of 51 h | 51 h | 35.7 h | 35.7 h |
| 17 h of 51 h | 51 h | 44.0 h | 40.8 h |
| 34 h of 51 h | 51 h | 52.4 h | 45.9 h |
| 51 h of 51 h | 51 h | 60.7 h | 51.0 h |
The week from Day 1 has 34 h of complex tickets. The team has 40 h.
- On Day 1, Emre asked Kai in an email: “If AutoDev does all the small tickets, which tickets are left for me to learn on?” Answer him in two sentences. Use the list of routine tickets in M6 and the simulator: in which kind of week does AutoDev save the most time, and what does that mean for Emre?Help: “Emre, the routine tickets are ..., and these are the tickets you ... AutoDev saves the most time when ..., so ...”
A strong answer: The routine tickets are T-102, T-103 and T-104, the small tasks Emre learns on. The simulator shows that AutoDev saves the most time in weeks with many routine tickets, so exactly those tickets would go to AutoDev, and Emre would be left with code review or complex tickets he does not have the experience for yet.
What the simulator shows: in Kai's worst case, AutoDev makes the week longer as soon as more than about 31 of the 51 h are complex. The week from Day 1 (34 h complex) takes 52.4 h instead of 51 h.
Zoom out: the whole city
Leave Respawn Games for a moment and look at the whole city. Imagine that most game studios and software companies in Ohm City give their routine tickets to AI tools like AutoDev. Read M7 first: a real study about young workers.
Fewer first jobs?
A study about young workers and AIStanford researchers studied the pay data of millions of US workers (2025). Since late 2022, fewer young people aged 22 to 25 work in jobs where AI can do many tasks, such as software development: 13% fewer, compared with other jobs. For older workers there, the numbers stayed stable or grew. The researchers think AI replaces book knowledge more easily than experience.
Source: Brynjolfsson, Chandar and Chen, Stanford Digital Economy Lab, August 2025
- a) What happens to young developers like Emre? Complete this sentence in the box: “Most companies give routine tickets to AI, so young developers ..., therefore in five years ...”
- b) M7 says that AI replaces book knowledge more easily than experience. What could companies like Respawn do now, so that they still have experienced developers in five years? Sentence 1: name one idea. Sentence 2: explain how your idea gives young developers experience.
- Emre says: “Fine. Then I just learn how to check AI code instead of writing it myself.”
- c) Can Emre become an experienced developer this way? Judge in three sentences. Use M4 and M5 from Day 1: wrong code can look just as good as right code, and even experienced developers misjudged their work with AI.Help for c): “To check code, you need to ... In M5, even experienced developers ... So ...”
a) Most companies give routine tickets to AI, so young developers get fewer simple tasks to learn on, or are not hired at all, therefore in five years there are too few people with experience.
b) For example: Respawn keeps some routine tickets for juniors on purpose, or pairs every junior with an experienced developer. M7 shows that first jobs are already going down while experience is still needed; if nobody gains experience today, it becomes rare and expensive later.
c) Your own judgement counts. A strong answer: to check code, you need exactly the knowledge you get from writing code yourself, because wrong code looks just as good as right code (M4), and even experienced developers misjudged their work with AI (M5). So checking alone is probably not enough, unless Emre still writes part of the code himself. A different judgement is also possible if you give good reasons.
Your rule and your statement
Work alone. You write the rule for the whole team, like Kai would, so you say “our rule”. Kai takes your rule to the team on Wednesday. Before that, you prepare a short statement about it for your classmates. You can use AutoDev for everything, only for some tickets, or not at all. Choose the rule you can defend best.
- a) Write the team's rule for AutoDev in one sentence. Your rule answers three questions: Does the team use AutoDev? For which tickets? Who checks the code?Help: “The team uses AutoDev for ..., and ... checks the code” or “The team does not use AutoDev, and ...”
- b) Prepare your statement. Write exactly three sentences, one in each box.
- Sentence 1 starts with: “Our rule is ...” Write your rule from a) again as one sentence and start it with these words.
- Sentence 2 starts with: “The strongest reason for our rule is ...” Use a number from Step 1 or a fact from M5 or M7.
- Sentence 3 starts with: “The biggest weakness of our rule is ..., and we deal with it by ...”Help for sentence 3: “The biggest weakness of our rule is that it costs ... hours / that Emre ..., and we deal with it by ...”
- c) Everyone prepares this part. Ms Borgwardt chooses some of you to read their three sentences out loud. Then two classmates ask two questions: “Who loses because of your rule?” and “How much does your rule cost?” Write your answers here, one or two sentences each.
- Question 1: “Who loses because of your rule?”Help for question 1: Think of Emre. If your rule leaves AutoDev out, think of the team and the 51 h of work in 40 h.
- Question 2: “How much does your rule cost?”Help for question 2: Give two numbers: the price of your rule in euros per month and the hours of work in one week. Compare the hours with the 40 h the team has. AutoDev only for the routine tickets: 3 × €39 = €117 a month, and 11.9 h + 34 h = 45.9 h of work. AutoDev for all tickets: €117 a month, and your results from Step 1 c) (worst case) and d) (best case). No AutoDev: €0, but 51 h of work.
Every rule is possible. A strong rule answers all three questions in a). In b), sentence 2 has a number or a fact (51 h against 40 h, 11.9 h, 52.4 h, €229.50, €117, 19%, 13%), and sentence 3 names a real weakness and what you do about it.
Strong middle ways: AutoDev only for routine tickets, and a second person checks every line in a code review; Emre writes a fixed number of routine tickets himself every week; tickets like T-106 with personal data never go to AutoDev.
Question 1 needs a real person: with AutoDev, Emre loses the tickets he learns on; without AutoDev, the team has 51 h of work and only 40 h. Question 2: AutoDev costs €117 a month for the team. Only routine tickets with AutoDev: 11.9 + 34 = 45.9 h, so 5.1 h saved (€229.50 a week), but code review takes back part of it.
The statements
Stop here and wait until the statements start. While you wait, read your three sentences from Step 4 b) to yourself and check your answers in Step 4 c). Ms Borgwardt chooses some of you to read their three sentences. She also chooses two classmates who ask: the first one always asks “Who loses because of your rule?”, the second one always asks “How much does your rule cost?” If you read, answer with your notes from Step 4 c). If you ask, ask your question after each statement. Everyone writes notes, also the readers and the askers: after each statement, write down in a few words who loses, in the box for this step. At the end, write two sentences under your notes: What do the people who lose have in common?
- First, while you listen: who loses in each statement? A few words for each one. Then think about all the answers to the first question, “Who loses because of your rule?” Write two sentences under your notes: What do the people who lose have in common?Help: Look at your notes. Do the people who lose decide about the rule? “Most of the people who lose are ... They all ...” If you missed the statements: leave out the notes and write two sentences. Think of Emre, and of the people who lose under your own rule. What do they have in common?
A strong answer finds a pattern, for example: the people who lose are often at the start of their working life, have little money, or have no say in the decision. They carry the risk of the new tool, but they did not choose it.
Check your answer: Did you name what the people have in common, and not only who they are?
What I learned today
Write three sentences, one for each important thing you learned in Development & IT, in your own words. For example: when AutoDev saves time, and what your rule changes for someone like Emre.
Check your workbook
- Save your workbook.
- Choose the file here.
- Does the page name a step? Then an answer is still missing or very short. Fill in that box, save the file and choose it here again.
- When all answers are there, Kai answers you and the solutions appear under every step.
- Compare the solutions with your answers. Is a number or a fact in your answer wrong? Write “Correction:” and the right answer in the same box, under your answer.
- Is the answer your own opinion or your own rule? Then more than one answer can be good. Write “Also:” and one idea from the solution that you did not have.
- Save your workbook again.
Thank you for our rule. I'll pin it to the board for Wednesday's meeting and tell Jan where it came from.
It was great to have you in Development & IT. You helped us make a good decision, thank you!