Speak and write
Vorbire și scriere. Scrii un mesaj pentru canalul de Slack al echipei și exersezi un dialog despre cum se gestionează un incident tehnic.
Говорение и письмо. Напишите короткое сообщение для рабочего чата и подготовьте диалог о том, как обсудить технический сбой с коллегами.
Resolving a Broken Build
Role-play a conversation in pairs. One of you is the tech lead who noticed a red pipeline, and the other is a developer who pushed a change earlier today. Discuss what happened, locate the issue, and decide how to fix it without blaming each other.
• Ask what happened and who pushed the last commit to the main branch.
• Explain that you made a small change but did not expect it to break the build.
• Discuss the steps to reproduce the error or decide to revert the commit immediately.
• Apologize for the accident and talk about how to avoid this issue next time.
Post-Incident Slack Message
Write a message to your team's Slack channel (#dev-alerts) explaining why the main branch was red this morning, how you fixed it, and what the team should do now. Write between 40 and 120 words.
• Explain clearly what went wrong (for example, a unit test failed after a commit).
• State what actions you took to resolve it (for example, 'I reverted the change...').
• Remind the team to pull the latest green build before they start their daily work.
Despre această lecție
Această lecție te ajută să comunici clar în timpul incidentelor tehnice de pe proiect. Vei învăța să pui întrebări directe despre cine a produs o eroare și cum să descrii fluxul de lucru în Git.
Об этом уроке
Этот урок поможет вам четко общаться во время технических инцидентов в проекте. Вы научитесь задавать прямые вопросы о том, кто допустил ошибку, и описывать рабочий процесс в Git.