Flutter Dev | Uzbekistan 🇺🇿

Snippet! Loyihangizda AutomaticKeepAliveClientMixin ni ishlating va har safar TabView bolalarini (children) almashtirganingizda ularni qayta qurilishini oldini olasiz! Foydali bo'gan bo'sa like boooosing! Terqating! #snippet #code @flutterblogs

Nega "readable" ishlatish kerak? Loyihada ko'pgina tarqoq yordamchilar yoki kengaytmalar bo'lmaydi. Yordamchilar allaqachon qurilgan va "qutidan" olib foydalanishga tayyor. O'qilishi oson bo'lishi mumkin bo'lgan ko'plab foydalanish holatlarini topasiz! - Mana: https://pub.dev/packages/flutter_readable - Dokumentlari: https://flutterqueen.github.io/website/docs/readable/intro/ Like booosing! Sog' bo'lasla! #package #plugin @flutterblogs

Snippet! Eshmat: Agar BloC ning ichida Streamlarni ishlatishga to'g'ri kelib qolsa nima qilishimiz kerak? 🤔 Toshmat: StreamBuilderni BlocBuilder bilan o'ra! 🤪 Abdulla: Flutter BloC >=7.2.0 dan boshlab buni yechimini BloC ni o'zi beradi. Yuqoridagi snippetni ishlat! 🤓 Abdullani aytganini qil! (Batafsil) #bloc #code #stream #snippet @flutterblogs

Flatter (ixchamlovchi) - sizning kodingizni "tapaloq" lashtiradigan plugin! Ya'ni 🤔 Qisqa aytaman, - Avval:

