Muhammad Aziz

Summary WASM vs. JS

2024-05-31T04:45:17.410Z

- Why WASM is the future - https://www.ramotion.com/blog/is-webassembly-the-future/

- Why we chose WASM for EDGE COMPUTING (Cloud Computing) - https://thenewstack.io/why-we-chose-webassembly-wasm-for-our-edge-runtime/

- WASM vs. JS. Which one is better? - https://www.adservio.fr/post/webassembly-vs-javascript-which-is-better#el10
+ https://www.spec-india.com/blog/webassembly-vs-javascript

-------

1. Is WebAssembly the Future? - Ramotion

This article highlights WebAssembly (WASM) as a transformative technology for web development. It emphasizes WASM's ability to run code at near-native speed, its potential for high-performance applications, and its growing adoption by major tech companies. The article concludes that while WASM won't replace JavaScript, it will complement it, providing significant performance improvements for specific use cases.

2. Why We Chose WebAssembly (WASM) for Our Edge Runtime - The New Stack

Unavailable for direct review due to access restrictions.

3. WebAssembly vs JavaScript: Which is Better? - Adservio

This article provides a detailed comparison between WASM and JavaScript, discussing their respective advantages and disadvantages. It focuses on performance, security, compatibility, and use cases, concluding that the choice depends on specific project requirements. WASM excels in performance-critical applications, while JavaScript remains essential for most web development tasks due to its flexibility and widespread use.

4. WebAssembly vs JavaScript: Which One to Choose? - SPEC INDIA

This article compares WASM and JavaScript across various parameters, including performance, security, loading time, and memory management. It outlines scenarios where each technology is more suitable and highlights the importance of context in choosing the right tool. The article suggests that WASM is ideal for compute-intensive tasks, whereas JavaScript is better for general web development and UI interactions.

Conclusion

Based on the detailed analysis from the available articles, WebAssembly (WASM) is generally considered superior for performance-critical and compute-intensive applications due to its near-native execution speed and efficiency. However, JavaScript remains more versatile and essential for general web development, benefiting from a vast ecosystem of libraries, frameworks, and developer support.

Key Points

🟢 Performance: WASM offers near-native speed, making it ideal for high-performance tasks.

🔒 Security: WASM runs in a sandboxed environment, providing enhanced security.

💻 Compatibility: JavaScript is compatible with all browsers and devices, ensuring widespread use.

🔧 Use Cases: WASM is best for compute-intensive apps, while JavaScript excels in UI and general web development.

🛠️ Flexibility: JavaScript's flexibility and extensive libraries make it suitable for diverse applications.

🚀 Loading Time: WASM has faster loading times for heavy computations; JavaScript is quicker for simple tasks.

🗂️ Memory Management: JavaScript has built-in garbage collection, simplifying memory management.

👥 Community: JavaScript benefits from a large developer community and extensive documentation.

🔍 Debugging: Debugging is more straightforward in JavaScript due to its interpreted nature.

📈 Adoption: WASM is increasingly adopted for specialized use cases, complementing JavaScript.

Summary

Performance Comparison: WASM offers better performance for intensive tasks; JavaScript is better for general purposes.
Security Considerations: WASM provides a more secure environment due to its sandboxing.
Development Flexibility: JavaScript is more versatile and widely supported.
Compatibility and Ecosystem: JavaScript's compatibility across browsers and devices makes it indispensable.
Use Cases: WASM is ideal for high-performance applications; JavaScript suits most web development needs.
Memory Management: JavaScript's automatic garbage collection simplifies development.
Community Support: JavaScript has a vast ecosystem and robust community support.
Loading Times: WASM is faster for complex computations; JavaScript for simpler tasks.
Debugging and Development: JavaScript offers easier debugging due to its interpreted nature.
Future Trends: WASM's adoption is growing, especially for specialized, performance-critical tasks.

©️ Summary by ChatGPT

Flutter Uzbekistan: t.me/flutterblogs

Ayzek Azimov: Hayot, jamiyat va ijod haqida hikmatlar.

2024-01-14T16:41:31.546Z

Tarixiy jarayon shunday nuqtaga keldiki, endi insoniyatga dushmanlik qilish, yovlashish mumkin emas. Yerdagi odamlar bir-birlari bilan do‘stlashishlari lozim. Men, shu g‘oyani o‘z asarlarimda alohida ta’kidlab kelaman…

Ayzek Azimov 1920 yil 2 yanvarda Rossiyadagi Smolensk shahriga yaqin qishloqda tug‘ilgan. 1923 yili uning ota-onasi Amerika Qo‘shma Shtatlariga ko‘chib, Nyu-York shahrining Bruklin tumanida yashay boshlaganlar. 1935 yilda o‘rta maktabni tugatgan Ayzek bir yil kollejda ta’lim oladi, so‘ng o‘z shahridagi Kolumbiya universitetining kimyo fakultetiga o‘qishga kiradi. U 1939 yilda biokimyo bakalavri, 1941 yilda biokimyo magistri darajalarini yoqlaydi. U o‘z mutaxassisligi bo‘yicha bir qancha muddat ishlagach, 1945 yilda harbiy xizmatga chaqiriladi. 1946 yili uyiga qaytadi va aspiranturaga kiradi. 1948 yili uni tugatib, biokimyo doktori darajasini oladi. 1949 yildan Boston shahri universitetining meditsina fakultetida dars bera boshladi. 1951 yilda assistentlik, 1955 yilda dotsentlik unvoniga sazovor bo‘ldi. Bu maskanda, u 1958 yildan maosh olmay faoliyat yurita boshladi, sababi adabiyot jabhasida yaxshigina pul topayotgan edi. 1979 yilda unga professor unvoni berilgan.
Azimovning birinchi ““Vest”da qolib ketganlar” fantastik hikoyasi 1939 yilda “Amazing Stories” (“Ajabtovur voqealar”) jurnalida chop etildi. Shundan so‘ng, u yana o‘ntacha kichik asarlarini e’lon qildi. Lekin, 1941 yilda bosilgan “Tunning boshlanishi” hikoyasi dovrug‘ qozondi va u mashhur yozuvchiga aylandi. Aytib o‘tish joizki, 1968 yilda Amerika fantast-yozuvchilari assotsiatsiyasi ushbu asarni butun tarixdagi eng zo‘r hikoya deb tanladi. U ikki marta ekranlashtirildi ham. Shu davrdan Ayzek Azimovning ijodi gullab-yashnay boshladi. U birin-ketin robotlar haqidagi nom qozongan asarlarini yoza boshladi. Robotexnikaning uch qonunini ishlab chiqdi. Turli mukofotlarga sazovor bo‘lgan “Asoslanish” nomli romanlar turkumini boshladi. U to 1958 yilga qadar juda sermahsul ijod qildi. Shu davrdan boshlab esa ilmiy-ommabop risolalar ham bita boshladi.
Ayzek Azimov 1992 yil 6 aprelda yurak va buyrak xastaligidan vafot etdi.

Mayli, barcha kishilar bir-birlarini yaxshi ko‘rmasinlar, biroq ular orasidagi nafratni albatta yo‘qotish shart.

Ilmiy fantastika barcha odamlarning birlashishlariga yordam beruvchi soha deb qattiq ishonaman.

Bizning fantastik asarlarda ko‘tarayotgan muammolarimiz butun insoniyatning dolzarb muammolaridir…

Fantast-yozuvchi, fantastik asarlarni o‘quvchilar va fantastikaning o‘zi insoniyat taraqqiyotiga xizmat qiladilar.

Har bir odam istagan narsasiga ishonaversin. Lekin, hammani bir narsaga ishontirishga qarshiman.

Ilm-fanda ifoda etiladigan eng hayajonli so‘z “Evrika!” emas, “Mana bu ajoyib-ku!”dir.

Bahslashmaydigan ayollarni kamchiliklardan xoli deb hisoblayman.

Agar ovqat shirin bo‘lsa, u zararlidir.

Mas’uliyatlilik – og‘ir ish emas.

