Hayitbek Yusupov - IT Blog

- React XSS hujumlardan qanday himoyalanadi? - XSS hujumlardan himoyalanish uchun best practicelar https://overreacted.io/why-do-react-elements-have-typeof-property/ https://gomakethings.com/how-to-sanitize-third-party-content-with-vanilla-js-to-prevent-cross-site-scripting-xss-attacks/

- React.useState() aslida qanday ishlaydi? - React.useState() DOM ni qanday update qiladi? - react-dom, react-dom/server, react-native kabi packagelar o'zi nega kerak? https://overreacted.io/how-does-setstate-know-what-to-do/

https://tkdodo.eu/blog https://blog.webdevsimplified.com https://overreacted.io https://www.totaltypescript.com/articles

I hate javascript

Credits to @muminovbob

😆

xullas yosh = 20;

agar(yosh > 18){
  korsat("Mumkin");
}
yemasa(yosh > 12){
  korsat("Ozgina bor");
}
oxiri{
  korsat("Kichkinasanu ukam");
}

If you ask the business managers if they want to be able to make changes, they'll say that of course they do, but may then qualify their answer by noting that the current functionality is more important than any later flexibility. In contrast, if the business managers ask you for a change, and your estimated costs for that change are unaffordably high, the business managers will likely be furious that you allowed the system to get to the point where the change was impractical #clean_architecture

If you give me a program that works perfectly but is impossible to change, then it won't work when the requirements change, and I won't be able to make it work. Therefore the program will become useless. If you give me a program that does not work but is easy to change, then I can make it work, and keep it working as requirements change. Therefore the program will remain continually useful #clean_architecture

Software was invented to be soft. It was intended to be a way to easily change the behavior of machines. If we'd wanted the behavior of machines to be hard to change, we would have called it hardware #clean_architecture

Tauridagi footgunlardan biri Taurida system trayga icon qo'shish tauri.conf.json fayli orqali, yoki system tray plugini orqali amalga oshiriladi. Agar siz ikkalasini ham ishlatsangiz macos & windowsda ikkita tray icon yaratib qo'yadi, linuxda esa bir marta yaratadi #tauri

Agar siz toza arxitekturaning narxi qimmatga tushadi deb o'ylasangiz, yomon arxitekturani sinab ko'ring

Yaqinda bir loyihada shu holatga duch keldim. Menejerlar bizga falon loyihani kichkina mvp versiyasini chiqarib berib, ko'rsatishimiz kerak deyishdi. Shu sababdan, ha mayli bu axir mvp ku deb monolit arxitekturada loyihani yozishni boshladik. Ishonasizmi, shu mvp deyilgan loyiha hali ham davom etayapti. Axir bu mvp ku deganimga ming pushaymon yeyapman. Bu mvp avgust oxirida boshlangan bo'lsa, haligacha davom etayapti. 2-2.5 oy ichida codebase ham ancha kattalashdi. Lekin, baribir vaqt ajratib, loyihani FSD arxitekturasiga olib chiqdim va ahvol bir muncha yaxshilandi. Lekin baribir, ildizidan to'g'ri o'smagan daraxtni parvarishlash qiyin kechar ekan #clean_architecture

Clean Architecture Kitobni o'qishni boshlab oldim. Kirish qismini o'zidayoq muallif yaxshi bir fikr aytgan: agar 1970-yillardagi dasturchini hozirgi kunga olib kelib, birorta zamonaviy dasturlash tilida kod yozib ber desangiz, 24 soat shok holatda bo'lishi mumkin, ammo sekin-sekinlik bilan baribir moslashadi. Xuddi shunday, agar 2024-yilda yashayotgan dasturchini 1970-yilga olib borib kod yozdirsangiz, 24 soat shok holatida bo'lishi mumkin, lekin baribir moslashadi. Bunga sabab shuki, dasturlash tillari rivojlanib borayotgan bo'lsa ham, ulardagi fundamental tushunchalar bir xil. Shu sababli ham, aynan bironta framework, dasturlash tiliga yopishib olmasdan, fundamental tushunchalarni kuchaytirish kerak ekan. #clean_architecture @khaitbekdev

https://globbing.com orqali anchadan beri o'zim qiziqib kelayotgan kitoblarimdan biri - Clean Architecture kitobini Amazondan sotib oldim. Yilni so'nggiga qadar asosan fokusni shu kitobga qaratmoqchiman. Bu degani boshqa mavzularga fokusni qarata olmasligim, yoki kam qaratishim mumkin. Bir vaqtni o'zida bir nechta narsaga fokusni qaratish uncha foydali bo'lmadi. Lekin, bir vaqtni o'zida bir nechta narsaga fokus qaratmasam ham, har kuni oz-oz dan fokus qaratishim kerak bo'lgan narsalarga vaqt ajratmoqchiman. Masalan kuniga hech bo'lmasa 30 daqiqa Leetcodeda masala ishlash. Masalani 30 daqiqa ichida ishlay olishim muhim emas, muhimi davomiylik. Clean Architecture kitobini tugatganimdan so'ng boshqa muhimroq narsaga asosiy fokusni qarataman. Ya'ni 2-3ta eng kerakli jabhalarga e'tiborni qaratib, boshqa kerakli ammo muhimligi u darajada yuqori bo'lmagan jabhalarni sekin-sekinlik bilan rivojlantirib boraman. Albatta bu usulni Cal Newportning podkastlaridan birida eshitdim. Cal Newport Slow Productivity degan kitob yozayotgan ekan, shu yil qishda sotuvga chiqadi deb aytyabdi. Olib o'qish kerak bo'lgan kitoblardan biri. Zero vaqtimiz eng qimmat resursimiz