code upskilling

Explaining Your Work — Briefings, Handovers and Interviews

You can do the work and you cannot make anybody act on it. This is the ordering: the answer in the first sentence, an incident report a manager will act on, interview answers that survive the second question, and a handover the next person can use without ringing you. Four artefacts, all written by you.

  • trending_upIntermediate
  • schedule6h 41m
  • menu_book12개 강의
  • publicEnglish
  • workspace_premiumBasic
Explaining Your Work — Briefings, Handovers and Interviews

개요

You can do the job. You find things other people miss, you fix things nobody else wants to touch, and when the week is over you can describe none of it in a way that makes anything happen. You have sat in a stand-up and heard yourself narrate a day. You have written an incident report that was accurate, complete, and forwarded to somebody technical with three questions attached. You have been asked a question in an interview and watched a perfectly good answer fall apart on the follow-up. None of that is a knowledge problem. Every one of them is an ordering problem, and ordering is learnable in a way that talent is not. You start with the first fifteen seconds. The conclusion, not the journey, then the detail if they want it, then what you need and from whom. Three lines — changed, blocked, need — replace forty seconds of verbs in a stand-up. Then the written artefact. Four headings, one page, a subject line that is a sentence. A severity score describes the hole and knows nothing about your building, so you learn to say what a nine point eight actually means here, including the ones where the honest answer is that it can wait. Then pressure. Six interview stories carrying a specific number, a setback said plainly and a decision that went partly against you. The three moves — acknowledge, answer, bound — that keep you credible in a room that has decided to test you. Then a mock interview where every answer gets pushed on twice, because the follow-up is where prepared material comes apart. Finally the two rooms nobody prepares for. The handover, which fails because you left out everything you knew. And the client briefing, where the deck is answering a question the room stopped asking, and the only move left is to shut the laptop. This is not spoken English. If you lose words under pressure, do the technical-english segment first.

강의 커리큘럼 · 4개 모듈

lock접근 시 이용 가능
  1. 01 Lead With the Answer
    3개 강의·1h 23m

    Every investigation you have ever run went evidence, evidence, evidence, conclusion, and you narrate it that way because that is how it is stored. The room does not want your head, it wants your…

  2. 02 A Report That Causes a Decision
    3개 강의·1h 46m

    A competent, technically correct incident report that does not contain the amount of money stolen is the failure this module is built around. Four headings: what happened, what it cost or risked,…

  3. 03 Answers That Survive Being Pushed
    3개 강의·1h 46m

    Six stories, one per area, each carrying a specific number, a setback said plainly and a decision that did not fully go your way. Then the three moves for a hostile question — acknowledge, answer,…

  4. 04 The Bit You Did Not Say
    3개 강의·1h 46m

    A handover is the only document you write where your own competence ruins it — you drop the context because you are carrying it, and the context is the only part the next person does not have. Then…

자주 묻는 질문

Explaining Your Work — Briefings, Handovers and Interviews에서 무엇을 배우나요?
You can do the work and you cannot make anybody act on it. This is the ordering: the answer in the first sentence, an incident report a manager will act on, interview answers that survive the second question, and a handover the next person can use without ringing you. Four artefacts, all written by
사전 경험이 필요한가요?
Explaining Your Work — Briefings, Handovers and Interviews을 시작하기 전에 기초 지식이 있으면 좋아요.
Explaining Your Work — Briefings, Handovers and Interviews은 얼마나 걸리나요?
Explaining Your Work — Briefings, Handovers and Interviews은 4개 모듈과 12개 강의로 구성되어 있고, 자신의 속도로 학습할 수 있어요.
어떻게 접근하나요?
Explaining Your Work — Briefings, Handovers and Interviews은 모든 유료 구독에 포함되어 있어요.

프로그래밍의 다른 강의

Python From a White Sheet
Beginner Python From a White Sheet 정확히 아홉 명의 학생이 이미 걸어간 경로입니다. 빈 파일에서 시작해 질문을 하고, 답을 검사하고, 잘못된 입력을 거부하는 프로그램까지. 프로그래밍 사전 경험 없음. 수학 필요 없음. 의도적으로 반복해서 부술 것입니다.
First Program — Scratch for ages 5–9
Beginner First Program — Scratch for ages 5–9 Nine Scratch blocks, three sessions of about twenty-five minutes, and one small program a child of five to nine builds themselves. Written for the parent sitting beside them: what to click, what they will get stuck on, what to say when it goes wrong, and when to keep your hands off the mouse.
과대광고 없는 AI
Beginner 과대광고 없는 AI 모델이 질문에 답할 때 실제로 무엇을 하는지, 왜 그것이 사고처럼 보이는 결과를 낳는지, 왜 인용문을 만들어내는지, 거의 아무도 설명하지 않는 비용 메커니즘: 채팅은 매번 대화 전체를 다시 전송합니다. 직접 계산해야 합니다.
Binary, Hex and Data Units
Beginner Binary, Hex and Data Units The topic that costs more marks than any other on the paper, taught by hand. Bits and bytes, binary and hex in all six directions, the 1000-versus-1024 trap, file sizes, transmission times, overflow, two's complement and character sets. Every module ends in a timed drill marked the way an examiner marks it.
IGCSE and GCSE Computer Science — 실제로 채점되는 이론
Intermediate IGCSE and GCSE Computer Science — 실제로 채점되는 이론 시험장에서도 살아남는 이론 반쪽. 메모리 계층 구조와 부팅 시 실제로 일어나는 일. 컴파일러, 인터프리터, 어셈블러, 그리고 그럴듯해 보이지만 점수를 얻지 못하는 답. 스프레드시트에서 시작해서 키와 정규화까지의 데이터베이스. Enter를 누르는 순간부터 페이지가 표시될 때까지의 전체 DNS 경로. 시스템 소프트웨어, 그리고 시험지에서 가장 쉬운 10점인 윤리 및 법률 섹션.
Programming for the Exam — Python Answers That Score
Intermediate Programming for the Exam — Python Answers That Score The programming half of the paper, taught at exam pitch. Pseudocode translated both ways, because the mark scheme is written in a notation nobody practises. Trace tables done column by column, including the ones with a loop and a condition inside it. Linear and binary search, bubble and insertion sort, what each costs and the comparison questions boards love. Validation against verification, and the boundary test data everybody forgets. Procedures against functions, and a systematic method for finding your own error with four minutes left.