B2 — TEXNIK dars: Dasturchi ingliz tili (chuqur — documentation, code review, meetings)

B2 — YUQORI O'RTA · texnik dars · (kengaytirilgan chuqurlik)

1. Dars nomi, maqsad va motivatsiya

Dasturchi uchun yakuniy maqsad ko'pincha masofaviy/xorijiy ish va intervyu bo'ladi. Texnik ingliz tili bu yo'lda eng hayotiy ko'nikma: hujjat (documentation) o'qish, kod-review yozish/o'qish (LGTM, nit, suggestion), commit/PR yozish, standup va jamoaviy uchrashuvlarda gapirish, bug va yechimni tushuntirish. Bularsiz texnik jamoada to'liq ishtirok eta olmaysiz — grammatika to'g'ri bo'lsa ham.

B1-34 da texnik ingliz tiliga kirdik; bu dars uni chuqur, real ish kontekstida rivojlantiradi. Maqsad — kod-review, agile uchrashuvlar va texnik muzokarada professional va aniq muloqot qilish. Bu — sizning B2 darajangizni to'g'ridan-to'g'ri karyeraga bog'laydi. C1-12 (ish intervyusi) ga ham ko'prik.

Real hayotda nega kerak:

• Code review: "LGTM, just a nit: could we extract this into a helper?"
• Standup: "Yesterday I fixed the auth bug; today I'm working on the API; no blockers."
• PR: "This PR refactors the login flow and adds tests."
• Debug: "It seems to be a race condition — the request fires before the state updates."

ASOSIY tushuncha — texnik ingliz = aniq fe'l + jamoa register + kontekst. Texnik muloqot uchta qatlamdan iborat:

Qatlam	Misol
Texnik so'z/fe'l	deploy, refactor, debug, scalable, dependency
Jamoa iboralari	LGTM, nit, blocker, sprint, standup, backlog
Muloqot tuzilmasi	"It seems...", "Could we...", "I'd suggest..." (B2 funksional)

O'xshatish — "jamoa tili": texnik ingliz — futbol jamoasining "maydon tili" kabi. Maxsus iboralar (offside, pass, marking) jamoa a'zolariga tez va aniq muloqotga imkon beradi. Dasturchi jamoasida — roll back, spin up, merge, blocker. Bu "qisqartmalar" tashqaridan g'alati ko'rinadi, lekin jamoa ichida — samarali. Ularni bilish = jamoaga to'liq qo'shilish.

