UC00599 · Interagir em inglês · sector informática

Há um pacote premium desta unidade: um PowerPoint editável de 100 ou mais diapositivos, um manual em PDF e dois testes com correção. Esta sebenta continua gratuita.

Introdução

O inglês é a língua franca da informática mundial. Mais de 90% da documentação técnica, 80% dos cursos online avançados, a maioria das conferências internacionais e quase todas as comunidades técnicas (Stack Overflow, GitHub, Reddit) usam inglês.

Sem domínio de inglês:

• Limita-se acesso a recursos modernos.
• Carreira fica circunscrita ao mercado local.
• Salários significativamente menores.
• Impossível trabalhar em multinacionais ou remotamente para empresas estrangeiras.

Esta UC (50h) foca-se em inglês técnico aplicado ao sector informática: vocabulário, leitura de documentação, escrita de emails e bug reports, listening de tutoriais, speaking em standups e reuniões, e preparação para entrevistas técnicas.

Objectivo do curso: chegar ao nível B2+ (CEFR), o mínimo exigido pela maioria das ofertas júnior em IT internacional.

1. Por que inglês em IT

1.1 Estatísticas

• ~95% das linguagens de programação têm documentação primária em inglês.
• Top 100 cursos online de IT: > 90% em inglês.
• Stack Overflow: > 90% das perguntas/respostas em inglês.
• GitHub: > 95% do código com comentários em inglês.
• Salários globais: ofertas internacionais (remote) pagam 2-5× o mercado português.

1.2 Níveis CEFR

Common European Framework of Reference:

• A1 (Beginner): saudações simples.
• A2 (Elementary): situações quotidianas básicas.
• B1 (Intermediate): conversas familiares, viagens.
• B2 (Upper Intermediate): conversas profissionais, MÍNIMO para IT júnior.
• C1 (Advanced): fluente em contexto profissional, presentações.
• C2 (Proficient): praticamente nativo.

Objectivo: começar nível B1, terminar B2+ no fim do curso.

1.3 Vantagens de inglês em IT

• Acesso a recursos topo (livros, cursos, papers).
• Comunidades globais (Stack Overflow, Reddit).
• Conferências internacionais.
• Trabalho remoto internacional.
• Salários significativamente superiores.
• Mobilidade de carreira.
• Lifelong learning (livros novos saem em inglês primeiro).

1.4 Mitos

❌ "Não preciso de inglês, posso usar tradutor". ✅ Tradutor é ajuda, não substituto. Termos técnicos perdem nuance.

❌ "Sou developer, não preciso de falar". ✅ Reuniões, code reviews, entrevistas — falar é essencial.

❌ "Vou aprender quando precisar". ✅ Aprender demora anos. Começa já.

❌ "Português chega para o mercado nacional". ✅ Mercado nacional cada vez mais conectado a internacional.

2. Vocabulário técnico

2.1 Programming fundamentals

2.2 Software development

2.3 Version control (Git)

2.4 Web development

2.5 Databases

2.6 DevOps and infrastructure

2.7 Job titles

2.8 Common idioms in tech

• "Move fast and break things": avançar rápido aceitando erros.
• "Ship it!": lançar (mesmo com imperfeições).
• "Drink your own champagne" / "Dogfooding": usar o próprio produto.
• "Yak shaving": tarefa que leva a outra que leva a outra.
• "Bikeshedding": discutir detalhes triviais ignorando o importante.
• "Technical debt": código mau acumulado.
• "Spaghetti code": código desorganizado.
• "Pair programming": dois programadores num computador.
• "Code smell": cheiro a código mau.
• "Greenfield project": projecto novo do zero.
• "Legacy code": código antigo difícil de mudar.

3. Reading: documentação

3.1 Estrutura típica de docs

Páginas comuns:

• Overview / Introduction: visão geral do projecto.
• Getting Started / Quick Start: começar em 5 minutos.
• Installation: como instalar.
• Configuration: configurações.
• Tutorial / Walkthrough: tutorial guiado.
• API Reference: documentação detalhada de cada método.
• Examples: exemplos práticos.
• FAQ: perguntas frequentes.
• Troubleshooting: resolução de problemas.
• Changelog: histórico de versões.
• Contributing: como contribuir.
• License: licença.

3.2 Skim vs Scan

