C1 — 19-dars: Texnik va professional ingliz (dasturchi uchun)

C1 — ILG'OR · 19-dars · (kengaytirilgan chuqurlik) · Masofaviy ish — IT/dasturchi

1. Dars nomi, maqsad va motivatsiya

Texnik ingliz — dasturchining kundalik ish tili: kod muhokamasi, code review, commit/PR yozuvi, standup, hujjat o'qish/yozish, jamoa muloqoti (Slack/GitHub). Bu — masofaviy/xorijiy IT ishning markaziy ko'nikmasi: texnik bilim birinchi shart, lekin uni inglizcha aniq yetkaza olish — odamni yollaydi yoki cheklaydi.

Bu — masofaviy IT ishga bevosita ko'nikma. Xalqaro IT jamoasi ingliz tilida ishlaydi: siz PR yozasiz, hamkasb kodini review qilasiz, standupda hisobot berasiz, bug haqida yozasiz, arxitektura muhokamasida fikr bildirasiz. Bu — kundalik. Va: ish intervyusi (C1-36) ham asosan texnik muloqot — bu dars unga bevosita tayyorlaydi.

Bu — barcha o'rgangan vositalarni (register, hedging, cohesion, phrasal verbs) IT kontekstida birlashtirish. Eng muhim tamoyil: aniqlik + qisqalik + hamkorlik ohangi.

ASOSIY tushuncha — texnik muloqot = "aniqlik + hamkorlik". IT muloqotda ikki narsa hal qiluvchi:

Element	Nima
Aniqlik (clarity)	noaniq emas — aniq muammo, aniq so'rov, aniq qadam
Hamkorlik (collaboration)	tanqid emas, birga yaxshilash ohangi (code review, PR)

Texnik aniqlik ("the function throws a null pointer on line 42") + hamkorlik ("what do you think about extracting this?") — professional dasturchi belgisi.

O'xshatish — "jarroh va hamshira". Operatsiya xonasida jarroh aniq, qisqa gapiradi: "Scalpel. Suction. BP dropping." — ortiqcha so'z yo'q, har so'z aniq. IT jamoasi ham shunday: standup, code review, bug report — aniq, qisqa, ortiqchasiz. Lekin jarrohlik jamoasi hamkorlikda ishlaydi — bir-birini qo'llab. Texnik ingliz: jarrohlik aniqligi + jamoa hamkorligi. Noaniq yoki qo'pol muloqot — "operatsiyani" buzadi.

Til-fakti: texnik ingliz soha jargoni (jargon) + umumiy professional ingliz aralashmasi. Jargon (deploy, refactor, merge, rollback, async) — xalqaro standart (tarjima qilinmaydi!); umumiy professional til ("Could you take a look at...", "I'm not sure this scales") — C1 ko'nikmasi. Ko'p o'zbek dasturchi jargon (kod) biladi, lekin muloqot (review, PR, muhokama) ingliz tilini emas — aynan shu cheklaydi. Va jargon talaffuzi muhim: cache = /kæʃ/ ("kash", "kech" emas), query = /ˈkwɪəri/, schema = /ˈskiːmə/, null = /nʌl/.

2. Avvalgi darslardan takror (spiral)

• C1-15 (professional yozish): email/hisobot — bugun IT-ga xos (PR, standup).
• C1-6 (hedging) / C1-17 (munozara): code review — nazokatli e'tiroz, arxitektura muhokamasi.
• C1-10 (phrasal verbs): IT phrasal verblar (roll out, back up, spin up).
• B2-50 (code review/standup kirish): asoslar. Bugun chuqur + C1.
• Tez mashq: "the bug appears when..." — aniqroq? (steps to reproduce). "your code is bad" nazokatli? ("I have a suggestion here...").

3. Strategiya — chuqur, to'liq tushuntirish

3.1. Code review — fikr berish (eng nozik — hamkorlik)

TANQIDNI HAMKORLIKKA AYLANTIRING (nazokat + aniqlik):
   qo'pol: "This is wrong." / "Bad code."
   professional:
     "What do you think about extracting this into a helper?" (taklif — savol bilan)
     "Nit: could we rename this for clarity?" (kichik — "nit" = nitpick)
     "This might cause a race condition — have you considered...?" (hedging C1-6)
     "I'd suggest... but happy to discuss." (taklif + ochiqlik)