Til-fakti: texnik ingliz xalqaro standart — git, GitHub, agile, code review terminlari butun dunyoda bir xil (inglizcha). O'zbek dasturchi sifatida siz allaqachon ko'p terminni bilasiz (commit, merge, deploy), lekin ularni gapda to'g'ri ishlatish (fe'l shakli, predlog, jamoa iboralari bilan) — bu B2 ko'nikmasi. "I will deploy" (to'g'ri) vs "I will make deploy" (kalka xato).

2. Avvalgi darslardan takror (spiral)

• B1-34 (texnik ingliz kirish): asosiy IT atamalari. Bugun code review + meetings + chuqur.
• B2-39/41 (opinion/suggesting): code review'da fikr/taklif.
• B2-9/40 (deduction/speculation): bug tahlilida (it must be / it might be).
• B2-36 (phrasal verbs): roll back, spin up, break down.
• Tez mashq: texnik fe'l: "tuzatmoq" fix/debug; "joriy etmoq" deploy; "qayta yozmoq" refactor.

3. Texnik til banki — soha bo'yicha

3.1. Asosiy texnik fe'llar (to'g'ri ishlatish)

deploy (joriy etmoq), refactor (qayta tuzmoq), debug (xatoni tuzatmoq),
implement (amalga oshirmoq), merge (birlashtirmoq), commit (saqlamoq),
roll back (orqaga qaytarmoq), break (buzmoq), fix (tuzatmoq), test,
scale (kengaytirmoq), optimise (optimallashtirmoq), integrate, configure

"We need to deploy this by Friday." / "I'll refactor the auth module."
"Let's roll back the last commit — it broke the build."

Kalka xatosi: make a deploy / do a refactor deploy it / refactor it (fe'l sifatida). make a commit — aslida OK (make a commit normal), lekin commit fe'l ham: commit the changes.

3.2. Texnik sifat/ot

SIFAT: scalable, maintainable, reusable, deprecated (eskirgan), legacy (eski),
       robust, secure, responsive, backward-compatible, lightweight
OT:    a bug, a dependency, a feature, the codebase, a workaround, an edge case,
       technical debt, a breaking change, the stack, the pipeline, an endpoint

3.3. Code review tili (juda muhim!)

TASDIQLASH:  LGTM (Looks Good To Me) / Approved / Ship it! / Nice work!
KICHIK E'TIROZ (nit): Nit: ... (arzimas) / Minor: ... / Just a small thing...
TAKLIF:      Could we...? / What if we...? / I'd suggest + -ing / Consider + -ing
             It might be cleaner to... / Have you considered...?
SAVOL:       Why did you choose...? / What's the reason for...? / Could you clarify...?
O'ZGARTIRISH SO'RASH: This needs a change before merging. / Could you address...?

"LGTM overall! Just a nit: could we rename this variable for clarity?"
"I'd suggest extracting this logic into a separate function. What do you think?"
"This could cause a memory leak — have you considered cleaning up the listener?"

Native siri — code review xushmuomalalik: to'g'ridan "This is wrong" o'rniga yumshoq: "I think there might be an issue here", "What do you think about...?", "Could we maybe...?". "nit" (nitpick) — "arzimas, lekin..." degan belgi. Bu — jamoa munosabatini saqlaydi.

4. Texnik til banki — uchrashuvlar va muzokara

4.1. Standup / agile uchrashuv

KECHA:    Yesterday, I worked on / finished / fixed / looked into...
BUGUN:    Today, I'm going to / I'll be working on / I plan to...
TO'SIQ:   I'm blocked on... / I'm stuck with... / No blockers. / I need help with...
AGILE:    sprint, backlog, ticket, story points, stand-up, retro (retrospective),
          sprint planning, the board, in progress, ready for review, done

"Yesterday I finished the login feature. Today I'll start on the dashboard.
 I'm a bit blocked on the API access — could someone help me with the credentials?"

4.2. Bug/muammoni tushuntirish (B2-9/40)

TASVIR:   There's a bug where... / The issue is that... / It throws an error when...
TAXMIN:   It seems to be / It might be / It looks like a race condition.
          My guess is that... / It's probably caused by...
QADAMLAR: To reproduce it, you... / Steps to reproduce: ... / It happens when...

4.3. Yechim taklif qilish (B2-41)

I'd suggest + -ing / We could try + -ing / One option would be to...
The cleanest fix would be to... / As a workaround, we can...
Let's roll back for now and investigate. / I'll open a ticket for this.

5. Misollar — kontekst bo'yicha

DEPLOY:    "The build passed, so I'll deploy to staging now."
REVIEW:    "LGTM! One nit: this could throw if the array is empty."
STANDUP:   "I'm blocked on the database migration — waiting on access."
DEBUG:     "It seems the request fires before the token is set — a timing issue."
PR:        "This PR adds input validation and fixes #142."
REFACTOR:  "I'd suggest breaking this 200-line function into smaller helpers."

6. Yangi so'zlar (Anki jadvali) + kollokatsiya

Texnik chunk: spin up a server, roll back a deploy, merge a PR, open/close a ticket, technical debt, code smell, ship a feature, pass/fail the build, hot fix, the happy path, peer review.

Native chunk: "the happy path" (ideal stsenariy — xato yo'q), "code smell" (yomon kod belgisi), "technical debt" (texnik qarz — keyin tuzatish kerak bo'lgan ish), "ship it" (chiqaramiz/joriy qilamiz). Bular — jamoa jargoni, native dasturchilar har kuni ishlatadi.

7. Dialog + o'qish matni

Dialog (code review + standup): A: Hey, can you review my PR when you get a chance? B: Sure. Just had a look — LGTM overall, nice clean code! A couple of nits, though. A: Go ahead. B: First, this function is a bit long — I'd suggest breaking it into smaller helpers. Second, you're not handling the edge case where the list is empty. A: Good catch. I'll refactor it and add a guard clause. B: Perfect. Also, did you run the tests? The build was failing earlier. A: Yeah, it was a flaky test — passes now. I'll push the changes and we can merge. B: Great. By the way, are you blocked on anything for standup? A: Not really. Once this is merged, I'll deploy to staging and start on the next ticket.

Tahlil: review my PR / LGTM / a couple of nits / I'd suggest breaking it / edge case / refactor / a guard clause / the build was failing / a flaky test / push / merge / blocked / standup / deploy to staging / the next ticket. — boy, autentik texnik til + B2 funksional (suggest, could).

O'qish (texnik — documentation uslubi):

README: Getting Started

This guide will walk you through setting up the project locally.

First, clone the repository and install the dependencies by running npm install. Once the installation is complete, copy the example environment file and configure your credentials.

To start the development server, run npm run dev. The app should be available at localhost:3000. If you encounter any issues, check that all required environment variables have been set.

Note: The legacy authentication module has been deprecated and will be removed in the next major release. Please migrate to the new auth flow before upgrading.

Contributions are welcome. Before submitting a pull request, make sure the tests pass and the code follows our style guide.

Topshiriq: Matndan buyruq fe'llari (imperatives) va passiv tuzilmalarni toping. Documentation nega buyruq shaklini ko'p ishlatadi?

8. Texnik ingliz tilidagi tipik xatolar (L1 transfer)

Asosiy tuzoq: (1) texnik terminlarni fe'l sifatida ishlating (deploy/refactor it, NOT make a deploy); (2) standart grammatika xatolarini (predlog, tense, artikl — B2 darslar) texnik kontekstda ham qiling; (3) explain sth to sb, depend on, agree with.

9. Chuqur tahlil — qo'shimcha faktlar va nozikliklar

B2 dan C1 (va ish intervyusi) ga ko'prik.

(a) Documentation — imperative + passive. Hujjat buyruq (Run, Install, Configure) va passiv (the file is generated, has been deprecated) ko'p ishlatadi — chunki o'quvchiga yo'riqnoma beradi va jarayonni shaxssiz tasvirlaydi. Bu — texnik yozuvning uslubi.

(b) Code review — "we" madaniyati. "Could we rename this?" (NOT "you should rename") — we aybni yumshatadi, jamoaviy ohang beradi. "Why did you...?" qattiqroq; "What's the reasoning here?" yumshoqroq.

(c) Qisqartmalar — texnik jamoa. LGTM (looks good to me), WIP (work in progress), PR (pull request), TODO, FYI, IMO (in my opinion), TBD (to be decided), AFAIK (as far as I know). Slack/PR'da keng tarqalgan.

(d) "blocked on/by". I'm blocked on the API (nimaga bog'liq) / blocked by the deploy (nima to'sdi). Standup'da blocker — eng muhim so'z (jamoa yordam berishi uchun).

(e) Past vs Present Perfect texnikada. "I fixed the bug" (tugagan, standup) vs "The bug has been fixed" (natija muhim, passiv). PR/ticket'da Present Perfect (has been added); standup'da Past (I added).

(f) "should" — kutilgan xulq. "The app should run on port 3000" (kutilyapti — B2-9). "This should work" (ehtimol, lekin 100% emas). Documentation va debugda should — "kutilgan natija".

(g) Texnik phrasal verbs (B2-36). spin up (ishga tushirmoq — server), roll back (qaytarmoq), break down (qismlarga ajratmoq), figure out (tushunib yetmoq), look into (tekshirmoq), come up with (o'ylab topmoq), fall back on (zaxiraga o'tmoq). Zarracha ma'nolari (B2-36).

(h) Commit/PR — buyruq (imperative) shakli. Commit xabari buyruq maylida yoziladi, o'tgan zamonda emas: "Fix login bug", "Add input validation" — "Fixed..." / "Fixes..." / "I fixed...". Sabab — konvensiya: xabar "agar qo'llansa, bu commit nima qiladi" degan savolga javob beradi ("Fix login bug" = "bu commit login xatosini tuzatadi"). PR sarlavhasi ham shu qoidaga bo'ysunadi. Bu — kichik, lekin xalqaro jamoada darrov ko'zga tashlanadigan professionallik belgisi.

(i) Intervyu ko'prigi (C1-12). Texnik intervyuda: tajriba (I've worked with...), muammo-yechim (I ran into..., so I...), STAR usuli (Situation-Task-Action-Result). Texnik so'z + B2 grammatika + funksional til = professional javob.

C1 / karyera ko'prigi: texnik ingliz — masofaviy/xorijiy ish maqsadi yo'lidagi markaziy ko'nikma. Kod-review, standup, PR, va texnik suhbatda professional muloqot — bu grammatika emas, amaliy jamoa tili. Bu ko'nikma to'g'ridan-to'g'ri ishga olinishingizga va jamoaga moslashishingizga ta'sir qiladi. (C1-12 — ish intervyusi — buni davom ettiradi.)

10. Mashqlar

A. To'g'ri texnik fe'lni tanlang (deploy / refactor / roll back / debug):

1. The build broke — let's ___ to the previous version.
2. This function is messy; we should ___ it.
3. Once tests pass, I'll ___ to production.
4. Let me ___ this error first.

B. Kalka xatosini tuzating:

1. I will make a deploy tonight. 2. Can you explain me this? 3. It depends from the config.

C. Code review jumlasini yumshating (xushmuomala):

1. This is wrong. 2. You should rename this. 3. Bad approach.

D. Standup javobini to'ldiring (kecha/bugun/to'siq): "Yesterday, I ___. Today, I'm going to ___. I'm blocked on ___."