Kelajakda ham kitobning o‘rnini hech narsa egallay olmaydi, xuddi o‘tmishda egallay olmaganidek.

Insoniyat tarixini anglash qiyin. Kichik o‘zgarishlar katta kutilmagan natijalarga olib kelgan.

Yaratgan Zot hammamizni sevadi, lekin hech birimizga qoyil emas.

Jahli chiqib turgan odamning haqoratlaridan xafa bo‘lmang. Agar, u tinchlanib, haqoratlarini yana qaytarsa, shundagina ranjishingiz mumkin.

Hayotda turli savollarga to‘g‘ri javob topishdan qiziqarliroq ish bormi?

Balog‘atga yetganimizdan so‘ng, biz o‘zgarmaymiz, faqat yoshimiz ulg‘ayadi va ajinlarimiz ko‘payadi. Ammo, bu tashvish chekishga arzimaydi.

Agar shifokor menga besh minut umrim qolganini aytsa, vahimaga tushmayman. Faqat tezroq nimadir yozib qolishga urinaman.

Kam degani, umuman yo‘q, degandan ko‘ra yaxshiroqdir.

Odamlar o‘zlarini qo‘shnilaridan yaxshiroq, madaniyatlari qadimiyroq va yuqoriroq, boshqa yerlarga tarqalgan jamiki yaxshi jihatlar ulardan olingan, yomonliklar esa o‘zga mamlakatlarda o‘ylab topilgan, deb hisoblashga o‘rganib qolganlar.

Qarishni ham bilish kerak. Siz qariganingiz sari muloyimroq, odamlarga mehribonroq bo‘lib boring. Asosiysi, atrofdagilar siz o‘z hayotingizdan qoniqayotganingizni va rohatlanib yashayotganingizni ko‘rishsin.

Sevgi bobida o‘zingizni qiynamang. Oddiy yo‘l tuting, ya’ni sevgili qizingizdan uning chin munosabatini so‘rang-qo‘ying. Sevish va sevilish qanday yaxshi.

Jamiyat boshida turuvchi robot yaratilganda, u eng yaxshi siyosatchi bo‘lgan bo‘lardi. Robotexnika qonuniga muvofiq, u odamlarga ziyon yetkaza olmasdi, zo‘ravonlik va poraxo‘rlik qilmasdi. U qarimas va o‘lmas ekanligini bilsa ham, vaqtida iste’foga chiqardi.
Avval o‘yla, keyin indama.

– Hech qachon odamlarni tushunmaganman, – xo‘rsindi Pilorat.
– Bu juda oson. Sen avval o‘zingga boq, o‘zingni angla. Shunda boshqalarni tushuna boshlaysan. Insonlar bir-birlaridan ko‘p ham farq qilmaydilar.

Seni kim deb hisoblashlari emas, sen o‘zingni kim deb his qilishing muhimdir.

Ishonch va matonat doimo mukofotlanadi. O‘simlik poyasini ushlab, shahd bilan hamla qiling, u dushmanga to‘qmoqdek tuyuladi.

Taraqqiyot faqat ixtirolar orqaligina amalga oshadi.

Hayot – yo‘qotishlar zanjiridir. Yoshligingni, ota-onangni, do‘stlaringni, sog‘lig‘ingni va oxirida hayotning o‘zini ham yo‘qotasan.

Fantast-yozuvchilar nima qilayotganliklarini o‘zlari ham aniq bilmaydilar. Ularning ko‘pchiligi o‘z ijodlarini tirikchilik manbai deb aytishlari mumkin. Ammo, men uchun, ular – noma’lum va xavfli kelajakka boqishga jazm etayotgan insoniyat ko‘zlaridir.

Tarixchilarning ma’lumotiga ko‘ra Makedoniya shohi Filipp qo‘shni Sparta davlatiga bunday maktub yuborgan: “Agar, men yurtingizga kirsam, Spartani yer bilan bitta qilib tashlayman!” Ular bitta so‘z bilan javob qaytarganlar:“Agar!” Bu insoniyat tarixidagi eng qisqa javob xati hisoblanadi.
Bir marta sotqinlik qilgan, yana qilaberadi. Bu – hayot qonunidir.

Qadimda Misr hududida yashagan shumerlar o‘zlarining ikki ming yillik hayot jarayonlarida g‘ildirakli transportni, astronomiyani, matematikani, tijorat tashkilotlarini, g‘ishtni, undan muhtasham binolar qurishni, yozuvni ixtiro qilganlar. Ular insoniyat taraqqiyotini ixtiro qilganlar desa ham bo‘ladi. Hozir ular yo‘qlar. Troya urushiga yetti yuz yil, Rim nomli qishloqning vujudga kelishiga bir ming bir yuz yil qolganda yo‘qolganlar. Ularning mavjudligi 19 asrning oxirlarida olib borilgan arxeologik qazish ishlariga qadar noma’lum edi.

Matematikadan boshqa hech vaqoni bilmasang, buyuk matematik deb hisoblanishing mumkinmi?

Yaxshi ilmiy-fantastik asar o‘quvchini hayajonlantiradi, lekin bundan tashqari, u kelajak haqida o‘ylashga ham majbur qiladi.

Olg‘a qadam tashlash uchun doimo sabab bor. Faqat uni o‘z vaqtida topib turish lozim.

Odamlarga bir o‘yin o‘ynashga ruxsat berilgan: “Men sendan yaxshiroqman”, degan. Uni miyadan chiqarib tashlash juda mushkul.

1976 yildagi kelajak bashorati: “Televizor uydagi markaziy joyni egallaydi. Telefonlarda suhbatlashayotgan odamni ko‘rib turish uchun teleekranlar o‘rnatiladi.”

Ko‘pchilik hozir xuddi asalari inining uyalarida yashayotgan va ishlayotgandeklar. Yoritqichlar sun’iy, havo konditsioner orqali keladi. Bu odamlarni yer ostidagi shunday uyalarga ko‘chiring, farqini deyarli sezmaydilar. Bundan tashqari, yer tagining ijobiy jihatlari bor: u yerda havo issiqligi keskin o‘zgarmaydi, qishda isitish, yozda sovutish muammolari yo‘q. Transport yo‘lini yomg‘ir-u qorlar to‘sib qo‘ymaydi. Ishlab chiqarish ko‘lami ham kattalashadi, sababi kun va tunning farqi bo‘lmaganligi uchun, uni uzluksiz uyushtirish mumkin.

Ishonch aqldan ustun.

Odamzotni biologik tahlil qilsak, ayollarda qirq oltita xromosoma, erkaklarda esa qirq besh-u va yarimta (Y-xromosoma) mavjud. Xromosomalar nuqtai nazaridan qaraganda, erkak chala, yarim xromosomasi kam ayoldir. Balki, shuning uchun ayollar erkaklarga nisbatan chidamliroqlar va umrlari ham olti-yetti yilga uzoqroq.

Yerning og‘irligi qancha? Javob oddiy. Yer erkin tushish holatidadir. Bunday holatdagi har bir jismga atrofdagi gravitatsiya maydonlari to‘liq ta’sir ko‘rsatadi. Lekin, Yerga bunday ta’sirlarning natijasi yo‘q. Shuning uchun, Yerning og‘irligi yo‘q, u nolga teng.

Hayot, umuman olganda, antiqadir. Antiqalik unga to‘liq mos keluvchi yagona sifatdir.

Men hech narsaga ko‘r-ko‘rona ishonmayman. Har bir g‘oya, fikr, ma’lumot mantiqqa asoslanishi lozim. Aks holda, uning qiymati bir pul.

Inson shunday tuzilganki, u ma’lum bir yoshga yetganda, o‘limga befarq bo‘lib qoladi. U biron maqsad sari intilmaydi, o‘z ustida ishlamay qo‘yadi. Bunday holat yaxshimi yo yomonmi, lekin u hayotini yashab bo‘lganligini, o‘zi va dunyo uchun qo‘lidan kelgan barcha ishlarni qilib ulgurganligini anglaydi va bunga ko‘nikadi.