DARAJALAR (qanchalik muhim):
  "Blocking:" / "Must fix:"  — birlashtirishdan oldin shart
  "Suggestion:" / "Consider:" — yaxshi bo'lardi (ixtiyoriy)
  "Nit:" / "Minor:"  — kichik (uslub, nom)
  "Question:" / "Curious:"  — tushunish uchun savol (tanqid emas)

MAQTOV ham (balans):  "Nice solution!" / "Clean approach " / "TIL — didn't know this!"

Oltin qoida: kodga (g'oyaga) e'tiroz bildiring, odamga emas (C1-17). Savol bilan taklif ("What if we...?") — buyruqdan ("Change this") yumshoqroq, hamkorlik ohangida.

3.2. Code review — fikr qabul qilish

ROZILIK:        "Good catch!" / "You're right, I'll fix that." / "Makes sense, thanks."
TUSHUNTIRISH:   "I did it this way because... but I'm open to changing it."
NOZIK E'TIROZ:  "I see your point, though I went with X for [reason]. What do you think?"
SAVOL:          "Could you clarify what you mean by...?"
RAHMAT:         "Thanks for the thorough review!" / "Appreciate the feedback."

3.3. Commit message va PR — yozuv konvensiyalari

COMMIT MESSAGE (buyruq mayli — imperative!):
   "Add user authentication" / "Fix null check in parser" / "Refactor cache layer"
   "Added..." / "Fixes..." / "I added..." (buyruq mayli: Add, Fix, not Added)
  Konvensiya: <type>: <qisqa> — "feat: add login", "fix: handle empty array"

PR (PULL REQUEST) TAVSIFI:
  Title: aniq, qisqa
  Description:
    ## What  — nima o'zgardi (qisqa)
    ## Why   — nega (kontekst/muammo)
    ## How   — qanday (yondashuv, agar nozik bo'lsa)
    ## Testing — qanday tekshirildi
  "This PR adds... / Closes #123 / Note: this depends on..."

Commit — buyruq mayli (Add, Fix, Update — "Added" emas): "agar qo'llansa, bu commit [X qiladi]". PR tavsifi — kontekst beradi (review qiluvchiga): nima, nega, qanday tekshirilgan.

3.4. Standup (agile) — kundalik hisobot

UCH SAVOL (qisqa, aniq):
1. KECHA: "Yesterday I finished the login API and started on the tests."
2. BUGUN: "Today I'll wrap up the tests and start the integration."
3. TO'SIQ (blocker): "I'm blocked on the staging deploy — waiting on DevOps."
                     / "No blockers." / "Nothing blocking me."

IBORALAR:  "I'm still working on..." / "I picked up the ticket for..."
           "It's taking longer than expected because..." / "I should have it done by..."
           "I could use a hand with..." (yordam so'rash)

Standup — qisqa (1-2 daqiqa har kishi): kecha/bugun/to'siq. Tafsilotga berilib ketmang; to'siq bo'lsa aniq ayting (kimdan/nima kutyapsiz).

3.5. Bug report / yordam so'rash — aniqlik

YAXSHI BUG REPORT (aniq, takrorlanadigan):
  - What happened: "The app crashes when I submit an empty form."
  - Steps to reproduce: "1. Open the form  2. Leave fields blank  3. Click Submit"
  - Expected vs actual: "Expected: validation error. Actual: 500 error."
  - Error/logs: "Console shows: TypeError: cannot read property 'id' of null"
  - Environment: "Chrome 120, staging"

YORDAM SO'RASH (kontekst bilan):
  "I'm running into an issue with X. I've tried Y and Z, but still getting [error].
   Any ideas?" (nima sinaganingizni ayting — "It doesn't work" emas)

"It doesn't work" — yomon: aniq emas. Steps to reproduce + error message + nima sinaganingiz — professional. Hamkasb vaqtini tejaydi, hurmat ko'rsatadi.

3.6. Arxitektura/texnik muhokama — trade-off tili

TAKLIF:        "I'd propose we go with X." / "What if we used Y instead?"
TRADE-OFF:     "X is faster, but Y is more maintainable." / "There's a trade-off between..."
EHTIYOT (hedging): "This might not scale well." / "I'm a bit concerned about performance."
ROZILIK/E'TIROZ:  "That makes sense." / "I see the appeal, but I worry about..."
QAROR:         "Let's go with X for now and revisit later." / "Let's not over-engineer this."

4. Native nozikliklari va qo'shimcha qoidalar

• "Nit:" / "TIL" / "LGTM" — IT qisqartmalar: Nit (nitpick — kichik); TIL (Today I Learned); LGTM (Looks Good To Me — tasdiq); PR (pull request); WIP (Work In Progress); PTAL (Please Take A Look); IIRC (If I Recall Correctly). Jamoa chatida keng.
• Savol bilan taklif — hamkorlik: "What do you think about...?", "Could we maybe...?", "Would it make sense to...?" — buyruqdan ("Do this") yumshoq, ochiq muloqot. Code review'da ayniqsa.
• Async muloqot (Slack/GitHub) — aniqlik + qisqalik: yozma, kontekstsiz — shuning uchun aniq bo'ling ("Re: the deploy issue — I found the cause..."). Kontekst qo'shing. Emoji/reaksiya () — tabiiy, do'stona.
• Maqtov — jamoa madaniyati: faqat tanqid emas — "Nice work!", "Great catch!", "This is really clean". Ijobiy fikr — hamkorlikni mustahkamlaydi (ayniqsa masofaviy jamoada).
• "Could you take a look?" — muloyim so'rov: review/yordam so'rashda hedging ("When you get a chance, could you...?") — talabchan emas. "PTAL" (norasmiy jamoa).
• Haddan rasmiy ham noo'rin: IT muloqot ko'pincha iliq-norasmiy ("Hey, quick q...", "Cheers!") — juda rasmiy ("Dear colleague, I hereby request...") — g'alati. Jamoa madaniyatiga moslang (odatda neytral-iliq).
• "We", "you" emas — inkluziv olmosh (native code-review siri): e'tirozni "we" (biz) bilan qadoqlash "you" dan yumshoqroq: "Could we add a guard here?" — "You forgot a guard" dan hamkorlik ohangida (aybni birovga tashlamaydi, umumiy kodga qaratadi). Native reviewer'lar "the code / this function" ham ishlatadi ("this could throw" — "your code throws" emas): fikr kodga qaratiladi, muallifga emas.
• Yumshatuvchi so'zlar (async so'rov): just, quick, maybe, a bit, when you get a chance, no rush — talabni past qiladi: "Just a quick question...", "maybe we could...", "whenever you get a chance". Ular so'rovni buyruqdan iltimosga aylantiradi (ayniqsa vaqt mintaqalari turlicha bo'lgan masofaviy jamoada — javob darhol kutilmaydi).
• Approve / Request changes / Comment (GitHub mexanikasi): review yakunida uch holat bor — Approve ("LGTM! " — birlashtirishga tayyor), Request changes ("A couple of blocking items below" — tuzatish shart), Comment (bloklamaydigan fikr, savol). "Blocking" so'zi aynan shuni bildiradi: request changes darajasidagi, birlashtirishdan oldin shart bo'lgan e'tiroz.
• Jargon talaffuzi: cache /kæʃ/, query /ˈkwɪəri/, schema /ˈskiːmə/, null /nʌl/, tuple /ˈtjuːpl/, cron /krɒn/, Linux /ˈlɪnəks/, data /ˈdeɪtə/, GIF (bahsli!). Noto'g'ri talaffuz — tushunmovchilik.