E. Xatoni tuzating:

1. I fixed it and I push it.
2. open a issue
3. This code is more better.

11. Amaliy topshiriq (Wisar AI bilan)

Maqsad: real texnik vaziyatlarda professional ingliz tilida muloqot qilish.

Vazifa — rol o'yini (tanlang):

• (A) Code review: Men sizning kodingizni "PR" qilaman (matn bilan tasvirlab), siz review yozasiz — tasdiqlash + 2 ta xushmuomala taklif/e'tiroz (nit, suggestion).
• (B) Standup: Men jamoa lideriman. Siz standup yangiligingizni bering (kecha/bugun/to'siq), professional tarzda.
• (C) Bug tushuntirish: Bir bug uchraydi (men tasvirlayman), siz uni tushuntiring (taxmin + qadamlar + yechim taklifi).

Masalan (standup): "Yesterday, I finished the authentication feature and fixed a couple of edge cases. Today, I'm going to start on the API integration and write some tests. I'm slightly blocked on the staging environment — could someone help me get access?"

Kamida 5 gap, va ularda:

• 3 ta texnik so'z/chunk (deploy, refactor, edge case, blocker, roll back...)
• 1 ta xushmuomala taklif/fikr (I'd suggest / Could we / It might be cleaner to)
• 1 ta B2 grammatika (passiv / modal / conditional)

"Tayyor" mezonlari: (1) 3 texnik chunk to'g'ri (fe'l sifatida: deploy it, NOT make a deploy); (2) xushmuomala "we" ohangi (code review uchun); (3) standart grammatika to'g'ri (predlog/tense/artikl); (4) explain to / depend on / agree with to'g'ri; (5) professional, jamoaviy ohang.

Men javobingizni baholayman — texnik til, professionallik, grammatika va xatolar bo'yicha izoh beraman (real jamoaga moslik darajasida).

12. Javoblar kaliti

A: 1. roll back · 2. refactor · 3. deploy · 4. debug

B: 1. I will deploy tonight · 2. Can you explain this to me? · 3. It depends on the config

C: 1. I think there might be an issue here. · 2. Could we maybe rename this for clarity? · 3. Have you considered a different approach?

D: Namuna: "Yesterday, I fixed the login bug. Today, I'm going to work on the dashboard. I'm blocked on the API credentials."

E: 1. I fixed it and pushed it · 2. open an issue · 3. This code is better/cleaner

Tez ma'lumotnoma

TEXNIK FE'L (fe'l sifatida!): deploy, refactor, debug, merge, commit, roll back, scale
   deploy IT (NOT make a deploy) · explain sth TO sb · depend ON

CODE REVIEW: LGTM / nit: / I'd suggest + -ing / Could we...? / Have you considered...?
   "we" ohangi (NOT "you should") · yumshoq, jamoaviy

STANDUP: Yesterday I [past] · Today I'm going to [future] · I'm blocked on [blocker]
  agile: sprint, backlog, ticket, retro, PR, the board

BUG: It seems to be / It might be / It's probably caused by (B2-9/40)
DOCUMENTATION: imperative (Run, Install) + passive (has been deprecated)

QISQARTMA: LGTM, WIP, PR, TODO, FYI, IMO, TBD · chunk: spin up, technical debt, happy path

Bog'lanish

• Oldingi: B1-34 (texnik kirish), B2-9/40 (deduction), B2-36 (phrasal verbs), B2-39/41 (opinion/suggest).
• Keyingi: B2-51 (B2 CHECKPOINT TEST + IELTS 6.5-7 + C1 ko'prik).
• Aloqador: C1-12 (ish intervyusi — masofaviy ish), LUGAT B2-5 (texnologiya lug'ati).

Manba

Software engineering communication conventions (GitHub, agile); technical writing guides; "English for IT" (Cambridge); real-world code review/standup practices.