Plastmassani hayotga tatbiq qilish bilyardxonalardan boshlangan. O‘sha paytda bilyard sharlari fil suyaklaridan tayyorlangan, bu esa ularni juda qimmatlashtirgan. XIX asrning 60 — yillarida, kimki fil suyagi o‘rniga ishlatish mumkin bo‘lgan qattiq, elastik, sinib ketmaydigan, suvga chidamli va tekislasa bo‘ladigan mahsulot kashf qilsa, 10 000 dollar mukofot berilishi e’lon qilingan. Va ko‘p olimlar harakatga tushib ketganlar.

Saljuqiylarning buyuk hukmdori Malikshoh uzoqroq yashaganda yoki iste’dodli taxt vorisiga ega bo‘lganda, salb yurishlari avval boshdanoq halokatga uchrardi. Umuman olganda, salbchilarning ayrim muvaffaqiyatlari musulmonlar orasidagi kelishmovchiliklar tufayli yuz bergan.

Fransiyada, qirol Lyudovik VII davrida, shamol tegirmonlari qurilishi boshlangan. Bu g‘oya o‘sha paytlarda texnologiya sohasida ancha ilg‘or bo‘lgan Sharq mamlakatlaridan ortga qaytayotgan salbchilar tomonidan olib kelingan. Salb yurishlari natijasida, u yerlarda o‘rganilgan yangicha tafakkur va yetuk g‘oyalarning qimmati, yutqizilgan yoki yutilgan janglar ahamiyatidan ancha yuqori bo‘lgan.

“Ish mana bunday bo‘lishi mumkin edi!”, deb afsuslanishdan foyda yo‘q. Mavjud holatlar bilangina hisoblashish kerak.

Men amaldorlarning ko‘pini ko‘rdim, ammo ularning orasida baxtlilarini uchratmadim. Amal – polga qoqib qo‘yilgan kursi emas. Shuning uchun, amaldor doimo kursini kimdir siljitmasligidan ogoh bo‘lib, hamisha xavotirda ishlaydi.

Muammoni hal qilishning eng oson yo‘li – uni yo‘q deb faraz qilishdan iborat.

Olti – “a’lo sonlar”ning birinchisidir. Uning bo‘linuvchilarining yig‘indisi o‘ziga teng. Ya’ni, 6 da ular uchta: 1, 2 va 3. Ularning yig‘indisi 6 ga teng. Bunday sonlar ko‘p emas. Undan so‘ng, 28 keladi: 1+2+3+7+14=28. Keyingilari, 496 va 8128 sonlaridir. Bu narsani qadimgi matematiklar yaxshi bilishgan.

Ilmiy haqiqat qonuniy yoki noqonuniy kabi tushunchalardan tashqaridadir.

Nasroniylik qator asrlarda ilm-fanning rivojlanishiga yo‘l bermagan. Ushbu din Ioniya faylasuflari g‘oyalaridan chuqur farq qilgan. Nasroniylarning fikricha, inson uchun o‘zi ko‘rayotgan, his qilayotgan dunyo emas, “Ilohiy dunyo” muhimdir. U joyga borish uchun yo‘l ko‘rsatuvchilar cherkov namoyandalari tomonidan bitilgan “Injil” kitobidir va cherkovning o‘zining ruhiy tashviqoti ta’siridir.

Faylasuf bo‘lish uchun oliygohda o‘qish shart emas. O‘tkir aql va hayotiy tajriba kerak.

Ozod bo‘lishni istagan odamgina ozod bo‘la oladi.

Istamay olingan bilim – foydasi yo‘q bilimdir.

Hech qachon – bu juda uzoq vaqtdir.

Qo‘rquv – insonga kerak. U ehtiyotkor bo‘lishni o‘rgatadi va hayotni asraydi.

Biz qanday usulda rizq-nasiba topayotganimiz, qay holatlardan zavqlanayotganimiz, qanday g‘oyaga ishonayotganligimiz, nimalarni yaxshi, nimalarni yomon, deyayotganimiz – madaniyatdir.

Bu sayyorada birgina ishlab chiqarish rivojlangan edi, ya’ni davlat tomonidan birgina mahsulot – qonun chiqarilardi. Butun hayot jarayoni betinim boshqarilardi. Sayyorada odamlar, uy hayvonlari va parazit-tekinxo‘rlar yashardilar. Trantorda boshqacha hayot yo‘q edi.

Yomon xabarlar burgut qanotida keladi, yaxshilari esa toshbaqa oyoqlarida.

Ayni hayotdan qoniqmaslik insoniyatni taraqqiyotga va madaniyat rivojlanishiga undagan. Holatidan qoniqib o‘tiraberish – ortga ketishdir.

Pulning jozibasi – juda kuchli. Lekin, hayotga jiddiy qaragan odam uchun pulning o‘zi yetarli emas.

Kimnidir sevsang, uning ko‘zlarida hamisha quvonch chaqnayotganligini ko‘rging keladi.

Atirgul – loy va iflos tuproqda o‘sadi.

Kuch maydoni nima? Bu juda oddiy narsa. Masalan, jism atomlardan tashkil topadi. Atomlar esa bir-birlari bilan o‘zaro ta’sir kuchlari orqali bog‘langanlar. Endi, ana shu atomlarni olib tashlang! Nima qoladi? Kuch maydoni.

O‘tgan zamonni butunlay unitish mumkin emas, chunki u bugunni keltirib chiqargan.

Mish-mishlarni barcha zamonlarda to‘xtata olishmagan.

Sen ko‘phujayralik organizm sifatida taxminan ellik trillion hujayradan iboratsan. Lekin, shaxs sifatida, aytilgan barcha hujayralar ahamiyati yig‘indisidan muhimroqsan.

Ishlarni rivojlantirish uchun rejalar tuzishning o‘zi kamlik qiladi. Ularni vaqt kelganda o‘zgartirishni ham bilish kerak.

Men to‘satdan, odamlar ahmoqdir, degan fikrga kelib qoldim. O‘ylab ko‘ring, insonlar xatti-harakatlarini tartibga soluvchi qonun-qoidalar yo‘q edi, ularni o‘ylab topishdi. Ammo, odamlar, shu, o‘zlari o‘rnatgan qoidalarga rioya qilishmaydi. Ajab!..

Telegram: @curiosities

7 onsites 7 offers

2023-07-26T07:55:09.546Z

Wanted to share my recent job search results and materials I used for studying.

I have 6 yoe with TC 530k and tried to break into staff level this time around. Prepared 1 month with a mix of LC, system design, and behavioral preparation. I knew that my yoe is low, so will be a uphill battle. I ended up doing 7 onsites and got 7 offers (some senior, some staff). Sharing the resources that helped me be successful.

— LEETCODE —

Always ask clarifying questions, they are meant to be vague.

Tech Interview Handbook (solve 50 suggested LCs multiple times)
https://www.techinterviewhandbook.org/software-engineering-interview-guide/
Grokking Coding Interview:
https://www.educative.io/courses/grokking-the-coding-interview

I always try to solve each question myself before looking at answers. After struggling with certain topics, I found some youtube resources that were really helpful.

Graph problems: https://youtu.be/tWVWeAqZ0WU
Kahn’s topsort: https://youtu.be/cIBFEhD77b4
Dijkstra’s shortest path: https://youtu.be/pSqmAO-m7Lk
Kruskal’s MST: https://youtu.be/JZBQLXgSGfs
Union find: https://youtu.be/ibjEGG7ylHk
Dynamic programming: https://youtu.be/oBt53YbR9Kk

I would say 1/2 of my coding questions was graph related, and I used topsort, MST, union find during my interviews so its worth knowing them well.

Really great resource on Binary Search (especially for harder variants): https://leetcode.com/discuss/general-discussion/786126/Python-Powerful-Ultimate-Binary-Search-Template.-Solved-many-problems

Quite a few LC hards involve binary search as part of its solution, but its non-obvious.