5. Ko'p misollar — zaif professional (IT)

CODE REVIEW:
  zaif: "This code is bad."
  prof: "I think this could be simpler — what about using map() here?"
COMMIT:
  zaif: "fixed stuff" / "Added new feature for login and also fixed bug"
  prof: "fix: handle null user in auth middleware"
STANDUP:
  zaif: "I did some work yesterday."
  prof: "Yesterday I completed the API endpoints; today I'm writing tests. No blockers."
BUG REPORT:
  zaif: "The login doesn't work."
  prof: "Login fails with a 401 when the email contains a '+'. Steps: ... Error: ..."
YORDAM:
  zaif: "Help, my code doesn't work!"
  prof: "I'm getting a CORS error on the API call. I've checked the headers and tried X.
         Could it be a proxy config issue?"
MUHOKAMA:
  zaif: "No, use Redis."
  prof: "Redis could work well here — it'd be faster, though it adds a dependency. Thoughts?"

6. Holat/case yechimlari

1. Code review: hamkasb kodida muammo — nazokatli ayting.

• "I think there might be an edge case here — what happens if the array is empty?" (savol + hedging, "bu xato" emas).

2. Commit message — to'g'ri shakl?

• Buyruq mayli: "Add password validation" (Added/Adding emas). Konvensiya: "feat: add password validation".

