Heb ik eerdere ervaring nodig?

Enige voorkennis wordt aanbevolen voordat je Technical English — Being Understood at Work start.

Hoeveel tijd kost Technical English — Being Understood at Work?

Technical English — Being Understood at Work bevat 4 modules en 12 lessen. Je leert in je eigen tempo.

Hoe krijg ik toegang?

Technical English — Being Understood at Work is inbegrepen bij elk betaald abonnement.

code communication

Technical English — Being Understood at Work

Your English is fine in writing and it fails you out loud. This is the method that fixed that for working engineers and analysts: write a script, mark it, read it aloud five times, record the first take and the last take, and listen to both. Four set pieces, all recorded by you.

trending_upIntermediate
schedule6h 39m
menu_book12 lessen
publicEnglish
workspace_premiumBasic

lock_open Start met leren

Technical English — Being Understood at Work

Inleiding

You are competent. You read specifications in English, your written messages are clear, and nobody has ever complained about them. Then you speak, live, to people, and it goes badly. You lose the word. You start a sentence you cannot finish. You say the tool name and the room stays blank. That is not a language problem. It is a preparation problem wearing a language problem's coat. This segment is the method as it actually ran with working professionals — a SOC analyst in Barcelona, an Italian threat-intelligence analyst, a Russian-speaking infrastructure engineer, a Polish network engineer. You write a script. Not notes — a script, in full sentences, five minutes, three cases. You put the unresolved things first and label everything ongoing or completed. You take the jargon out and put human language in: "someone's Windows PC", not "the endpoint". You attach a "so what" to every technical statement, because naming a tool and stopping is the fault that appeared independently in two separate learners. You mark the page for emphasis and pauses. You read it aloud five or more times in one sitting. You record the first attempt and the last attempt, listen to both in order, and the difference is audible — which is the only feedback that has ever convinced anybody. You will build and record four things: a stand-up, a shift handover flagging a suspicious service account, an incident briefing for a manager who does not do technology, and an answer to a hostile question you did not see coming. No grammar. No accent work. Your accent is fine and it is staying.

Cursusopbouw · 4 modules

lockBeschikbaar met toegang

01 Voordat je je mond opendoet
3 lessen·1h 18m

Aantekeningen bezwijken onder druk. Een script niet. Dat is het hele argument van deze module en het is geen stilistische voorkeur — het is wat herhaaldelijk gebeurde met mensen die improviseerden…
02 Volgorde, en woorden die mensen gebruiken
3 lessen·1h 32m

De meeste mensen briefen in de volgorde waarin dingen gebeurden, wat het ene ding dat de zaal nodig had, begrafft. Onopgelost eerst. Dan lopend. Dan voltooid, laatst en kort. En het woord "endpoint"…
03 So What
3 lessen·1h 41m

Je hebt de tool benoemd. Je hebt nooit gezegd waarom iemand erom zou geven. Elke technische uitspraak die je voor een belanghebbende doet, bestaat uit drie onderdelen en je verzendt er één van. Tool,…
04 When It Goes Wrong Live
3 lessen·2h 8m

Tot nu toe werd ervan uitgegaan dat je je zin af kunt maken. Deze module gaat ervan uit dat je dat niet doet. Het eindigt met de volledige sessie — ruwe opname, script, vijf passes, final take, beide…

Veelgestelde vragen

Wat leer ik in Technical English — Being Understood at Work?: Your English is fine in writing and it fails you out loud. This is the method that fixed that for working engineers and analysts: write a script, mark it, read it aloud five times, record the first take and the last take, and listen to both. Four set pieces, all recorded by you.
Heb ik eerdere ervaring nodig?: Enige voorkennis wordt aanbevolen voordat je Technical English — Being Understood at Work start.
Hoeveel tijd kost Technical English — Being Understood at Work?: Technical English — Being Understood at Work bevat 4 modules en 12 lessen. Je leert in je eigen tempo.
Hoe krijg ik toegang?: Technical English — Being Understood at Work is inbegrepen bij elk betaald abonnement.

Meer in Programmeren

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.

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.

Beginner AI Without the Hype What the model is actually doing when it answers you, why that produces something that looks like thinking, why it invents citations, and the cost mechanic almost nobody explains: a chat resends the entire conversation on every single turn. You will do the arithmetic yourself.

Beginner Python From a White Sheet De exacte volgorde die negen studenten al hebben gelopen, van een leeg bestand naar een programma dat vragen stelt, antwoorden controleert en slechte invoer weigert. Geen eerdere programmeerervaring. Geen wiskunde. Je zult het herhaaldelijk opzettelijk breken.

Intermediate IGCSE and GCSE Computer Science — Theory That Actually Gets Marked The theory half of the paper, taught so it survives the exam room. The memory hierarchy and what actually happens at boot. Compilers, interpreters and assemblers, including the answer that sounds right and scores nothing. Databases from a spreadsheet up to keys and normalisation. DNS and the full path between pressing Enter and seeing the page. Systems software, and the ethical and legal section that is the easiest ten marks on the paper.

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.