At staff level, you are expected to have great communication, come up with one or more high level solutions in reasonable time with space and time complexity, implement mostly correct, and check for errors independently.

— SYSTEM DESIGN —

Always ask clarifying questions, they are meant to be vague.

Number 1 tip: Pay for mock interviews, take extensive notes, study, pay for more interviews. I used igotanoffer.com. Try booking different interviewers, they have different expectations, communication, friendliness.

Grokking system design: https://www.educative.io/courses/grokking-the-system-design-interview

It’s good to complete grokking, but in practice its a little too shallow for staff level.

Watch all videos and take notes from this channel: https://youtube.com/c/SystemDesignInterview

Most other channels like Exponent are actually not great examples of a good interviewee for staff level.

Read papers on Dynamo, BigTable, MapReduce, Cassandra, Raft, Lamport Clocks, etc.

A lot of material written by this Medium writer is great: https://medium.com/@kousiknath

Memorize Jeff Dean’s latency numbers: https://gist.github.com/jboner/2841832

If you have time, read DDIA: https://dataintensive.net

I memorized mnemonics for structure of how I execute my interview, as well as for each topic. Like OSI model, caching strategies, load balancing strategies, database types, etc. You need to make up your own in order to ingrain them.

Number 2 tip: Every system design question has a point of contention. Is it storage? Latency? Where will the system start to break? This is pivotal to figure out asap.

Basic structure:

Requirements (functional / non-functional)
Estimations (focus on contention point)
System API
Data model
High level design (core components)
Detailed design (ask where to dive in)
Bottlenecks (scale, redundancy, SPOFs, metrics, logs, alerts, dashboards, pagerduty, deployment, failure scenarios)

As staff level interviewee, you are expected to lead the interview and provide alternatives, weigh pros & cons of each approach and commit to one with justification. Outside of typical system design topics, staff level also needs to consider costs, system complexity, and business aspects (e.g. CDN too expensive for free tier).

For most interviewers, you should be familiar with at least one database technology for each category (key value, document, columnar, relational, etc). For Google, they typically want you to design from fundamentals instead of using off the shelf technologies.

I mastered using excalidraw for my system design interviews and always ask if I can use it instead: https://excalidraw.com

Number 3 tip: Listen intently to interviewer when they speak and take their hints.

— BEHAVIORAL —

Prepare an introduction about yourself. Keep it short and sweet, highlighting background and - a major accomplishment. (Don’t be afraid to sell yourself)

Grokking the behavioral: https://www.educative.io/courses/grokking-the-behavioral-interview

The resource itself isn’t that useful but should prepare answers from your own experience and recording yourself. Take time to reflect on your past few years and make sure you have answers about conflict, projects you led, giving/receiving feedback, and challenges you solved. Don’t lie.

STAR is a good structure for your stories but I learned a better story shape from this YouTuber.

U shape story: https://youtu.be/hU6BVxtGd5g

Read “Staff Engineer”: https://staffeng.com/book

For each company, make sure you know their products, their company motto and values. I kept notes which I read a few mins before my onsite starts. Prepare plenty of questions to ask.

— OFFERS —

Current TC 530k (Senior)

AtoB (Senior/Staff)
TC 325k
Base 200k, Options 500k over 4 years
Notes: Hard to evaluate startup offer, it felt too low and risky for me.

Airbnb G9 (Senior)
TC 450k
Base 225k, RSU 825k over 4 years, Sign on 80k
Notes: I did an uplevel round for staff after onsite. Recruiter said based on interviewing perf, the team will vouch for me for staff. After uplevel round, they said I did well but team wants to be conservative so no staff offer. I passed on the senior offer.

Google L5 (Senior)
TC ~480k
Notes: No actual numbers. I did a L6 onsite, went on and matched a team for TLM role. HC came back down leveling citing YOE but with highest verbal offer. I passed on the senior offer.

Roblox IC4 (Senior/Staff)
TC ~560k
Notes: No actual numbers. Roblox had the most rounds out of everybody. Kept pushing me to share numbers saying they want to beat them all and put together an offer only once. I shared staff level expectations (IC5) and eventually shared my highest numbers because they wouldn’t proceed. They came back saying IC5 needs 10 yoe and that I should take the other offers.

Snap L5 (Staff?)
TC 576k
Base 225k, Bonus 34k/year, RSU 940k over 3 years, Sign on 15k
Notes: Not sure if Snap L5 is staff but that is what they said it maps to. Negotiated from 550k and apparently this is the max.

Stripe L4 (Staff)
TC 690k
Base 250k, Bonus 40k/year, RSU 380k/year, Sign on 80k
Notes: Originally got L3 (Senior) offer but persuaded recruiter to try staff loop. Passed staff loop and then negotiated from 650k.

Quant firm
TC 800k
Base 210k, Bonus 590k/year
Notes: Didn’t think I’d get it but I somehow I did it. Questions similar to regular FANG. Negotiated from 750k. I ended up taking this offer because it’s cash and I’m concerned about recession.

Always negotiate! And try to get multiple offers as that is the best form of leverage. Read this:
https://haseebq.com/my-ten-rules-for-negotiating-a-job-offer/

Source: https://www.teamblind.com/post/7-onsites-7-offers-aAFTykAD

Telegram: @flutterblogs

Flutter isolates - bilishingiz kerak bo'lgan hamma narsa

2023-07-25T10:17:41.220Z

"Izolyatsiya" so'zi siz uchun yangi bo'lmasligi kerak - pandemiya boshlanganidan beri u mashhur so'zga aylandi. Ehtimol, siz bu atamani Flutterga nisbatan ishlatilganini ham eshitgandirsiz, ammo "isolates" o'zi nima? Dart kodingizni qanday "run" qiladi? Isolatesni qanday amalga oshirasiz? Bu savollarning barchasiga ushbu maqolada javob beriladi.

Agar siz Flutterda yangi bo'lsangiz, bu maqola siz uchun, chunki men ko'plab tushunchalarni soddalashtirishga harakat qildim. Ammo, agar siz tajribali dasturchi bo'lsangiz, ushbu maqola ham foydali bo'lishi mumkin. Flutter izolatlari kontseptsiyasini tushuntirishga yordam berish uchun biz kofe kioskining analogiyasidan foydalanamiz .

Dartda kodning bajarilishi

Dart - bu bir oqimli til (single thread). Bu nimani anglatishini tushunish uchun birinchi navbatda oqimlar nima ekanligini tushunishimiz kerak.

Oqim (thread) nima?

Oqim - bu jarayonning birligi. Bu asosiy jarayondan mustaqil ravishda rejalashtirilishi va bajarilishi uchun mo'ljallangan kichik ko'rsatmalar to'plami.

Hisoblashda jarayon atamasi bajarilayotgan dasturning holatini bildiradi.