3. Standup: vazifa kechikyapti — qanday ayting?

• "The migration is taking longer than expected due to some legacy data issues. I should have it done by tomorrow." (sabab + taxminiy muddat, bahona emas).

4. Bug: "it doesn't work" deb yozdim.

• Aniq qiling: steps to reproduce + expected vs actual + error message + environment.

5. Arxitektura: hamkasb yondashuviga qo'shilmayman.

• "I see the appeal of that approach, but I'm a bit concerned about maintainability. What if we...?" (yon berish + e'tiroz + muqobil — C1-17).

6. PR review so'rash — muloyim.

• "Hey team, this is ready for review when someone gets a chance — PTAL . No rush!" (iliq, talabchan emas).

7. Kengaytirilgan lug'at + IT iboralar banki

Tayyor iboralar (IT — professional, iliq):

• Could you point me in the right direction? — To'g'ri yo'lni ko'rsata olasizmi?
• Let me sync up with the team and get back to you. — Jamoa bilan gaplashib, javob beraman.
• Just to give you some context,... — Biroz kontekst berishim uchun,...
• That's a fair point — let me think about the trade-offs. — To'g'ri fikr — trade-off'larni o'ylab ko'ray.

Native siri (masofaviy IT ish): texnik aniqlik + hamkorlik ohangi — sizni "ishlash oson" hamkasb qiladi (masofaviy jamoa eng qadrlaydigan sifat). Code review'da: tanqidni taklifga aylantiring ("What about...?"), maqtang ham ("Nice!"), nazokatli e'tiroz qiling. Standup/PR'da: aniq va qisqa. Bug'da: aniq + nima sinaganingiz. Bu — texnik mahoratingizni "ko'rinadigan" qiladi. Xalqaro jamoa kodingizni emas, muloqotingizni birinchi ko'radi.

8. Namunaviy matnlar (IT — izohli)

(A) PR DESCRIPTION:

## What This PR adds rate limiting to the public API endpoints. [nima — qisqa]

## Why We've been seeing abuse on the /search endpoint, which has caused a couple of outages. This should mitigate that. Closes #284. [nega — kontekst + issue]

## How I used a sliding-window approach with Redis. I considered a simpler in-memory solution, but it wouldn't work across multiple instances. [qanday + trade-off]

## Testing Added unit tests for the limiter and tested manually against staging. PTAL — happy to walk through the logic if helpful! [test + ochiqlik]

(B) CODE REVIEW COMMENTS:

"Nice, clean implementation overall! A few thoughts: [maqtov + balans] - Blocking: this could throw if user is null — could we add a guard? [muhim + savol] *- Suggestion: might be worth extracting this into a helper for reuse. [ixtiyoriy] *- Nit: tiny one — could we rename data to something more descriptive? [kichik] *- Question: out of curiosity, why a Map here rather than an object? [savol, tanqid emas] Happy to discuss any of these!" [ochiqlik]

(C) STANDUP:

"Morning! Yesterday I wrapped up the authentication flow and got the PR up for review. Today I'm planning to start on the password reset feature. One thing — I'm slightly blocked on the email service; I've reached out to [name] and I'm waiting to hear back. Other than that, all good!"

Tahlil: (A) PR — What/Why/How/Testing + trade-off + ochiqlik (PTAL); (B) review — maqtov + darajalangan fikr (Blocking/Suggestion/Nit/Question) + savol bilan, hamkorlik; (C) standup — kecha/bugun/to'siq, qisqa, aniq. Barchasi: aniqlik + hamkorlik + iliq professional ohang.

9. O'qish — graded matn (C1 — texnik muloqot haqida)

The other half of engineering

Ask a junior developer what makes a great engineer, and they will likely talk about algorithms, languages, and frameworks. Ask a senior one, and the answer is almost always different: communication. For beyond a certain level, the bottleneck is rarely what you can build alone — it is how well you can work with others to build something larger.

Consider the humble code review. A reviewer who writes "this is wrong" has technically done their job, yet has poisoned the interaction. One who writes "what do you think about handling this edge case?" achieves the same correction while building trust, inviting dialogue, and treating their colleague as a partner rather than a subordinate. The information is identical; the effect is worlds apart.

The same principle runs through every channel of technical work. A clear, well-structured pull request saves a reviewer an hour of confusion. A precise bug report — with steps, errors, and context — turns a frustrating guessing game into a five-minute fix. A concise standup respects everyone's time. In each case, the technical content is only half the story; the other half is the care taken in conveying it.

This is especially true of remote work, where there are no corridors, no whiteboards, no quick taps on the shoulder. Words on a screen are all you have — and they must carry not only your meaning but your tone, your intent, your goodwill. The engineers who thrive in distributed teams are not always the most brilliant coders. They are, almost invariably, the clearest communicators.

Topshiriq: Matn nima "muhandislikning ikkinchi yarmi" deydi? Nega "this is wrong" va "what do you think about...?" bir xil ma'lumot, lekin boshqacha ta'sir? Masofaviy ishda nega muloqot ayniqsa muhim?

10. Tipik xatolar (IT muloqot)

Asosiy tuzoq: (1) code review — taklif/savol (tanqid emas, shaxsga emas); (2) commit — buyruq mayli (Add, Fix); (3) bug — aniq (steps+error); (4) standup — qisqa; (5) muhokamada nazokatli e'tiroz; (6) iliq-professional (juda rasmiy emas); (7) jargon talaffuzi to'g'ri.

11. Chuqur tahlil — qo'shimcha faktlar va nozikliklar (masofaviy ish)

C1 dan C2 ga ko'prik.

(a) Muloqot — senior'lik belgisi. Junior dasturchi kodga e'tibor beradi; senior — muloqot va hamkorlikga. Masofaviy/xalqaro jamoada texnik mahorat "kirish bileti", lekin inglizcha aniq muloqot — o'sish va liderlik kaliti. Ko'p iqtidorli dasturchi aynan muloqotda qoladi. Bu dars — o'sha "ikkinchi yarmi".

(b) Async muloqot — yozma aniqlik. Masofaviy ish ko'pincha asinxron (Slack, GitHub, email — turli vaqt mintaqalari). Yozma muloqot kontekst talab qiladi (og'zaki "tez so'rash" yo'q): "Re: yesterday's deploy — the issue was X, fixed in PR #12". Aniq, o'zini tushuntiruvchi xabar — javob kutmasdan tushuniladi. Bu — masofaviy ishning markaziy ko'nikmasi.

(c) Code review — psixologiya. Code review — eng nozik IT muloqot: birovning mehnatini baholaysiz. Qoidalar: kodga e'tiroz (shaxsga emas), savol bilan taklif, maqtov ham, "men" tilida ("I think..." — "You should..." emas). Darajalash (Blocking/Nit) — muhimlikni aniqlaydi. Yaxshi reviewer — o'rgatadi, hamkorlik qiladi, ishonch quradi.

(d) "Disagree and commit" — professional madaniyat. Texnik muhokamada e'tiroz bildiring, lekin qaror qabul qilingach — qo'llab-quvvatlang (Amazon tamoyili): "I'd have gone with X, but Y works — let's do it." Cheksiz bahslashish emas. Fikrni ayting, eshiting, qaror qiling, davom eting. Bu — yetuk jamoa belgisi.

(e) Brevity — IT fazilati. IT muloqot qisqalikni qadrlaydi: uzun email/xabar o'qilmaydi. Standup 1-2 daqiqa; Slack xabari — bir necha jumla; PR tavsifi — aniq, ortiqchasiz. "TL;DR" (Too Long; Didn't Read — qisqacha) qo'shish — uzun xabarni umumlashtirish. Aniqlik + qisqalik.

