Mundarija (27)
- 1. Dars nomi, maqsad va motivatsiya
- 2. Avvalgi darslardan takror (spiral)
- 3. Texnik ingliz — to'liq
- 3.1. Asosiy dasturlash atamalari
- 3.2. Git / GitHub ingliz
- 3.3. Hujjat o'qish (documentation) — naqshlar
- 3.4. Xato xabarlari (error messages) o'qish
- 3.5. Jamoa muloqoti / standup iboralari
- 3.6. Texnik intervyu iboralari
- 3.7. Fe'l + ot kollokatsiyalari (texnik)
- 3.8. Texnik ingliz uslubi — nega aniq va rasmiy
- 3.9. Akademik so'z boyligi (Academic Word List — kirish)
- 3.10. Jarayon va instruksiya tili (bosqichlar)
- 3.11. Ta'rif berish (definitions)
- 3.12. Grafik va ma'lumot tavsifi (IELTS Task 1 — kirish)
- 3.13. Rasmiy so'z tanlash (get → obtain)
- 3.14. Soha lug'ati (texnologiya va fan — asosiy so'zlar)
- 4. Misollar (kontekst bo'yicha)
- 5. Talaffuz bo'limi
- 6. So'z boyligi (Anki) — texnik atamalar
- 7. O'qish matni va dialog (input)
- 8. O'zbekcha-inglizcha tipik xatolar
- 9. Mashqlar
- 10. Production drill + model javoblar
- 11. Javoblar kaliti
- 12. Xulosa va keyingi dars
- Manba
Texnik ingliz tili — dasturlash va IT atamalari: kirish (B1, 34-dars)
B1 — O'RTA · 34-dars · maxsus yo'nalish (dasturchi/IT uchun)
1. Dars nomi, maqsad va motivatsiya
Bu darsda texnik ingliz tilining asosini o'rganasiz — dasturlash va IT atamalari, hujjat (documentation) va xato xabarlari (error messages) o'qish, git/GitHub tili va texnik intervyu iboralari. Bu — masofaviy dasturchi ishi uchun hal qiluvchi (ko'pchilik o'quvchilar uchun asosiy maqsad).
The function returns a value. (Funksiya qiymat qaytaradi.) I'll submit a pull request. (Pull request yuboraman.) The build failed because of a bug. (Build xatolik tufayli barbod bo'ldi.) Can you review my code? (Kodimni ko'rib bera olasizmi?)
Real hayotda nega hal qiluvchi:
- Masofaviy ish: xalqaro jamoa, mijoz, hujjat — hammasi inglizcha.
- Hujjat o'qish: har bir kutubxona/framework hujjati inglizda — tushunish shart.
- Intervyu: texnik suhbat, code review, jamoa muloqoti — inglizcha.
Asosiy tushuncha — texnik ingliz = aniq + sodda: texnik til murakkab grammatika emas — u aniq, sodda, takrorlanuvchi. Asosiy — atamalar (vocabulary) va standart iboralar ("the function takes a parameter", "it throws an error"). Hujjat asosan Present Simple (qanday ishlaydi) va imperative (ko'rsatma) da yoziladi. Atamalarni va naqshlarni yodlasangiz, texnik inglizcha — oson.
2. Avvalgi darslardan takror (spiral)
- B1-13,14 (passive): is called, is stored — texnik tilda juda ko'p.
- A1-21 (imperative): Install, Run, Click — hujjat ko'rsatmalari.
- B1-29 (articles): texnik yozuvda artikl.
- B1-1 (present perfect): I've deployed, the build has failed.
- Tez mashq: atama: bug (?), deploy (?), commit (?) (xatolik, joylashtirmoq, saqlash/o'zgartirish).
3. Texnik ingliz — to'liq
3.1. Asosiy dasturlash atamalari
KOD: code, source code, line of code, syntax, indentation, comment
TUZILMA: function, method, variable, parameter, argument, class, object, array, loop, condition
XATO: bug, error, exception, crash, fix, debug, troubleshoot, stack trace
JARAYON: run, execute, compile, build, deploy, test, refactor, optimize
MA'LUMOT: database, query, server, API, request, response, endpoint
VOSITA: framework, library, package, dependency, repository (repo), IDEThere's a bug in this function. — Bu funksiyada xatolik bor.
I need to fix this error. — Bu xatoni tuzatishim kerak.
Let's deploy the new version. — Yangi versiyani joylashtiramiz.
The API returns a JSON response. — API JSON javob qaytaradi.3.2. Git / GitHub ingliz
clone — nusxa olmoq: Clone the repository.
commit — o'zgarishni saqlamoq: Commit your changes with a clear message.
push / pull — yubormoq / olmoq: Push to the main branch. / Pull the latest changes.
branch — tarmoq: Create a new branch for this feature.
merge — birlashtirmoq: Merge the branch into main.
pull request (PR) — o'zgarish so'rovi: I opened a pull request.
review — ko'rib chiqmoq: Could you review my PR?
conflict — to'qnashuv: There's a merge conflict.I've pushed my changes to a new branch. Could you review the pull request?
— O'zgarishlarimni yangi tarmoqqa yubordim. Pull request'ni ko'rib bera olasizmi?3.3. Hujjat o'qish (documentation) — naqshlar
Hujjat asosan Present Simple (qanday ishlaydi) va passive/imperative:
"The function returns a string." — Funksiya satr qaytaradi. (Present Simple)
"This method takes two parameters." — Bu metod ikki parametr oladi.
"It throws an error if the input is invalid." — Kiritma noto'g'ri bo'lsa, xato beradi.
"The data is stored in the database." — Ma'lumot bazada saqlanadi. (passive)
"Install the package using npm." — Paketni npm orqali o'rnating. (imperative)
"Make sure you have Node.js installed." — Node.js o'rnatilganiga ishonch hosil qiling.Naqshlar: "X returns Y", "X takes a parameter", "it throws an error", "X is called when…". Bularni butun ibora sifatida yodlang.
3.4. Xato xabarlari (error messages) o'qish
"undefined is not a function" — undefined funksiya emas
"cannot read property 'x' of null" — null'ning 'x' xususiyatini o'qib bo'lmaydi
"unexpected token" — kutilmagan belgi
"module not found" — modul topilmadi
"permission denied" — ruxsat rad etildi
"connection timed out" — ulanish vaqti tugadi
"syntax error" — sintaksis xatosiXato xabarlari — qisqa, aniq inglizcha. Kalit so'zlar: not found, undefined, failed, invalid, missing, expected, denied. Ularni tanib olsangiz, muammoni tez topasiz.
3.5. Jamoa muloqoti / standup iboralari
"What did you work on yesterday?" — Kecha nima ustida ishladingiz?
"I'm working on the login feature." — Login funksiyasi ustida ishlayapman.
"I'm blocked by a dependency issue." — Dependency muammosi tufayli to'xtab qoldim.
"It's almost done. I just need to test it." — Deyarli tayyor. Faqat test qilishim kerak.
"Can you give me a hand with this?" — Bunga yordam bera olasizmi?
"Let's pair on this." — Buni birga (pair) qilamiz.
"I'll take care of it." — Men hal qilaman.
"LGTM" (Looks good to me) — Menimcha yaxshi (kod tasdig'i).3.6. Texnik intervyu iboralari
"Can you walk me through your solution?" — Yechimingizni tushuntirib bera olasizmi?
"What's the time complexity?" — Vaqt murakkabligi qanday?
"I would approach this by..." — Men bunga ... orqali yondashardim.
"Let me think out loud." — Ovoz chiqarib o'ylab ko'ray.
"This is an edge case." — Bu — chekka holat.
"Could you clarify the requirements?" — Talablarni aniqlashtira olasizmi?
"I have experience with React and Node." — React va Node bilan tajribam bor. (B1-1)3.7. Fe'l + ot kollokatsiyalari (texnik)
write code, fix a bug, run a test, deploy an app, merge a branch,
raise an issue, review a PR, refactor the code, ship a feature, roll back a change3.8. Texnik ingliz uslubi — nega aniq va rasmiy
Texnik ingliz faqat dasturlash emas — u fan, muhandislik va hujjatning umumiy uslubi. Adabiy tildan farqli ravishda, uning uch belgisi bor:
- Aniqlik (precision): har bir so'z bitta ma'noda. "Chiroyli, ta'sirchan" so'zlar emas — faqat faktlar. Bir tushuncha uchun bir atama ishlatiladi (bir joyda function, keyin procedure deb chalkashtirilmaydi).
- Rasmiylik (formality): so'zlashuv iboralari (gonna, kinda, stuff, a lot of) ishlatilmaydi; ularning rasmiy varianti (going to, rather, items, many) qo'llaniladi.
- Shaxssizlik (impersonality): "men qildim" o'rniga passive yoki shaxssiz shakl: "The test was run" (kim qilgani muhim emas, natija muhim).
Oddiy (so'zlashuv): I got the data and it works fine.
Texnik (rasmiy): The data is obtained and processed correctly.Bog'lanish: shaxssiz passive — B1-13,14 da o'rgangansiz (is stored, is called). Texnik va ilmiy ingliz — o'sha passive-ning eng ko'p ishlatiladigan joyi: matn diqqatni odamdan emas, jarayon va natijadan olib qolmaydi.
3.9. Akademik so'z boyligi (Academic Word List — kirish)
Fan va texnika matnlarida bir xil "akademik" so'zlar qayta-qayta uchraydi. Ular birgalikda Academic Word List (AWL) deb ataladi va deyarli har qanday sohada (dasturlash, tibbiyot, iqtisod, muhandislik) kerak bo'ladi. Eng asosiy 9 tasi:
analyse — tahlil qilmoq: We analyse the results.
data — ma'lumot(lar): The data show a clear pattern.
factor — omil: Cost is an important factor.
method — usul: This method is faster than the old one.
process — jarayon: The process takes two steps.
research — tadqiqot: Recent research confirms this.
significant — muhim/sezilarli: There is a significant difference.
require — talab qilmoq: The task requires more memory.
occur — yuz bermoq: An error occurs when the input is empty.Diqqat (o'zbek o'quvchi uchun): research — sanalmaydigan ot: "a research" EMAS, balki research yoki a study deyiladi. data — rasmiy fanda ko'plik: the data are/show. Bu so'zlarni bilib olsangiz, istalgan texnik matnning "skeleti" tushunarli bo'ladi.
3.10. Jarayon va instruksiya tili (bosqichlar)
Har qanday texnik ko'rsatma — bosqichlar ketma-ketligi. Ularni bog'lovchilar bilan tartiblaymiz:
First, install the dependencies. — Avval, bog'liqliklarni o'rnating.
Then, run the build. — So'ng, build'ni ishga tushiring.
After that, start the server. — Shundan keyin, serverni ishga tushiring.
Finally, open the app in the browser. — Nihoyat, ilovani brauzerda oching.Ko'rsatma berganda — imperative (Install…, Run…, A1-21). Jarayonni tasvirlaganda (kim qilgani muhim emas) — passive Present Simple (13-dars):
The file is compiled, and the output is saved. — Fayl kompilyatsiya qilinadi va natija saqlanadi.
The sample is heated to 100 degrees. — Namuna 100 darajagacha qizdiriladi.
The results are recorded in a table. — Natijalar jadvalga yoziladi.Naqsh: ko'rsatma = First… Then… Finally + imperative. Ilmiy jarayon = passive (is compiled, is heated, is recorded). Ikkisini aralashtirmang.
3.11. Ta'rif berish (definitions)
Texnik va ilmiy matnda tez-tez yangi tushunchaga ta'rif beriladi. Uch asosiy naqsh bor — ularni tayyor qolip sifatida yodlang:
A variable is a type of container for data. — O'zgaruvchi — ma'lumot uchun bir tur idish.
"API" refers to a way for programs to communicate. — "API" dasturlarning o'zaro muloqot usulini bildiradi.
Latency is defined as the delay before a response. — Kechikish javobdan oldingi to'xtalish sifatida ta'riflanadi.Naqsh: X is a type of Y · X refers to Y · X is defined as Y. Rasmiy ta'rifda is defined as eng "ilmiy" ohangda, refers to esa yumshoqroq izohda ishlatiladi.
3.12. Grafik va ma'lumot tavsifi (IELTS Task 1 — kirish)
Texnik hisobot va akademik ishda grafik, jadval yoki raqamlar tez-tez tavsiflanadi (IELTS Writing Task 1 ham aynan shu ko'nikma). Asosiy fe'llar — o'zgarish yo'nalishi:
increase / rise / go up — oshmoq: Sales increased in 2023.
decrease / fall / drop / go down — kamaymoq: The error rate fell sharply.
remain stable / stay the same — o'zgarmay qolmoq: Traffic remained stable.
peak / reach a peak — cho'qqiga chiqmoq: Usage peaked in July.O'zgarish tezligini ravish bilan aniqlaymiz: slightly (bir oz), gradually (asta-sekin), sharply (keskin), significantly (sezilarli).
The number of users rose sharply, then remained stable.
— Foydalanuvchilar soni keskin oshdi, so'ng o'zgarmay qoldi.Diqqat: grafik tavsifida o'tgan zamon (increased, fell) yoki umumiy Present Simple (the graph shows…) ishlatiladi. "Will" (kelasi) faqat bashorat uchun.
3.13. Rasmiy so'z tanlash (get → obtain)
Bir xil fikrni oddiy yoki rasmiy so'z bilan aytish mumkin. Texnik va akademik matn deyarli har doim rasmiyni tanlaydi:
oddiy → rasmiy
get → obtain / receive (obtain the result)
use → utilise / apply (apply the method)
help → facilitate / assist (facilitate the process)
show → demonstrate / indicate (the data indicate a rise)
start → begin / initiate (initiate the process)
enough → sufficient (sufficient memory)
a lot of → many / a large number ofYana bir rasmiylik belgisi — nominalizatsiya (fe'lni otga aylantirish): "We decided" → "The decision was made"; "They analysed the data" → "The analysis of the data showed…". Bu matnni shaxssiz va rasmiy qiladi.
3.14. Soha lug'ati (texnologiya va fan — asosiy so'zlar)
TEXNOLOGIYA: device, hardware, software, network, data, storage, interface, update, setting
FAN/O'LCHOV: experiment, result, measurement, unit, rate, average, sample, accuracy
UMUMIY: system, structure, model, feature, function, value, source, output, inputBu so'zlar ham dasturlash, ham umumiy texnika/fan matnida uchraydi — texnik inglizning "umumiy poydevori".
4. Misollar (kontekst bo'yicha)
kod: This function handles user input. / The variable stores the result.
git: I committed the fix and pushed it. / We need to resolve the conflict.
hujjat: The API accepts a POST request. / Returns null if not found.
jamoa: I'm halfway through the task. / It's ready for review.
intervyu: I'd use a hash map to optimize the lookup.
akademik: The data show a significant increase. / The method is described below.5. Talaffuz bo'limi
deploy /dɪˈplɔɪ/ "diploy" query /ˈkwɪəri/ "kwiəri" cache /kæʃ/ "kesh"
repository /rɪˈpɒzɪtri/ "ripozitri" parameter /pəˈræmɪtə/ "pəremitə"
variable /ˈveəriəbl/ "veəriəbl" asynchronous /eɪˈsɪŋkrənəs/ "eysinkrənəs"Native siri: texnik atamalar ko'pincha noto'g'ri talaffuz qilinadi — cache = "kesh" (NOT "kash/keysh"), query = "kwiəri", deploy = "diPLOY" (urg'u 2-da). Bu atamalarni to'g'ri talaffuz bilan bir necha marta takrorlang.
Topshiriq (shadowing): "Deploy the app. Review the pull request. The function returns a value. Fix the bug." ni ayting. Bu atamalar talaffuziga alohida e'tibor bering.
6. So'z boyligi (Anki) — texnik atamalar
| English | O'zbekcha | Soha |
|---|---|---|
| bug / fix | xatolik / tuzatmoq | xato |
| deploy | joylashtirmoq | jarayon |
| commit / push / pull | saqlamoq / yubormoq / olmoq | git |
| pull request (PR) | o'zgarish so'rovi | git |
| merge / branch | birlashtirmoq / tarmoq | git |
| function returns | funksiya qaytaradi | hujjat |
| throws an error | xato beradi | hujjat |
| review the code | kodni ko'rib chiqmoq | jamoa |
| I'm blocked by... | …tufayli to'xtab qoldim | jamoa |
| edge case | chekka holat | intervyu |
Tayyor iboralar (chunks):
- Could you review my PR? — kod ko'rib chiqish so'rovi.
- The build failed. — "Build barbod bo'ldi."
- It works on my machine. — (klassik dasturchi iborasi ).
- Let me push the fix. — "Tuzatmani yuboray."
- I'm on it. — "Hozir qilaman."
- It's ready for review. — "Ko'rib chiqishga tayyor."
7. O'qish matni va dialog (input)
Dialog — code review (texnik jamoa):
A: Hey, I've finished the login feature. Could you review my pull request? — Salom, login funksiyasini tugatdim. Pull request'imni ko'rib bera olasanmi?
B: Sure. Let me pull the branch first. — Albatta. Avval tarmoqni olib olay.
A: Thanks. There's one part I'm not sure about — the error handling. — Rahmat. Bir qismi haqida ishonchim yo'q — xato bilan ishlash.
B: I see. The function looks good, but it throws an error if the email is empty. — Tushundim. Funksiya yaxshi ko'rinadi, lekin email bo'sh bo'lsa, xato beradi.
A: Good catch. I'll add a check for that. — Yaxshi topding. Buning uchun tekshiruv qo'shaman.
B: Also, you have a merge conflict with the main branch. — Yana, main tarmoq bilan to'qnashuving bor.
A: Oh, I'll resolve it and push again. — Voy, hal qilib qaytadan yuboraman.
B: Great. Once it's fixed, it looks ready to deploy. LGTM. — Zo'r. Tuzatilgach, joylashtirishga tayyor ko'rinadi. Menimcha yaxshi.O'qish matni — "Reading documentation" (hujjat o'qish):
Learning to read documentation is one of the most important skills for a developer. — Hujjatni o'qishni o'rganish — dasturchi uchun eng muhim ko'nikmalardan biri.
Most documentation is written in simple, clear English. — Ko'p hujjat oddiy, aniq inglizchada yozilgan.
It usually explains what a function does, what parameters it takes, and what it returns. — Odatda funksiya nima qilishini, qanday parametr olishini va nima qaytarishini tushuntiradi.
For example: "This method accepts a string and returns its length." — Masalan: "Bu metod satr qabul qiladi va uning uzunligini qaytaradi."
When something goes wrong, the error message tells you where to look. — Biror narsa noto'g'ri ketganda, xato xabari qayerga qarashni aytadi.
Don't be afraid of English documentation — it follows the same patterns every time. — Inglizcha hujjatdan qo'rqmang — u har safar bir xil naqshlarga amal qiladi.
The more you read, the faster you understand. — Qancha ko'p o'qisangiz, shuncha tez tushunasiz.Topshiriq: matnda texnik atamalar (function, parameter, returns, error message) va passive/Present Simple naqshlarini belgilang. So'ng o'z ishingiz/loyihangiz haqida 6 gap yozing (texnik atamalar bilan: I'm working on…, I deployed…, the function…).
8. O'zbekcha-inglizcha tipik xatolar
Atama talaffuzi: cache = "kash", query = "kveri", deploy = "deploy" (noto'g'ri urg'u). cache = "kesh", query = "kwiəri", deploy = "diPLOY".
make a bug / do a commit: I made a bug. I did a commit. I fixed a bug / introduced a bug. I made a commit. (to'g'ri kollokatsiya).
Hujjatda noto'g'ri zamon: "The function will return…" (umumiy ishlash uchun). "The function returns…" (Present Simple — qanday ishlaydi).
Texnik passive xatosi: "The data store in database." "The data is stored in the database." (passive — be + V3, B1-13).
So'zma-so'z tarjima: "to throw error" (artiklsiz). "to throw an error" (artikl — B1-29).
So'zlashuv uslubi ilmiy/texnik matnda: "I got a lot of data and it's pretty good." (og'zaki: got, a lot of, pretty). "A large amount of data was obtained, and the results are satisfactory." (rasmiy: obtain, passive, so'zlashuvsiz). Texnik hisobotda og'zaki so'zlarni rasmiy so'z bilan almashtiring.
"data" bilan noto'g'ri artikl: "I made a research." "I did some research." / "I carried out a study." (research — sanalmaydigan).
9. Mashqlar
Mashq 1. Atamani mosla:
1. bug a) joylashtirmoq
2. deploy b) xatolik
3. merge c) birlashtirmoq
4. review d) ko'rib chiqmoqMashq 2. Hujjat naqshini to'ldiring:
1. The function ___ (return) a value. (Present Simple)
2. The data ___ (store) in the database. (passive)
3. It ___ (throw) an error if the input is invalid.Mashq 3. To'g'ri kollokatsiya:
1. ___ a bug (fix / make)
2. ___ a commit (make / do)
3. ___ a test (run / make)
4. ___ a pull request (open / make)Mashq 4. Xatoni to'g'rilang:
The data store in database., I made a bug., to throw error, The function will return a value. (umumiy)
Mashq 5. O'zbekchadan inglizchaga:
1. Funksiya qiymat qaytaradi. = ___
2. Bu xatoni tuzatishim kerak. = ___
3. Pull request yubordim. = ___
4. Kodimni ko'rib bera olasizmi? = ___
5. Build barbod bo'ldi. = ___Mashq 6. Og'zaki so'zni rasmiy (texnik) so'z bilan almashtiring:
1. get → ___ 2. use → ___ 3. help → ___ 4. a lot of → ___ 5. enough → ___Mashq 7. Grafik fe'lini to'ldiring (increase / decrease / remain stable / peak):
1. Sales went up. = Sales ___.
2. The error rate stayed the same. = The error rate ___.
3. Usage reached its highest point. = Usage ___.Mashq 8. Ta'rif naqshini tanlang (is a type of / refers to / is defined as):
1. A loop ___ a structure that repeats code.
2. "Bug" ___ an error in a program.10. Production drill + model javoblar
Drill A — hujjat naqshi:
"This function ___ (takes/returns) ___ ." (parametr/qiymat)Drill B — git muloqoti:
"I've ___ my changes. Could you ___ the PR?" (pushed / review)Drill C — o'z ishingiz haqida:
"I'm working on ___ ." "I use ___ (framework/til)." "Today I fixed ___ ."Model javoblar (Drill C): I'm working on a web app. I use React and Node.js. Today I fixed a bug in the login form. So'ng o'z loyihangiz/ishingiz haqida 6 texnik gap tuzing va ovoz chiqarib ayting.
11. Javoblar kaliti
Mashq 1: 1-b · 2-a · 3-c · 4-d. Mashq 2: 1. returns · 2. is stored · 3. throws. Mashq 3: 1. fix · 2. make · 3. run · 4. open. Mashq 4: The data is stored in the database. / I introduced/fixed a bug. / to throw an error. / The function returns a value. Mashq 5: 1. The function returns a value. · 2. I need to fix this error. · 3. I opened/submitted a pull request. · 4. Can you review my code? · 5. The build failed. Mashq 6: 1. obtain/receive · 2. utilise/apply · 3. facilitate/assist · 4. many / a large number of · 5. sufficient. Mashq 7: 1. increased/rose · 2. remained stable · 3. peaked. Mashq 8: 1. is a type of / is defined as · 2. refers to.
12. Xulosa va keyingi dars
Tez ma'lumotnoma:
Texnik atamalar: bug/fix, deploy, function/parameter, variable, database, API
GIT: clone, commit, push/pull, branch, merge, pull request (PR), review, conflict
HUJJAT naqshlari (Present Simple + passive):
"X returns Y" | "X takes a parameter" | "it throws an error" | "X is stored in..."
XATO xabarlari: not found, undefined, failed, invalid, denied, timed out
JAMOA: "I'm working on...", "I'm blocked by...", "ready for review", "LGTM"
kollokatsiya: fix a bug, make a commit, run a test, open a PR, review code
AKADEMIK so'zlar: analyse, data, method, process, research, significant, require, occur
RASMIY tanlov: get→obtain, use→utilise, help→facilitate, a lot of→many, enough→sufficient
TA'RIF: "X is a type of...", "X refers to...", "X is defined as..."
GRAFIK: increase/rise, decrease/fall, remain stable, peak (+ slightly/sharply)
⚠️ talaffuz (cache=kesh); to'g'ri kollokatsiya; passive (is stored)Asosiy nuqtalar:
- Texnik ingliz — aniq + sodda + takrorlanuvchi.
- Hujjat: Present Simple + passive (returns, is stored).
- Git atamalar (commit, PR, merge).
- Xato xabarlari — kalit so'zlar (not found, failed).
- To'g'ri kollokatsiya (fix a bug, run a test).
- Akademik so'z boyligi (analyse, data, method, process) va ta'rif naqshlari (X refers to…).
- Rasmiy so'z tanlash (get→obtain) va shaxssiz, passive uslub (nominalizatsiya).
Bog'lanish: texnik ingliz — masofaviy dasturchi ishi uchun hal qiluvchi ahamiyatga ega. B2 da chuqurroq (texnik suhbat, hujjat yozish). Endi B1 deyarli tugadi — so'z mavzulari (review) va B1 checkpoint test qoldi.
Keyingi dars — B1 — MAXSUS dars: So'z mavzulari (ta'lim, ish, texnologiya, atrof-muhit, media). B1 darajadagi asosiy mavzular bo'yicha lug'at to'plami — keng muloqot uchun.
Manba
"English for IT/Software Engineering" (Oxford/Cambridge ESP); MDN Web Docs (documentation style); GitHub Docs; freeCodeCamp (technical English); Stack Overflow (developer communication); Averil Coxhead, "Academic Word List" (2000, akademik so'z boyligi).
O'qiganingizni mustahkamlang
Izohlar (0)
Izoh yozish uchun kiring.
- Hozircha izoh yo'q. Birinchi bo'ling!