Endi sizni bir narsa qiziqtirayotgan bo‘lishi mumkin: Agar Dart bitta oqimli til bo‘lsa, Flutter-dagi asinxron vazifalar (masalan, HTTP so'rovi orqali ma’lumotlarni olish) ilovaning boshqa faoliyatiga to‘sqinlik qilmasdan qanday qilib optimal tarzda bajarilishi mumkin? Xo'sh, bu ikki xil tushunchaga olib keladi, konkurentlik (concurrency) va parallellik (parallelism), birinchisi asinxron vazifalar uchun, ikkinchisi esa izolyatsiyada ishlaydigan vazifalar uchun. Ushbu tushunchalarni tushunish uchun keling, ikkita stsenariyni tayyorlaymiz.

1-stsenariy (concurrency)

Siz qahvaxonada kofe ichmoqchisiz. (Kofe do'konini faqat eshikli yopiq xona deb hisoblang.) Uzun navbat bor, lekin siz o'z navbatingizni kutishga qaror qildingiz. Barista (kofe ichimliklar tayyorlovchi va xizmat ko'rsatuvchi shaxs) navbatdagi har bir keyingi mijozning buyurtmalarini birin-ketin qabul qiladi.

Aytaylik, barista A va barista B xizmarlari o'rtasida vaqtli farq bor. Mijozlar barista B ni buyurtmalar qabul qilishini kutishi va navbat bilan siljishlari kerak. Barista A va barista B xizmatlari o'rasidagi farq mijozlarning harakatlariga boshqa tarzda to'sqinlik qilmaydi, chunki ular hali ham bir-birlari bilan gaplashishi, o'zaro tanalari bilan aloqa qilishlari mumkin va xkz.

Dartdagi asinxron kod ham xuddi shunday ishlaydi: awaitkalit so'ziniasync funksiyasida ishlatganingizda, dasturning boshqa qismlari ishlashda davom etadi va async vazifa tugagach, kodning keyingi qatoridan davom etadi. Vazifa (Task) - bu kerak bo'lganda asyncdasturingizning turli qismlari (voqealarni qayta ishlash) o'rtasida o'tadigan Dart hodisalari tsikli. Quyidagi kod namunasi buni amalda ko'rsatadi.

void asyncTask() async {
   /// Ushbu vazifa o'tishi uchun 5 sekund kutiladi
   final result = await Future.delayed(Duration(seconds: 5));

   /// So'ng, kodning keyingi qismlari ishlashga o'tadi
   /// Kutish davomida, bu kodning boshqa qismlarini ishlashdan bloklamaydi
   print(result);
 }

2-stsenariy (parallelism)

Bu safar siz va do'stingiz qahvaxonaga borishga qaror qildingiz, lekin birinchi do'konda navbat juda ko'p va kechikishlar juda ko'p. Shunday qilib, do'stingiz sizni birinchi qahvaxonada qoldirib, keyingi qahvaxonaga borishga qaror qiladi.

Bu stsenariyda aytishimiz mumkinki, siz birinchi qahvaxonada kofe olishingiz va do'stingiz keyingi qahvaxonada qahva olish jarayoni parallel ravishda sodir bo'lmoqda, chunki birinchi qahvaxonada nima sodir bo'lishidan qat'i nazar, keyingi qahvaxonaga ta'sir qilmaydi.

Bir qator dasturlarni parallel ravishda ishga tushirish uchun izolyatsiyalar ishga tushadi. Ammo ular buni qanday qilishlarini muhokama qilishdan oldin, birinchi navbatda Dartdagi izolyatsiya nima ekanligini tushunishimiz kerak.

Izolyatsiya nima?

Gapirishdan oldin shuni ta'kidlash kerakki, Dart dasturlari "default" holat bo'yicha izolyatsiyalarda ishlaydi. Dartdagi izolyatsiyani kofe kioski ichidagi kofe ichimliklar tayyorlash va qahva buyurtma qilish kabi tadbirlar o'tkaziladigan kichkina xona deb o'ylab ko'ring. Izolyatsiya mashinadagi kichik bo'shliqqa o'xshaydi, uning xotirasi (qisqa muddatli asosda kerak bo'ladigan ma'lumotlarni saqlaydigan tizim) va kodni qayta ishlovchi voqealar sikli (event loop) da ishlaydigan bitta oqim.

Manba: https://www.youtube.com/watch?v=OLAXR0TCrcc

Dart "multithreading"

Esingizda bo'lsa, biz Dartni bir oqimli til deb aytgan edik. Ammo bizda ishlash uchun juda og'ir hisoblash kodi bo'lsa-chi? Bunday holda, vazifani asinxron usulda bajarish, ehtimol, ilovada kechikishga olib keladi, shuning uchun bizga bu vazifani boshqa ish oqimlarida bajarish usuli kerak.

Dartda multithreadingni amalga oshirish uchun biz yangi izolyatsiyani yaratishimiz kerak. Shuni ta'kidlash kerakki, Dartda izolyatsiyalar xotirani boshqa izolatlar bilan baham ko'rmaydi. Aksincha, ular bir-biridan butunlay ajratilgan (oh, bechora izolyatsiyalar ...) , va ularning nomi aynan shundan kelib chiqqan.

Yangi izolyatsiyada o'z xotirasi va voqea tsikllari bo'ladi. Buni mustaqil Dart dasturini ishga tushirish deb tasavvur qiling. Yaxshi yangilik bor: ikkita izolyatsiya xabarlarni oldinga va orqaga uzatish orqali bir-biri bilan muloqot qilishi mumkin. Quyida buning misoli keltirilgan.

https://medium.com/dartlang/dart-asynchronous-programming-isolates-and-event-loops-bffc3e296a6a

Dartda boshqa izolyatsiyani yaratishning ikki yo'li mavjud: Isolate.spawn()funktsiya va compute()funktsiya.

Isolate.spawn() yordamida yangi izolyatsiya yaratish

Keling, Flutter izolyatsiyasining ba'zi misollarini ko'rib chiqaylik. Izolyatsiyani yaratishning birinchi usuli Isolate.spawn()dan foydalanishdir. Biz birinchi parametr sifatida ishlatmoqchi bo'lgan usulga o'tamiz, ikkinchi argument esa biz izolyatsiyaga o'tmoqchi bo'lgan parametrdir.

Izolyatsiyaga uzatiladigan funksiya spawn()yuqori darajadagi funksiya *(sinf chegarasida bo‘lmagan funksiya) yoki statik usul bo‘lishi kerak.

Mana, izolyatsiyani yaratish uchun kod:

import 'dart:isolate';

void main() {
  Isolate.spawn<IsolateModel>(heavyTask, IsolateModel(355000, 500));
}

void heavyTask(IsolateModel model) {
 int total = 0;


 /// Belgilangan miqdordagi iteratsiyalarni bajaradi
 for (int i = 1; i < model.iteration; i++) {

   /// Har bir indexni ko'paytiruvchiga ko'paytiradi va jamini hisoblaydi
   total += (i * model.multiplier);
 }

 log("FINAL TOTAL: $total");
}

class IsolateModel {
 IsolateModel(this.iteration, this.multiplier);

 final int iteration;
 final int multiplier;
}

Ikki izolyatsiya o'rtasida muloqot qilish

Ikki izolyatsiya o'rtasidagi aloqani portlar ( ReceivePortva SendPort) orqali xabarlar yoki qiymatlarni yuborish orqali amalga oshirish mumkin. Ushbu portlar Stream kabi ishlaydi. Aslida Streammavhum sinfidan ReceivePort foydalanadi.

SendPort-ni ReceivePort-dan ReceivePort-ning sendPortqabul qilish usuli (getter) ni chaqirish orqali yaratish mumkin . Bu xabarlar ReceivePort-ga yuboriladigan vositadir. Boshqa tomondan, ReceivePort o'zining SendPort-dan xabarlarni tinglaydi.

Ushbu jarayonning vizual tasvirini ko'rish uchun quyidagi rasmga qarang:

Ikki izolyatsiya o'rtasida xabar qanday yuborilishi tasvirlangan rasmli illyustratsiya. SenderPort SendPort orqali xabar sifatida yuborilishi mumkin, bu esa qabul qiluvchiga qayta aloqa qilish uchun ruxsat beradi.

Mana, izolyatsiyalar orasidagi aloqani ko'rsatadigan kod parchasi. Diqqat - kod biroz chalkash. Bu qanday ishlashini tushunishingizga yordam berish uchun ba'zi izohlar qo'shdim. Kodni yozish va ishga tushirish ham yordam beradi. Kodni o'qiyotganda, Maykni do'stingizning ismi deb hisoblang.

import 'dart:isolate';

void main() {
 createIsolate();
}

Future createIsolate() async {
 /// Where I listen to the message from Mike's port
 ReceivePort myReceivePort = ReceivePort();

 /// Spawn an isolate, passing my receivePort sendPort
 Isolate.spawn<SendPort>(heavyComputationTask, myReceivePort.sendPort);

 /// Mike sends a senderPort for me to enable me to send him a message via his sendPort.
 /// I receive Mike's senderPort via my receivePort
 SendPort mikeSendPort = await myReceivePort.first;

 /// I set up another receivePort to receive Mike's response.
 ReceivePort mikeResponseReceivePort = ReceivePort();

 /// I send Mike a message using mikeSendPort. I send him a list,
 /// which includes my message, preferred type of coffee, and finally
 /// a sendPort from mikeResponseReceivePort that enables Mike to send a message back to me.
 mikeSendPort.send([
   "Mike, I'm taking an Espresso coffee",
   "Espresso",
   mikeResponseReceivePort.sendPort
 ]);

 /// I get Mike's response by listening to mikeResponseReceivePort
 final mikeResponse = await mikeResponseReceivePort.first;
 log("MIKE'S RESPONSE: ==== $mikeResponse");
}

void heavyComputationTask(SendPort mySendPort) async {
 /// Set up a receiver port for Mike
 ReceivePort mikeReceivePort = ReceivePort();

 /// Send Mike receivePort sendPort via mySendPort
 mySendPort.send(mikeReceivePort.sendPort);

 /// Listen to messages sent to Mike's receive port
 await for (var message in mikeReceivePort) {
   if (message is List) {
     final myMessage = message[0];
     final coffeeType = message[1];
     log(myMessage);

     /// Get Mike's response sendPort
     final SendPort mikeResponseSendPort = message[2];

     /// Send Mike's response via mikeResponseSendPort
     mikeResponseSendPort.send("You're taking $coffeeType, and I'm taking Latte");
   }
 }
}

Yuqoridagi kodni haddan tashqari ortiqcha ishlab chiqilgan deb aytish mumkin, buning sababi shundaki, izolyatsiyalar faqat asosiy oqimda kechikishga olib kelmaslik uchun boshqa oqimda bajarilishi kerak bo'lgan og'ir hisoblash ishlarini bajarishda ishlatilishi kerak. Ya'ni, yuqoridagi kodning maqsadi turli xil izolyatsiyalar bir-biri bilan qanday aloqa qilishini ko'rsatishdir.

Izolyatsiya o'zining voqealar siklidagi barcha hodisalarni amalga oshirganda, Dart avtomatik ravishda izolyatsiyani o'ldiradi. Izolyatsiyani qo'lda o'ldirish uchun isolate.kill()dan foydalaning. Izolyatsiyani to'xtatib turish uchun isolate.pause() dan foydalaning . To'xtatilgan izolyatsiyani davom ettirish uchun isolate.resume() dan foydalaning.

compute() yordamida yangi izolyatsiya yaratish

Yangi izolyatsiyani yaratishning eng oson yo'li - compute() dan foydalanish, garchi o'zaro kelishuv shundaki, siz ko'plab moslashuvchan Isolate.spawn() bergan imkoniyatlarni yo'qotasiz.

compute<Q, R>()ikkita umumiy turni qabul qiladi: Qbu izolyatsiya funksiyasi parametr turi va Rizolyatsiya funksiyasining qaytish turi. Quyidagi kod parchasi buni qanday amalga oshirishni ko'rsatadi:

import 'package:flutter/foundation.dart';

void main() {
  compute<IsolateModel, void>(heavyTask, IsolateModel(355000, 500));
}

void heavyTask(IsolateModel model) {
int total = 0;

/// Performs an iteration of the specified count
for (int i = 1; i < model.iteration; i++) {

  /// Multiplies each index by the multiplier and computes the total
  total += (i * model.multiplier);
}

log("FINAL TOTAL: $total");
}

class IsolateModel {
IsolateModel(this.iteration, this.multiplier);

final int iteration;
final int multiplier;
}

Xulosa

Xulosa qilib aytadigan bo'lsak, Dart-da "multithread" larni o'tkazish mumkin, garchi Dart bir-treadli til bo'lsa ham. Bitta ogohlantirish bor: Dart ilovalari allaqachon juda tez va yuqori darajada optimallashtirilgan va ko'pincha siz izolyatsiyadan foydalanishingiz shart emas. Uni faqat og'ir hisoblash ishlarini bajarish kerak bo'lganda foydalaning. Shuningdek, biz voqea tsikllari nima ekanligini va ular Dartda qanday ishlashini muhokama qildik va izolyatsiyalar xotirani baham ko'rmasa ham, qanday qilib muloqot qilishini ko'rib chiqdik. Sog' bo'ling!

Manba: https://blog.codemagic.io/understanding-flutter-isolates/

Telegram: @flutterblogs

Flutter Security – Follow These 10 Security Tips To Prevent Security Risks

2023-07-24T07:18:10.751Z

Though Flutter apps have become immensely popular in recent years, certain security risks pose a threat to app security. Flutter apps can expose sensitive data in the absence of adequate security measures. Reverse engineering is among the most common threats faced by Flutter apps as Dart code (the programming language used in Flutter apps) generates metadata that can easily give insights into the application’s workings. Hackers conduct static analysis that can compromise the security of Flutter apps and encourage tampering attempts. This article will shed light on Flutter apps and ways to ensure Flutter app security.

Flutter Security Philosophy

Flutter facilitates the development of natively compiled, multi-platform applications from a single codebase. The Flutter team offers robust measures to tackle security flaws in apps created with the Flutter framework. Let’s understand the security philosophy that forms the foundation of Flutter’s security strategy.

Identify: Identify core assets, threats, and vulnerabilities to track and prioritize key security risks
Detect: Employ techniques and tools like vulnerability scanning, static application security testing, and fuzzing to pinpoint vulnerabilities
Protect: Mitigate known vulnerabilities and safeguard critical assets against source threats to prevent security risks
Respond: Define processes to report, triage, and respond to vulnerabilities or attacks
Recover: Equip apps with capabilities to contain damage and recover from the incident with minimal impact

How to Secure Your Flutter Applications?

Developers rely on Flutter to minimize development efforts and maintain native performance. Intellectual property theft, cloning, and tampering are among the security concerns to be addressed when developing Flutter apps. Here are the top 10 ways to secure your Flutter application:

1. Use code obfuscation

Hackers can reverse engineer app code. Strings, methods, class names, and API keys can be leaked if hackers launch attacks on the application. Hackers can easily misuse the code if data is stored in plain text. Obfuscation is a process that makes it difficult for hackers to read the code. It hides functions and class names in compiled Dart code. You can secure Flutter apps using code obfuscation techniques that modify an app’s binary. Use the -obfuscate parameter from the Dart side to obfuscate data.

2. Secure API keys

API keys that are not protected using obfuscation or encryption can be taken advantage of by hackers. You can apply application restriction controls to control which applications, websites, or IP addresses can access your API keys. Encrypting/decrypting API keys on runtime is yet another effective way to secure API keys and prevent hackers from deciphering the data. You should avoid tracking API keys on the repository to minimize the risk of exposing values. Using Firebase Remote Config is not recommended for storing sensitive data.

3. Use Flutter jailbreak detection

Flutter_jailbreak_detection package in Flutter helps safeguard apps against security threats from a jailbroken or rooted device. This package can be used to detect whether the app is running on a compromised device. Jailbroken or rooted devices have more privileges and enable easy installation of malware and viruses. Flutter apps with jailbreak detection use RootBeer on Android and DTTJailbreakDetection on iOS to detect if the app is running on a jailbroken or rooted device.

4. Ensure secure network connections

A secure network connection between mobile apps and servers is a prerequisite to ensure the protection of apps. Using a Transport Secure Layer (TSL) facilitates the secure exchange of information. Whitelisting your domain can help restrict traffic that is not secure. Implementing certificate pinning is another security best practice that will ensure all connections are secure. This prevents hackers from tampering with data in transit using illegitimate certificates.

5. Use only necessary permissions

Applications can access hardware and native APIs through app permissions. Avoid adding plugins that contain unnecessary permission requests.

6. Secure user data

Applications sometimes may have to store sensitive data such as PII. Use the Flutter_secure_storage package when there is a need to store PII, auth token, or other sensitive data. This package uses Keystore for Android and Keychains for iOS. You can use Hive which is a Dart package to store data locally and prevent tampering.

7. Background snapshots protection

Mobile devices have a task-switcher feature that displays a snapshot of the last state of the app. This snapshot, however, can expose sensitive information. The secure_application package is designed to protect application content from view on demand.

8. Implement local authentication

Local_auth is a Flutter plugin that enables local authentication for Flutter apps. Biometric authentication is useful to protect apps that store payment information or other critical information. Local authentication also helps provide an extra layer of protection in case the device is stolen.

9. Secure developer identity

Any data that may expose developer identity needs to be encrypted. Encrypt sensitive files like key.jks & keystore.properties with GPG. Avoid keeping track of unencrypted sensitive data in your repository.

10. Secure CI infrastructure

CI infrastructure refers to developers integrating code into a shared repository frequently. Developers should constantly monitor vulnerabilities and keep Virtual Machines updated to ensure apps are running in a protected environment. API keys and other sensitive data should not be added to the code. They should instead be included in the secret settings of the project.

Important Security Best Practices to Bear in Mind

Stay up-to-date: Staying updated about the latest Flutter SDK, plugins, and packages is critical to enhancing the security of Flutter apps. The Flutter team regularly releases updates to address security flaws detected in previous versions.
Update your application’s dependencies: You need to upgrade your package dependencies on time. Pinning to specific versions of dependencies is not recommended. If you decide to pin, make sure you do timely checks to ensure dependencies are updated properly.
Keep your Flutter version up to date: You may miss out on important security updates if you are using customized versions of Flutter. Such versions may not include security fixes usually found in the current versions. Hence, it is mandatory to update your copy of Flutter from time to time.

Final Thoughts

Flutter is a cost-effective way to build multi-platform native applications. Flutter apps are compiled directly into the native code which leads developers to think that security is not a major concern in Flutter apps. But Flutter apps, like every other traditional mobile app, are at risk of getting hacked. Flutter apps running in hostile environments are vulnerable to tampering and dynamic attacks. Hackers that know how to reverse engineer binaries can easily exploit security loopholes in Flutter apps. Robust security measures that include runtime detections to identify modifications or tampering are imperative to secure Flutter apps. Though Flutter has emerged to be a prominent framework among developers, building apps without appropriate security measures will have disastrous consequences for the enterprise. The security measures discussed in this article will help safeguard your Flutter mobile apps from a wide range of threats.

Пропаганда. Источники (Propoganda: Manbalar)

2022-06-01T20:15:25.977Z

История пропаганды / Propaganda tarixi:

https://arzamas.academy/mag/603-propaganda

Как работает пропаганда / Propoganda qanday ishlaydi:

https://www.prostranstvo.media/kak-rabotaet-propaganda/

Атлас стереотипов и предрассудков / Stereotiplar va xurofotlar atlasi:

https://alpinabook.ru/catalog/book-atlas-stereotipov-i-predrassudkov/

Новояз / Novayaz:

https://theoryandpractice.ru/posts/15651-sorri-za-novoyaz-pochemu-dialog-s-vlastyu-v-rossii-seychas-nevozmozhen-i-pri-chem-zdes-oruell

История создания и механизм работы НАТО / NATO ning tarixi va ishlash mexanizmi:

https://mailchi.mp/getkit.news/nato

Ложная дилемма / Yolg'on ikkilanganlik:

https://effectiviology.com/false-dilemma/

Демагогия / Demagogiya:

https://www.kommersant.ru/doc/3542549

Как работает подчинение авторитетам и конформизм / Avtoritetlarga sodiqlik va konfirmizm qanday ishlaydi:

https://monocler.ru/podchinenie-avtoritetu-kak-eto-rabotaet/

Про пирамидки и присоединение к большинству / Piramidkalar va ko'pchilikga qo'shilish tabiati:

https://mel.fm/zhizn/istorii/9041685-sovret-li-chelovek-pod-davleniyem-gruppy-eksperimenty-na-detyakh-i-studentakh-kotoryye-provodili-v-s

Цитата Тэтчер / Tetcher iqtibosi:

https://provereno.media/2021/05/18/govorila-li-margaret-tetcher-chto-ekonomicheski-celesoobraznoe-naselenie-rossii-15-mln-chelovek/

YouTube:

https://youtu.be/YB-N-_JYSnw - МОЛЧАНИЕ — знак согласия? ПРОПАГАНДА — ТОПЛЕС

https://youtu.be/lLEiT9PeHSg - Обыкновенные зомби. Как работает ложь (полный выпуск)

Blog | @curiosities

🇺🇿 Uzbekistan-Developers-Blogs

2022-06-01T19:35:13.271Z

📃 All Uzbekistan Developers blog list

If you have a blog (Telegram, website, Youtube, or any), welcome to Fork the repository and add yours. And make Pull request. If you can’t create Pull request, write to me directly in Telegram.

📚 Blogs

Flutter Blogs | Uzbekistan Telegram Blog
Nodirbek Ergashev Telegram Blog
Jakhongir Rakhmonov Telegram Telegram2 Blog
Bob Usmonov Telegram
10x Engineer Telegram
Ulugbek Samigjonov Telegram
muhammadyunus.uz Telegram
Sariq Dev Telegram
mabrur.dev Telegram
Inspired Engineer Telegram
Josh*Developer Telegram
Alisher Tojiyev Telegram
AHBS Telegram
Khumoyun Codes Telegram
Sukhrob Khakimov Telegram
Azimjon Pulatov Telegram
Farhodjon Yashayapti Telegram
Mayoq Telegram
Akbarjon Dev Telegram
Node.js (Saidabdulla Masharipov) Telegram
Farrukh Saliev Telegram
Umar Muhandis Telegram
Sardor Og’a kanali Telegram
Bexrux.ru - IT blog Telegram
Nurmuhammad Mahmudov - Telegram
Abduaziz Py🔥 Telegram
Saud Abdulwahed Telegram
Dev Farhod Telegram
PyNotes Telegram
Nuruddin Blogs Telegram
dev_b.log Telegram
azizbekx Telegram
Abdusamad Malikov Telegram Blog
Izlan & Rivojlan Telegram YouTube

💼 Job sources

Ustoz Shogird Telegram
Rizqim Telegram
IT Market Telegram
Teamwork.uz (фриланс площадка) Telegram
UZ Python Jobs Telegram
UzDev Jobs Telegram
IT Вакансии Ташкент Telegram
Uzbekcoders Jobs Telegram

🎙 Communities

Golang Telegram
Linux Telegram
DevOps Telegram
Python Telegram
Django Telegram
PyTelegramBotAPI Telegram
Flask Uzb Telegram
JS Telegram
NodeJs Telegram
Angular Telegram
Vue JS Telegram
React Telegram
Spring Telegram
TelegrafJS Telegram
PHP Telegram
Laravel Telegram
Yii Telegram
Dart - Flutter Telegram
iOS Telegram
Swift UZB Telegram
PostgreSQL Uzbekistan Telegram
DotNet Telegram
Csharp Uz Telegram
Xamarin Uz Telegram
UzGeeks Telegram
UzDev – Сообщество разработчиков Telegram
Faang Interview Telegram
Leetcode Telegram

Source: https://nodirshox.github.io/uzbekistan-developers-blogs/

Join: https://t.me/FlutterBlogs

Dartda ixtiyoriy parametrlar

2022-06-01T18:04:14.542Z

Dartda ikki xil funksiya parametrlari mavjud: positional va named.

Ixtiyoriy pozitsion parametrlar

Pozitsion parametrlar sizga tanish bo'lgan parametrlardir:

int sumUp(int a, int b, int c) {
  return a + b + c;
}
// ···
  int total = sumUp(1, 2, 3);

Dart yordamida siz ushbu pozitsion parametrlarni qavs ichiga oʻrash orqali ixtiyoriy qilishingiz mumkin:

int sumUpToFive(int a, [int b, int c, int d, int e]) {
  int sum = a;
  if (b != null) sum += b;
  if (c != null) sum += c;
  if (d != null) sum += d;
  if (e != null) sum += e;
  return sum;
}
// ···
  int total = sumUpToFive(1, 2);
  int otherTotal = sumUpToFive(1, 2, 3, 4, 5);

Ixtiyoriy pozitsion parametrlar har doim funksiya parametrlari roʻyxatida oxirgi boʻladi. Agar siz boshqa standart qiymat kiritmasangiz, ularning standart qiymati null bo'ladi:

int sumUpToFive(int a, [int b = 2, int c = 3, int d = 4, int e = 5]) {
// ···
}
// ···
  int newTotal = sumUpToFive(1);
  print(newTotal); // <-- prints 15

Code example

Birdan joinWithCommas()beshgacha butun sonni qabul qiladigan, so'ngra vergul bilan ajratilgan raqamlar qatorini qaytaradigan funksiyani amalga oshiring. Funktsiya chaqiruvlari va qaytarilgan qiymatlarga ba'zi misollar:

String joinWithCommas(int a, [int b, int c, int d, int e]) {
  var total = '$a';
  if (b != null) total = '$total,$b';
  if (c != null) total = '$total,$c';
  if (d != null) total = '$total,$d';
  if (e != null) total = '$total,$e';
  return total;
}

Funktsiya chaqiruvi

joinWithCommas(1)       
joinWithCommas(1, 2, 3)     
joinWithCommas(1, 1, 1, 1, 1)

Qaytarilgan qiymat

'1'
'1,2,3'
'1,1,1,1,1'

Ixtiyoriy nomli parametrlar

Figurali qavs sintaksisidan foydalanib, siz nomlari bo'lgan ixtiyoriy parametrlarni belgilashingiz mumkin.

void printName(String firstName, String lastName, {String suffix}) {
  print('$firstName $lastName ${suffix ?? ''}');
}
// ···
  printName('Avinash', 'Gupta');
  printName('Poshmeister', 'Moneybuckets', suffix: 'IV');

Siz kutganingizdek, ushbu parametrlarning qiymati default holat bo'yicha null, lekin siz standart qiymatlarni berishingiz mumkin:

void printName(String firstName, String lastName, {String suffix = ''}) {
  print('$firstName $lastName $suffix');
}

Funktsiya bir vaqtda ham ixtiyoriy pozitsion, ham ixtiyoriy nomlangan parametrlarga ega bo'lishi mumkin emas.

Kod misoli

copyWith()MyDataObject sinfiga misol metodini qo'shing . U uchta nomlangan parametrni olishi kerak:

int newInt
String newString
double newDouble

Chaqirilganda , oldingi parametrlardan (agar mavjud bo'lsa) ob'ektning xususiyatlariga ko'chirilgan ma'lumotlar bilan joriy misol asosida copyWith()yangisini qaytarish kerak . MyDataObjectMisol uchun, agar newIntnull bo'lmasa, uning qiymatini ga ko'chiring anInt.

class MyDataObject {
  final int anInt;
  final String aString;
  final double aDouble;

  MyDataObject({
     this.anInt = 1,
     this.aString = 'Old!',
     this.aDouble = 2.0,
  });

  // copyWith metodingizni shu yerga qo'shing:
}

copyWith haqida qisqacha:

//copyWith bizga T ni nusxalash va parametr argumentlari o'rniga
//qayta qiymat yozish imkonini beradi.

class _HomePageState extends State<HomePage> {
  List<Product> products = [];

  @override
  void initState() {
    super.initState();

    Product sixSeaterDiningTableBrown = Product(
      id: "0",
      name: "6 Seater Dining Table",
      color: Colors.brown,
    );

    Product sixSeaterDiningTableBlack =
        sixSeaterDiningTableBrown.copyWith(color: Colors.black, id: "1");

    products.add(sixSeaterDiningTableBrown);
    products.add(sixSeaterDiningTableBlack);
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text("Hello, copyWith!"),
      ),
      body: ListView(
          children: products
              .map((Product product) => ListTile(
                    trailing: Container(
                      width: 14,
                      height: 14,
                      color: product.color,
                    ),
                    title: Text(product.name),
                    subtitle: Text(product.id),
                  ))
              .toList()),
    );
  }
}

Maqola yoqqan bo'lsa do'stlaringizga ulashing va kanalimizga a'zo bo'ling:

Avtor: Mamasodiqov M

Kanal: Flutter Blogs

Курьёзные

2021-10-30T16:16:07.190Z

Если что-то может быть понято двояко - оно будет понято неправильно.

===

Мелочь, а приятно. А если приятно, то это уже не мелочь.

===

О вкусах не спорят - спорят об их качестве

===

Из двух спорящих всегда один - сволочь, а другой - дурак.

===

Чистая совесть - лучшее снотворное.

===

Удар судьбы в лоб означает, что не возымели действия её пинки в зад.

===

Чтоб Ваши желания обалдевали от Ваших возможностей..! (ехидный тост)

===

Очень много людей пропадает без вести при переходе от слов к делу.

===

Не всякий способен посмеяться над самим собой, дар этот редкий, требующий умения подняться над собственной ограниченностью

===

Не ждите чуда! Чудите сами!

===

Что посмеешь, то пожмёшь

===

Приближается мороз - здравствуй, остеохондроз...

===

Лишённым сострадания - не будет оправдания.

===

Моя жизнь - мои правила! Не нравятся правила? Не лезь в мою жизнь...

===

Не можешь противостоять - противолежи!

===

Нашедшего выход затаптывают первым...

===

Самые протоптанные пути - в никуда.

===

Всё нормально. Просто нормы меняются

===

Никто не умрёт девственником, жизнь всех поимеет

===

Чем ты обладаешь, то обладает и тобой

===

Шагая по жизни, постарайся не раздавить впечатления.

===

Несите чушь бережно, стараясь не расплескать. Хороша только полная чушь.

===

Не ищи пятен на Солнце, - ослепнешь!

===

От шика до пшика - одна буква

===

Диплом позволяет ошибаться значительно увереннее

===

В беге трусцой самое важное - не потерять трусцы

===

За неимением своего таланта зарывал в землю чужой

===

Лучшую характеристику получила пустыня: у неё не оказалось теневых сторон

===

Боги всемогущи, но черти значительно расторопнее

===

Глупые мысли редко запаздывают

===

Более тупой замолкает последним

===

Иногда наломаешь дров, а потом думаешь - и нахрена мне столько

===

Маленький мальчик смеяться любил... Сделает гадость, и ржёт как дебил...

===

Поцелуй - это еще один приятный способ найти общий язык.

===

Отсутствие наряда служит иногда лучшим нарядом.

===

Жизнь-игра. Задумана хреново, но графика обалденная.

===

Игры в Интернете - это мастурбация, ведущая к деградации

===

Знание закона не освобождает от соблазна...

===

Если человек лишен чувства юмора, значит было за что

===

Смех без причины - признак незаконченного высшего образования

===

Смех продлевает жизнь на 5 минут, а секс удлиняет член на 15 минут.

===

Чем больше принимается законов, тем больше в стране беззакония

===

Хуже незваного гостя может быть только невыпровоженный...

===

Когда срывает крышу, самое время строить следующий этаж

===

Когда в голове сквозняк, уши служат вентилятором.

===

Чем меньше словарный запас, тем сильнее словесный понос

===

У меня характер тяжёлый ..потому что - золотой!

===

Молчание - золото. Будешь много молчать - ограбят

===

Бараны бывают курдючные и пердючные,
А коровы - дойные и подвзбздойные.

===

Весна покажет, что скрывал сугроб...

===

Виагра кончилась... осталось лишь смотреть.

===

У запора два врага - чернослив и курага

===

Видали мы таких, но убежать успели.

===

Нет вкуса? У меня?! А вы лизните!

===

Я проверялся. Вы больны не мною

===

Волки от испуга трахнули друг друга

===

Если вас незаслуженно обидели - вернитесь и заслужите!.

===