(f) Inkluziv, do'stona ohang. Masofaviy jamoa bog'lanishni yo'qotmasligi uchun — iliq, do'stona muloqot: emoji (), maqtov, "Hope you're well", "Cheers", "". Bu sun'iy emas — masofaviy ishda "insoniy aloqa"ni saqlaydi. Faqat quruq texnik xabar — sovuq jamoa.

(g) Madaniy/til xilma-xilligi — sabr. Xalqaro jamoada hamma uchun ingliz ona tili emas (siz kabi). Shuning uchun: aniq yozing (idiom/slang ehtiyot), sabr qiling, tushunmasangiz so'rang ("Could you clarify...?"), boshqalarga ham sabr. Native bo'lmagan hamkasblar bilan — sodda, aniq til. Bu — global jamoa etiketi.

(h) Jargon — xalqaro standart. Texnik atamalar (deploy, refactor, async, endpoint, middleware) tarjima qilinmaydi — xalqaro. Lekin ularni to'g'ri ishlatish va talaffuz muhim (cache /kæʃ/, query /ˈkwɪəri/). Va: jargonni kontekstga qarab (texnik hamkasb — to'liq jargon; non-texnik/menejer — soddaroq tushuntirish).

(i) Texnik tushuntirish — auditoriyaga qarab. Bir tushunchani ikki xil tushuntirish: texnik hamkasbga (jargon, chuqur) vs menejer/mijozga (sodda, analogiya, "nega muhim"). "It's a caching issue" (texnik) vs "The system was remembering old data, which caused the slowness" (sodda). Band 9/senior — auditoriyaga moslashadi (C1-17 register).

(j) Ish intervyusiga ko'prik. Texnik ingliz — ish intervyusining (C1-36) yuragi: texnik savollar ("How would you design...?"), kod tushuntirish ("Walk me through your solution"), tajriba ("Tell me about a bug you fixed"). Bu darsdagi aniqlik + hamkorlik ohangi — intervyuda to'g'ridan-to'g'ri ko'rinadi. Keyingi dars — aynan ish intervyusi.

C2 ko'prik (masofaviy ish ustasi): texnik ingliz — "muhandislikning ikkinchi yarmi": aniqlik + hamkorlik + iliq professional ohang. C2 da siz code review, PR, standup, bug report, arxitektura muhokamasini tabiiy va ta'sirli qilasiz — texnik mahoratingizni "ko'rinadigan" qilasiz. Xalqaro jamoa sizni "ishlash oson, aniq muloqot qiladigan" hamkasb sifatida qadrlaydi — bu masofaviy ish va o'sishning kaliti. Texnik ingliz + professional yozuv + Speaking — ish arsenali to'liq. Keyingi dars — ish intervyusi (masofaviy IT ishning cho'qqisi).

12. Mashqlar

A. Code review — nazokatli/hamkorlik qiling:

1. "This is wrong." 2. "Bad variable name." 3. "You forgot error handling."

B. Commit message yozing (buyruq mayli):

1. login funksiyasi qo'shildi · 2. parserda null xato tuzatildi · 3. cache qayta yozildi

C. Bug report'ni yaxshilang: "The page is broken." (steps + expected/actual + error qo'shing).

D. Standup yozing: kecha API tugatdingiz, bugun test yozasiz, deploy'da to'siq bor.

E. Nazokatli e'tiroz (muhokama): hamkasb "let's use MongoDB" dedi, siz PostgreSQL afzal ko'rasiz.

F. To'liq PR tavsifi (uy ishi): o'zingiz qilgan (yoki xayoliy) o'zgarish uchun PR yozing (What/Why/How/Testing). Yoki Wisar AI bilan code review simulyatsiyasi.

13. Amaliy topshiriq (Wisar AI bilan) — IT muloqot simulyatsiyasi

Maqsad: texnik muloqotni (code review, PR, standup, bug, muhokama) aniq va hamkorlik ohangida olib borish — masofaviy ish darajasida.

Vazifa — rol o'yini (tanlang):

• (A) Code review: Men sizga kod parchasi (yoki uning tavsifi) beraman, siz review fikri yozasiz — darajalangan (Blocking/Suggestion/Nit/Question), nazokatli, hamkorlik ohangida. Yoki teskari — men review beraman, siz javob berasiz.
• (B) Texnik muhokama: Men arxitektura savoli/qaror beraman (masalan "SQL yoki NoSQL?", "monolith yoki microservices?"), siz fikr bildirasiz — trade-off, taklif, nazokatli e'tiroz bilan. Men qarshi argument beraman, siz javob berasiz.
• (C) Standup/PR/bug: Men vaziyat beraman, siz standup/PR tavsifi/bug report yozasiz.

Quyidagilarni ko'rsating:

1. Aniqlik (aniq muammo/so'rov/qadam — noaniq emas)
2. Hamkorlik ohangi (savol bilan taklif, maqtov, kodga e'tiroz — shaxsga emas)
3. Hedging/nazokat (I think, might, what about — C1-6)
4. IT iborasi (phrasal verb, jargon — to'g'ri)
5. Qisqalik + iliq professional

Masalan (A, review): kod getUser(id) null tekshirmaydi siz: "Nice work! One thing (blocking): this could throw if getUser returns null — could we add a guard before accessing .name? Also a nit: maybe rename u to user for clarity. Let me know what you think!"

"Tayyor" mezonlari: (1) aniq; (2) hamkorlik ohangi (tanqid emas); (3) hedging; (4) IT iborasi to'g'ri; (5) qisqa + iliq; (6) muhokamada trade-off/nazokatli.

Men javobingizni texnik muloqot mezonlari (aniqlik, hamkorlik, professionallik) bo'yicha baholayman — masofaviy ish va ish intervyusiga tayyorlik nuqtai nazaridan kuchli/zaif tomonlar va maslahatlar beraman.

14. Javoblar kaliti

A: 1. "What do you think about handling this differently?" · 2. "Nit: could we give this a more descriptive name?" · 3. "Should we add error handling here, in case the call fails?"

B: 1. "Add login function" (yoki feat: add login) · 2. "Fix null check in parser" · 3. "Refactor cache layer"

C: Namuna: "The dashboard page shows a blank screen on load. Steps: 1. Log in 2. Navigate to /dashboard. Expected: data table. Actual: blank, console shows 'TypeError: cannot read property map of undefined'. Env: Chrome, staging."

D: Namuna: "Yesterday I finished the user API endpoints; today I'll write the unit tests. I'm blocked on the staging deploy — waiting on the DevOps team to fix the pipeline."

E: Namuna: "MongoDB could work, but given our data is quite relational, I'd lean towards PostgreSQL — it'd handle the joins better and we'd get strong consistency. That said, I'm open to it if we expect the schema to change a lot. What's driving the NoSQL preference?"

Tez ma'lumotnoma

TEXNIK INGLIZ = aniqlik (clarity) + hamkorlik (collaboration) + iliq professional

CODE REVIEW: taklif/savol (tanqid emas!) — "What about...?" · kodga e'tiroz (shaxsga emas)
  darajalar: Blocking/Must fix · Suggestion/Consider · Nit/Minor · Question · + maqtov!
COMMIT: BUYRUQ mayli — "Add/Fix/Refactor" (Added emas) · "feat: add login"
PR: What / Why / How / Testing + kontekst + ochiqlik (PTAL)
STANDUP: kecha / bugun / to'siq (blocker) — QISQA
BUG REPORT: what + steps to reproduce + expected vs actual + error + environment
MUHOKAMA: trade-off · taklif (What if...) · nazokatli e'tiroz (I see your point, but...)

IT iboralar: take a look · ship/deploy · roll back · spin up · run into · sort out · loop in
qisqartmalar: Nit · TIL · LGTM · PR · WIP · PTAL · TL;DR
talaffuz: cache /kæʃ/ · query /ˈkwɪəri/ · schema /ˈskiːmə/ · null /nʌl/

 "It doesn't work"  (aniq qil) · "This is bad"  (taklif qil) · "Added"  (Add)
 muloqot = muhandislikning IKKINCHI yarmi (senior belgisi) · async=aniqlik+kontekst
 masofaviy: "ishlash oson" hamkasb bo'l (aniq+hamkorlik+iliq) · auditoriyaga moslash

Bog'lanish

• Oldingi: C1-15 (professional yozish), C1-6 (hedging), C1-10 (IT phrasal verblar), C1-17 (munozara), B2-50 (code review asoslari).
• Keyingi: C1-20 / C1-36 ( ISH INTERVYUSI — texnik muloqotning cho'qqisi).
• Aloqador: masofaviy IT ish (code review/PR/standup), ish intervyusi (texnik muloqot).

Manba

The Pragmatic Programmer (muloqot boblari); Google Engineering Practices (code review); Conventional Commits spec; GitHub/GitLab hujjatlari; Docs for Developers (texnik yozuv).