InkWell(
      onTap: () {},
      child: const Center(
        child: Padding(
            padding: EdgeInsets.all(20),
            child: DecoratedBox(
              decoration: BoxDecoration(boxShadow: [
                  BoxShadow(
                      color: Colors.black,
                      .....

Keyin: Text('Example') .textStyle(color: Colors.black, fontSize: 18.0, fontWeight: FontWeight.bold) .shadow(color: Colors.black, blurRadius: 20, spreadRadius: 1.0) .padding(20) .center() .inkWell(onTap: () {}); Kodingiz uzun va xunuk widjet daraxtidan qisqa va tushunarli ko'rinishga o'tadi! Qiziq bo'lsa mana, ishlating: https://pub.dev/packages/flatter Sog' bo'lasla! (Debat) #pubdev #plugin @flutterblogs

Flutter dasturchilari uchun shpargalka! "AppStore" ga skrinshot yuklayotganda razmerlarga qarab yuklanadi. Shunda siz qaysi simulyatorni tanlab ochish kerakligini quyidagi jadvaldan ko'rib olasiz: https://mamasodikov.notion.site/iPhone-sizes-for-AppStore-10d92eea026b4c20a41cda7d44e265ed (Diqqat: Jadval Sun'iy Intellekt tomonidan yaratilgan) #iphone #inches @flutterblogs

🔤3️⃣maktab Ha bu tizim haqida bilmaslikni iloji yo'q. Bu o'sha 🦕 dinozavrlar davridan beri yashab kelayotgan, boshlang'ich dasturchilar uchun juda foydali bo'lgan dasturlashni vizual o'rganish tizimi. 🧑‍💻 Bu tizimda mavzular boshlang'ich va sodda bo'lishi bilan birga har bir mavzuni testlab sinab ko'rish imkoni bor. Dasturlash tillari ham juda katta assosrtimentda berilgan. Xohlaganingizni tanlab "tanovvul qivurasiz" 😋. Xullas bu tizimni juda ko'pchilik biladi. Lekin mabodo bilmaganlar uchun havola w3schools.com. ❤ IT ni boshlagan do'stlarizgayam jo'natib qo'ying. Faqat doimgiday ingliz tilida ) ✅ @codvo

10 Math Concepts for Programmers (and for Flutter devs :) Watch online: https://youtu.be/bOCHTHkBoAs #coder #math @flutterblogs

JSON:API nima? API yasash dunyosida hech qanday soha uni dizaynidan ko'ra qizg'in muhokama qilinmaydi. REST, gRPC dan GraphQL gacha veb-API larni o'zaro ta'sirini loyihalash va standartlashtirish uchun ko'plab yondashuvlar mavjud. Bugun biz boshqa yondashuv haqida gaplashamiz, JSON:API, batafsil API qurish uchun spetsifikatsiyasi JSONAPI.org da. JSON:API, JSON shaklidagi javoblarni formatlashni yanada izchil qilish uchun spesifikatsiyalar kuttubxonasi. Maqsad mahsuldorlik va samaradorlikni oshirishdan iborat bo'lib, JSON:API ortiqcha server so'rovlarini bartaraf etadigan samarali keshlash xususiyatlari taqdim etadi. - Batafsil: https://nordicapis.com/the-benefits-of-using-json-api/ - Case-study: https://youtu.be/HfGFk4S-G1A (UCHI.RU) - "AvitoTech" dan master klass: https://youtu.be/JD3HLaLxUJ8 - Solishtirish (REST vs JSON:API vs GraphQL): https://youtu.be/hhB7bJC_sVs Sizga qaysi biri qulay yoki ishlatgansiz: GraphQL yoki JSON:API ? #rest #graphql #jsonapi @flutterblogs

𝟲 𝗘𝘀𝘀𝗲𝗻𝘁𝗶𝗮𝗹 𝗔𝗣𝗜 𝗦𝘁𝘆𝗹𝗲𝘀 🔀 An API style is like a secret handshake 🤝 between two computers, helping them share and understand each other's messages. There are various methods of handshakes and each has its own way of sending and receiving information! Here are the 6 most important API styles you need to know: 1️⃣ SOAP 🧼 An XML-based communication protocol with strict contracts. It's mostly used over HTTP(S) 🌐 and is popular in enterprise environments 🏢. What Engineers need to know: As a software or DevOps engineer, understanding SOAP is crucial for working in enterprise environments, especially where legacy systems still exist. 2️⃣ REST API 🔄 An easy-to-understand, resource-focused API style. It uses standard HTTP methods 🌐 and often employs JSON for data. What Engineers need to know: REST APIs are common, so mastery of their design and use is a key skill for developers and DevOps. 3️⃣ gRPC ⚙️ An API style emphasizing remote procedure calls (RPCs). It uses HTTP/2 for transport and Protocol Buffers for data serialization, making it ideal for efficient, low-latency microservices 🔬. What Engineers need to know: Knowledge of gRPC can help in designing and maintaining high-performing, scalable microservices. 4️⃣ GraphQL 📊 A flexible query language for APIs allowing clients to request specific data. It was developed by Facebook and can combine data from multiple sources 🔄. What Engineers need to know: Understanding GraphQL can help in creating efficient APIs that prevent over-fetching and under-fetching of data. 5️⃣ Websocket 🔌 A protocol for real-time, bidirectional communication 🔄. It maintains a long-lived connection and is great for web apps needing live updates 📲. What Engineers need to know: Websockets are essential for applications requiring real-time data exchange, like chat applications or real-time analytics. 6️⃣ Webhook 🎣 A server-side, event-driven mechanism. It sends HTTP callbacks (usually POST requests) when specific events occur, perfect for real-time data updates or third-party service integration 🔗. What Engineers need to know: Webhooks are crucial for setting up automated workflows and integrations, a common task in DevOps and software development. To stay ahead of the curve, software and DevOps engineers need to understand these API styles, their benefits, and their use cases. This will allow them to design and implement efficient, scalable, and functional systems. 🚀💻 #api #styles @flutterblogs

Bitta dasturning o’zida 6 ta dasturchining ishini qilish mumkinmi? ✅ Albatta mumkin! Buning uchun siz Flutter framework’ini bilishingiz kerak bo’ladi. 👩‍💻 Flutter yordamida siz bir vaqtning o’zida Windows, Mac Os, Linux, Android, IOS va Web Frontend uchun kod yozishingiz mumkin. Shuning uchun ham hozirda ko’pchilik kompaniyalar ushbu Flutterdan foydalanishni afzal ko’rmoqdalar. 📞 +998732542404 📩 @rtmadmin 📍Marg‘ilon shahar Xiyobon ko‘chasi 65-uy (Diyor mehmonxonasi orqasida) Telegram | Instagram | Facebook | YouTube | TikTok

Windows zo'rmi yoki Mac? 💻 Mirshakardan "jichcha" hangoma.. #hengoma #time #offtopic @flutterblogs

🎙 PODCAST - Trending topics in Mobile 🔊 Mobilersda yangi loyiha - Podcast. Ushbu loyihada biz jamoamiz a’zolari hamda bir nechta mehmon mutaxassislar bilan birgalikda Mobil dasturlash sohasidagi qiziq va kuzatuvchilar tomonidan so’ralgan mavzular suhbat ko’rinishida ochib beriladi. ❓Suhbat davomida siz oʻzingizni qiziqtirgan savollarni comment yoki live chat bo'limida berib ustozlar tomonidan javob olishingiz mumkin. 📌 Mavzu: Trending topics in Mobile 👨‍💻Suhbat ishtirokchilari: Jakhongir Madaminov, Sanjar Suvonov, Shaxzod Ilxomov 👉 TOMOSHA QILING @mobilers_uz

⌨️ "Typist" bo'lmasangiz ham dasturchi bo'lsangiz hech bo'lmaganda 41 WPM (Words Per Minute) dan yuqori bo'lishingiz kerak. ========= 📁 Mana mashq qilish uchun manbalar: 📚 O'rganish uchun juda zo'r: https://www.keybr.com/ 🤼‍♂️ Bellashish uchun yaxshilari: https://typer.io/ https://play.typeracer.com/ ⏱ Test qilish uchun zo'rlari: https://www.typing.com/student/typing-test/1-minute (Recruiterlar shuni ishlatisharmush) https://www.livechat.com/typing-speed-test/#/ #coder #typist @flutterblogs

Flutter | vs Native, Interview jarayonlari, Shaxmat. Hamidjon Egamov. (debug podcast #11)

Iqtibos: "Front-End har doim "tupoy" bo'lishi kerak" - Ulug'bek Samigjonov

Online ko'ring: https://youtu.be/nlZRG-It6uk #interview #debug #podcast @flutterblogs

Dasturchilar uchun 10 ta tavsiya! Men, bir-qancha tajribasi bor dasturchi sifatida, sizlarga foydali bo'lishi mumkin bo'lgan tavsiyalar bermoqchiman. Sizning tajribangiz qanchalik ko'p bo'lsa, quyidagi keltirilgan tavsiyalarning shuncha ko'pi sizga haqiqiy va banal ko'rinadi. Dasturlash sohasiga endi kirib kelayotgan dasturchilar uchun esa bu tavsiyalar juda g'alati tuyulishi mumkin. Tavsiyalar 1. Faqat sizga hozirgi vaqtda kerak bo'ladigan kod yozing (YAGNI printsipi) Ishlatilmaydigan kod quyidagi fikrlar asosida paydo bo'ladi. - "Kelajakda bu funksional menga albatta as qotadi. Uni hozir yaratib qo'ysam-chi?" - "Quyidagi abstraktsiya bu funksional tugallanmagan ko'rinadi. Shuning uchun uni hozir yaratib qoyganim maqul" Ortiqcha kod quyidagi muamolar yaratadi: - Uning aksariyat qismi baribir ishlatilmaydi - Bunday kodni o'qish va o'rganish ortiqcha vaqt oladi - Ancha vaqtdan beri ishlatilmaydigan kod, shu vaqtning ichida o'zgarib kelgan loyihaning holatiga to'g'ri kelmaydi 2. Eskirgan kodni shavqatsiz yo'q qiling Eskirgan kod - bu proyekt rivojlanishi mobaynida yaroqsiz holatga kelgan funksionaldir. Agar siz bu kodni kelajakda ishlatish umidida saqlayotgan bo'lsangiz, shuni biling-ki, aksariyat holatlarda uni qaytatdan yozish ham vaqt ham harajatni tejaydi. Boz ustiga, sizga kerak bolib qolishi mumkin bo'lga istalgan kodni GIT kabi versiyalarni boshqarish tizimidan olishingiz mumkin. Umid qilaman, siz bunday tizimdan foydalanasiz. 3. Yangi loyihani minimal funksional bilan boshlang (Minimum viable product) Muvaffaqiyatli loyiha, qancha to'sqinlik qilmang albatta mayda "ikr-chikir"lar bilan qoplanib ketadi. Agar yangi loyihada, siz birdaniga minglab funksiyalarni yaratsangiz, bu loyiha hech qachon ishga tushmasligi imkoniyati juda baland. 4. Refaktoring qilib turishni unutmang Har bir muvaffaqiyatli loyihaga hos xususiyat bu uning davomiy rivojlanishi. Bu jarayon mobaynida unga ko'plab yangi kod qo'shiladi. Shu sababli loyiha muvaffaqiyatligini faqatgina shu kodni refaktoring qilish bilan saqlab turish mumkin. Agar bu ish qilinmasa, vaqt o'tishi bilan, yozilgan kodni kengaytirish imkoniyati yo'qoladi va natijada loyiha bir joyda to'xtaydi. 5. Sodda yechimlarni, murakkab yechimlardan ustun qo'ying (KISS printsipi) Sodda yechimlarni tushunish, kengaytirish va debug qilish osonroq. Loyihalaringizni arxitekturasini qiyinlashtirishga emas, soddalashtirishga uruning. 6. Sodda va tushunarli kod, genial va murakkab koddan yaxshiroq Murrakab logika va arxitektura yordamida yozgan kodingizni kelajakda tushunishi, optimizatsiya qilishni va kengaytirishni kerak bo'ladigan dasturchilar haqida o'ylang. Bu dasturchiga yarim yildan keyin o'zingiz aylanishingiz mumkin:) Kerak bo'lmagan joyda turli xil dasturiy tamoyillarni, arxitektura shablonlarini, dasturiy tillarning yangi xususiyatlarini v.k. ishlatishga urunmang, chunki bu kodingizga ortiqcha murakkablik qo'shadi. 7. Loyiha arxitekturasini mayda funksiyalargacha boshida o'ylab chiqishga urunmang. "Ideal arxitekturani" o'ylab chiqishga 1 oy ketkazishdan ko'ra, ishlayotgan, lekin kichik nuqsonlari bor prototipni yaratishga bir-ikki kun ajratgan yaxshi. Tajribaga asosan, ikkala holatda xam loyihaga ko'plab o'zgarishlar kiritiladi va o'ylangan arxitektura yaroqsiz holatga kelib qolishi mumkin. 8. Copy-pastedan qo'rqmang. Qaytariluvchi kodni, uning yaroqliligini isbotlagach, alohida funksiyalarga o'girish mumkin. 9. Kod asta ishlashni boshlamaguncha, uni optimizatsiya qilishga ko'p etibor bermang. Optimizatsiya qilinishi mobaynida o'zgargan kod tushunarsiz holatga kelib qolishi mumkin. Boz ustiga, bu kod, loyihaning umumiy tezligiga, ko'pincha, juda kam ta'sir ko'rsatadi. 10. Bitta universal va 10 ga yaqin parametrlarni qabul qiluvchi funksiyadan, 10 ta kichik va sodda funksiya afzalroq. Funksiyangizda qancha ko'p parametr bo'lsa, uni ishlatish, kengaytirish va refaktoring qilish shuncha qiyinlashadi. Shuning uchun funksiyalarni iloji boricha sodda va ixcham qilib yarating. #suggestion @flutteerblogs