Skim (passar olhos rapidamente):

• Para visão geral.
• Ler títulos, subtítulos, primeira frase de cada parágrafo.
• Decidir se vale aprofundar.

Scan (procurar palavra específica):

• Para encontrar info concreta.
• Usar Ctrl+F (find).
• Saltar entre secções relevantes.

Standard tech:

• 80% do tempo a scan (encontrar exemplo específico, sintaxe).
• 20% do tempo a read carefully (entender conceito complexo).

3.3 Comentários em código

Inglês comum em código:

// TODO: refactor this function for clarity
// FIXME: handle edge case when array is empty
// HACK: temporary workaround until API is updated
// NOTE: this assumes timezone is UTC
// XXX: warning - this is performance-critical

/**
 * Calculates the total price including tax.
 * @param {number} basePrice - The base price.
 * @param {number} taxRate - Tax rate as decimal (e.g., 0.23 for 23%).
 * @returns {number} The total price including tax.
 */
function calculateTotal(basePrice, taxRate) {
    return basePrice * (1 + taxRate);
}

3.4 Stack Overflow

Estrutura:

• Question: pergunta com contexto, código de exemplo, o que tentou.
• Tags: identificam tecnologias (#python, #javascript, #react).
• Answers: respostas dos utilizadores.
• Accepted answer: resposta marcada como correcta pelo autor da pergunta (verde).
• Votes: upvotes/downvotes.

Estratégia de leitura:

1. Ler pergunta completa (com contexto).
2. Ver accepted answer primeiro.
3. Ler top voted answers (podem ter melhor solução).
4. Ler comments em respostas (clarificações).

Bom pergunta:

• Título descritivo.
• Código mínimo reprodutível.
• Erro completo (não apenas "não funciona").
• O que já tentou.
• Versões usadas.

3.5 Error messages

Erros comuns e seus significados:

• SyntaxError: invalid syntax: erro de sintaxe — código mal escrito.
• NameError: name 'x' is not defined: variável não definida.
• TypeError: unsupported operand type(s): operação inválida entre tipos.
• ValueError: invalid literal for int(): valor inválido.
• IndexError: list index out of range: índice fora dos limites.
• KeyError: 'key': chave inexistente em dicionário.
• AttributeError: 'X' object has no attribute 'y': método/propriedade inexistente.
• ImportError: No module named 'X': módulo não encontrado.
• FileNotFoundError: ficheiro não existe.
• PermissionError: sem permissões.

4. Writing: emails, docs, commits

4.1 Email profissional

Estrutura:

Subject: [Specific topic with context]

Dear [Name] / Hi [Name],

[Opening line - context or pleasantry]

[Main content - clear and structured]
[Use bullet points for lists]

[Call to action - what you need from them]

[Closing line]

Best regards / Kind regards,
[Your name]
[Title]
[Company]
[Contact]

Phrases úteis:

• Opening:
• "I hope this email finds you well."
• "Thank you for your previous email."

• "I'm reaching out regarding..."

• Stating purpose:

• "I am writing to inform you that..."
• "I would like to discuss..."

• "Could you please...?"

• Requesting:

• "Would it be possible to...?"
• "Could you please send me...?"

• "I would appreciate if you could..."

• Offering help:

• "Please let me know if you need any clarification."
• "I am happy to assist with..."

• "Feel free to contact me if..."

• Closing:

• "Thank you for your time and consideration."
• "Looking forward to your response."
• "Please let me know if you have any questions."

4.2 Bug report

Template standard:

Title: [BUG] [Concise description of the issue]

## Environment
- App version: 2.4.1
- Browser: Chrome 118.0 on macOS 14.0
- Device: MacBook Pro M1
- User: test-user@example.com

## Steps to reproduce
1. Navigate to login page
2. Enter valid credentials
3. Click "Sign in" button
4. Observe error message

## Expected behavior
User should be successfully logged in and redirected to dashboard.

## Actual behavior
Error message displayed: "Internal Server Error"
User remains on login page.

## Screenshots
[Attach screenshots showing the error]

## Logs

2026-05-22 14:32:15 ERROR [auth-service] Database connection timeout 2026-05-22 14:32:15 ERROR [auth-service] Failed to authenticate user

## Severity
- [ ] Critical (blocks all users)
- [x] High (blocks core feature)
- [ ] Medium (workaround available)
- [ ] Low (minor inconvenience)

## Additional notes
This bug appeared after the latest deployment on May 20.

4.3 Commit messages

Conventional Commits format:

<type>(<scope>): <subject>

<body>

<footer>

Types comuns:

• feat: new feature.
• fix: bug fix.
• docs: documentation only.
• style: formatting (no logic change).
• refactor: code refactoring (no functional change).
• test: adding tests.
• chore: maintenance (dependencies, build).
• perf: performance improvement.

Exemplos:

feat(auth): add multi-factor authentication

Implement TOTP-based MFA using Google Authenticator.
Users can now enable MFA in their profile settings.

Closes #234

fix(checkout): correct tax calculation for EU customers

Tax was being calculated using US rates for EU orders.
Now uses country-specific rates from tax service.

Fixes #567

docs(readme): update installation instructions

Add Windows-specific setup steps.
Mention Python 3.10+ requirement.

4.4 README

Estrutura típica:

# Project Name

[![Build Status](badge)] [![License](badge)]

Brief description of what the project does and why it's useful.

## Features

- Feature 1
- Feature 2
- Feature 3

## Installation

```bash
npm install my-package

Quick Start

const myPackage = require('my-package');
myPackage.doSomething();

Documentation

For detailed documentation, see docs/.

Contributing

See CONTRIBUTING.md.

License

MIT — see LICENSE.

### 4.5 Technical writing principles

- **Clear and concise**: short sentences, simple words.
- **Active voice** > passive ("The function returns X" > "X is returned by the function").
- **Present tense** for documentation ("The API accepts JSON").
- **Imperative** for instructions ("Click the button" not "You should click").
- **Examples > explanations**: show, don't just tell.
- **Consistent terminology**: same term for same concept.

---

## 5. Listening

### 5.1 Sources

**YouTube channels**:

- **freeCodeCamp**: long-form tutorials.
- **Fireship**: short, fun, fast (great for vocabulary practice).
- **Traversy Media**: friendly tutorials.
- **The Net Ninja**: beginner-friendly.
- **TechWorld with Nana**: DevOps focused.

**Podcasts**:

- **Syntax.fm**: web dev (Scott Tolinski, Wes Bos).
- **Software Engineering Daily**.
- **Changelog**.
- **Lex Fridman Podcast**: AI/ML conversations (long form).

**Conferences**:

- **TED Talks**: ted.com.
- **InfoQ**: enterprise tech.
- **YouTube channels** of major conferences (Google I/O, AWS re:Invent, KubeCon).

### 5.2 Listening strategies

**Active listening**:
- **Subtitles on** (English, not translated).
- **Reduced speed** (0.75×) if too fast.
- **Pause** to take notes.
- **Repeat** sections you didn't understand.

**Passive listening**:
- While commuting, exercising, doing chores.
- Don't try to understand everything.
- Goal: get used to sounds, rhythm, accent.

**Progress steps**:
1. **Subtitles + speed 0.75×**.
2. **Subtitles + speed 1.0×**.
3. **No subtitles + speed 1.0×**.
4. **Speed 1.25× or 1.5×** (challenging).

### 5.3 Accents

**Main accents to expect in IT**:

- **American English**: most common in tech (Silicon Valley).
- **British English**: formal, BBC.
- **Indian English**: many Indian engineers in tech. Rhythm different.
- **Australian / Kiwi**: occasional.
- **Other European**: German, French, Eastern European.
- **Asian**: Chinese, Japanese, Korean accents.

**Strategy**: expose yourself to **as many accents as possible**. Don't fixate on one.

### 5.4 Common challenges

- **Speed**: native speakers talk fast.
- **Idioms**: hard to catch in real-time.
- **Connected speech**: "want to" → "wanna", "going to" → "gonna".
- **Jargon**: tech-specific terms.
- **Accents**: regional variations.

**Solution**: time + exposure. There's no shortcut.

---

## 6. Speaking

### 6.1 Daily standup

**Structure**:

Yesterday: I worked on [task]. I [accomplished what]. Today: I will [continue/start] [task]. Blockers: I'm blocked on [issue]. I need [resource/help]. ```

Example:

"Yesterday I worked on the user authentication API. I implemented the login endpoint and started on the registration endpoint.

Today I'll finish the registration endpoint and start working on the password reset functionality.

I'm blocked on the email sending — I need access to the SendGrid API key."

6.2 Meetings

Useful phrases:

Starting a meeting:

• "Thank you all for joining."
• "Let's get started."
• "Today we'll be discussing X, Y, and Z."

Agreeing:

• "I agree with [name]."
• "That's a great point."
• "I see your point."
• "Absolutely."

Disagreeing politely:

• "I see it differently."
• "I'd like to push back on that."
• "I'm not sure I agree, because..."
• "Have we considered...?"

Asking for clarification:

• "Could you elaborate on that?"
• "I'm not sure I follow."
• "What do you mean by X?"
• "Can you give an example?"

Summarizing:

• "So, to summarize..."
• "Let me recap what we've discussed."
• "The main takeaways are..."

Action items:

• "Action items: ..."
• "Who will own this?"
• "When is this due?"

Ending:

• "Let's wrap up."
• "We'll continue this discussion in the next meeting."
• "Thank you all for your time."

6.3 Asking for help

Don't say: "I don't know how to do X."

Do say: "I'm working on X and have been trying approach A and B. I'm running into issue Y. Have you encountered this before?"

Difference: shows you've tried, makes it easier to help.

6.4 Giving updates

Format:

"Quick update on [project]: we've completed [milestone]. Next, we're working on [next step]. Expected delivery date is [date]. Any concerns or feedback?"

Concise + specific + invites feedback.

7. Interview English

7.1 Common questions

About yourself:

• "Tell me about yourself."
• "Walk me through your CV."
• "What's your background?"

Motivation:

• "Why do you want this job?"
• "Why our company?"
• "What attracted you to this role?"

Strengths/weaknesses:

• "What are your strengths?"
• "What is your biggest weakness?"
• "What do you struggle with?"

Past experience:

• "Tell me about a challenging project."
• "Describe a time you failed."
• "Tell me about a conflict you resolved."

Future:

• "Where do you see yourself in 5 years?"
• "What are your career goals?"

Why us:

• "Why should we hire you?"
• "What can you bring to the team?"

7.2 STAR method

For behavioral questions:

• Situation: set the context.
• Task: what was your responsibility.
• Action: what you specifically did.
• Result: outcome and what you learned.

Example:

"[S] In my previous role at Company X, our team had to deliver a critical feature in 2 weeks.

[T] I was responsible for the backend API.

[A] I broke down the work into 5 smaller tasks, identified dependencies, and proposed a parallelized approach. I worked closely with the frontend team to align on the contract.

[R] We delivered on time, with 95% test coverage. The feature is still in production today, used by 10,000 daily users. I learned the value of clear API contracts early in the project."

7.3 Technical interview

Common formats:

1. Coding interview (LeetCode-style):

• Solve algorithm problem on whiteboard or shared editor.
• 30-60 minutes.

2. System design (mid/senior):

• Design an architecture (e.g., "Design Twitter").
• Discuss trade-offs.
• 45-60 minutes.

3. Behavioral (cultural fit):

• STAR-style questions.
• Past projects, teamwork, leadership.

Tips for technical:

• Think out loud:
• "First, let me make sure I understand the problem..."
• "I'm considering two approaches: brute force and optimized..."

• "The time complexity is O(n log n) because..."

• Ask clarifying questions:

• "What's the size of the input?"
• "Are there any constraints on memory?"

• "Can the input contain duplicates?"

• Don't panic if stuck:

• "Let me think for a moment."
• "Let me try a different approach."
• "Can I work through a small example?"

7.4 Salary negotiation

Useful phrases:

• "Based on my research, the market rate for this role is X."
• "I was hoping for Y, considering my experience with Z."
• "Is there flexibility on the base salary?"
• "What other components are available — bonus, stock, benefits?"

Don't be afraid to negotiate: companies expect it.

8. Resources

8.1 Online learning

Free:

• Duolingo: gamified, good for daily practice.
• BBC Learning English: bbc.co.uk/learningenglish.
• British Council: learnenglish.britishcouncil.org.
• Cambridge English: cambridgeenglish.org.
• YouTube channels: BBC Learning English, EnglishClass101.

Paid:

• italki: 1-on-1 lessons with native teachers (~10-30 €/hour).
• Babbel: structured courses.
• Preply: tutoring marketplace.

8.2 Reading

• Hacker News: news.ycombinator.com — tech news in English.
• Medium / Dev.to: technical articles.
• Newsletters: TLDR, ByteByteGo.
• Books:
• "Clean Code" — Robert C. Martin (technical English standard).
• "The Pragmatic Programmer" — Hunt & Thomas.
• "Designing Data-Intensive Applications" — Kleppmann.

8.3 Practice

• Mock interviews: pramp.com (free), interviewing.io.
• Toastmasters: oratory practice (chapters in Portugal).
• Conversation partners: Tandem, HelloTalk (apps).
• Meetups: search "English meetup Lisboa/Porto".

8.4 Certification

If you want formal proof:

• TOEFL: American English, university-focused. ~250 €.
• IELTS: British English, work/study. ~250 €.
• Cambridge:
• FCE (B2).
• CAE (C1).
• CPE (C2).
• Linguaskill: Cambridge, computer-based. ~100 €.

For IT jobs: usually no formal cert needed if you can speak well in interview. But cert helps if you need visa or formal proof.

8.5 Immersion daily

Easy daily habits:

• Phone in English: forces daily exposure.
• Email signature in English: practice writing.
• One YouTube video / day in English.
• One technical article / day in English.
• Notes in English.
• Code comments in English (always).

More committed:

• Series: watch in English with English subtitles.
• Books: read 1 technical book in English / year minimum.
• Conversation: find a partner (online if needed).
• Trip: visit English-speaking country (immersion).

8.6 Common mistakes by Portuguese speakers

• "He have" instead of "He has" (3rd person singular).
• "I am agree" instead of "I agree".
• "Make a question" instead of "Ask a question".
• "Take a doubt" instead of "Have a doubt" or "Have a question".
• "Realize" can mean "perceber" but in English usually means "tornar real" — be careful.
• "Actually" means "in fact", not "atualmente" (which is "currently" or "nowadays").
• "Pretend" means "fingir", not "pretender" (which is "intend" or "plan").
• "Eventually" means "no fim" or "no final", not "eventualmente" (which is "possibly").

These false friends are frequent — be aware.

Apêndice A · Falsos amigos PT-EN

Apêndice B · Acrónimos IT essenciais

• API: Application Programming Interface.
• CRUD: Create, Read, Update, Delete.
• SQL: Structured Query Language.
• HTML: HyperText Markup Language.
• CSS: Cascading Style Sheets.
• HTTP: HyperText Transfer Protocol.
• JSON: JavaScript Object Notation.
• XML: eXtensible Markup Language.
• URL: Uniform Resource Locator.
• MVP: Minimum Viable Product.
• POC: Proof of Concept.
• KPI: Key Performance Indicator.
• ROI: Return on Investment.
• B2B / B2C: Business-to-Business / Business-to-Consumer.
• SaaS / PaaS / IaaS: Software/Platform/Infrastructure as a Service.
• AI / ML: Artificial Intelligence / Machine Learning.
• NLP: Natural Language Processing.
• CI/CD: Continuous Integration / Continuous Deployment.
• TDD: Test-Driven Development.
• DRY / KISS / YAGNI: Don't Repeat Yourself / Keep It Simple, Stupid / You Aren't Gonna Need It.
• MVP: Model-View-Presenter.
• MVC: Model-View-Controller.
• OOP: Object-Oriented Programming.

Apêndice C · Plano de estudo recomendado (1 ano)

Mês 1-3 (foundation):

• 15 min/dia Duolingo.
• 1 vídeo YouTube/dia (tech, com legendas EN).
• Telefone em inglês.

Mês 4-6 (intermediate):

• 30 min/dia: alternar entre listening (podcasts), reading (artigos), writing (journal).
• Aulas 1×/semana com tutor online (italki).
• Toastmasters mensal.

Mês 7-9 (upper intermediate):

• Ler 1 livro técnico em inglês.
• Watch 1 série inteira sem legendas.
• Conversação em meetups.
• Escrever blog em inglês (mesmo curto).

Mês 10-12 (advanced):

• Aulas particulares 2×/semana se possível.
• Apresentação técnica em inglês (gravada).
• Fazer mock interviews.
• Considerar certificação (FCE/CAE).

Resultado esperado: B1 → B2+ em 1 ano com esforço diário.