ts-node -> tsx

Node bilan ishlovchi dasturchilarga ts-node o'rniga tsx ishlatishlarini tavsiya qilaman. Ustunlik tomonlari:
- .env faylni ozi oqiy oladi, dotenv kerak bolmaydi
- watch mode bilan keladi, nodemonga ehtiyoj yoq
- esm support bilan keladi, SyntaxError: Cannot use import statement outside a module kabi xatolarga duch kelinmaydi

https://tsx.is

"Full-stack step by step" darslarimizni boshlab oldik, alhamdulillah. Darslarga linklarni kanalda ulashib va mana shu youtube playlistga qoshib boramiz, in shaa Alloh.

https://www.youtube.com/playlist?list=PLn8TR1nMED9YoOkLu8sPOOmEYcjW0Qr9b

"What is software architecture?" degan savolga berilgan javoblar:

⁃ “Architecture is about the important stuff. Whatever that is.” - Ralph Johnson

⁃ “Software architecture is the set of design decisions that, if made incorrectly, may cause your project to be cancelled.” - Eoin Woods

⁃ The process of defining a structured solution that meets all of the technical and operational requirements

⁃ The set of structures needed to reason about the system, which comprises software elements, relations among them, and properties of both

⁃ Software architecture is a set of characteristics that combine technical and business requirements

Sizningcha qaysi izoh terminni yaxshiroq yoki toliqroq ifodalaydi?

Quotelar "Software architectures for web developers" kitobidan olingan.

"Use case"lar

Biron yangi narsa o'rganganda har doim shu 2 savolni berishga odatlaning:
1) Buni qayerda apply qilishim mumkin (where)
2) Qanday apply qilishim mumkin (how)
Bu tushuncha dasturlashda (umuman har sohada) use case deb ataladi. Agar shunga javob bera olmasangiz bu o'rgangan narsangizni tez esdan chiqarasiz yoki qayerda ishlatishni bilmaysiz. O'rganayotgan manbaning ahamiyati yo'q, kitobdan yoki postdan oqiyapsiz mi, videoda yoki kursda ko'rdingiz mi, jamoadoshiz aytdi mi, buning "use case"lari qanday degan savol bering. Shunda uzoqroq muddat eslab qolishiz mumkin. Inson miyasi o'ziga kerak bo'lmagan malumotlarni garbage collect qiladi 😀 (o'zim to'qidim, lekin tajribadan)

PS: kanalda yoki shaxsiydan juda ko’p nimani o'rganish haqida savol kelib tushadi, bu savollarga umumiy javob berish juda qiyin, chunki har kimda holat individual bo'ladi. Bazan dasturchilar qaysidir ro'yhatlardan o'rganmoqchi bo'lishadi. Bir narsani esdan chiqarmaslik kerak, bu ro'yhatlar general, kimdadir ish beradi, kimdadir bermaydi. O'rganmoqchi bo'lgan narsalarni to'g'ri prioretlashtiring, eng boshida eng ehtiyojiz ko'p tushayotgan narsalarni qo'ying

Will AI replace humans?

It's been 24 months since the release of ChatGPT.

And don't get me wrong: AI has been a gamechanger. I use it daily to help me design solutions, autocomplete code and fix bugs.

But I'm also incredibly tired of the "in 6 months we won't need developers, AI can just do everything". We've been hearing that for 2 years, and yet here we are.

The idea that AI will replace developers assume that the amount of software we need in the world is fixed - and so if AI can help us get there twice as fast, we'll only need half as many devs.

But that premise is wrong. As technology keeps getting more advanced, there's an endless stream of software that will need to be built. And no matter how good AI gets, there will always be someone who needs to instruct it and know when it's going off track or runs into a problem it can't solve on its own.

The better way to look at is that if AI can speed up a single developer by 100%, the same amount of devs will just be able to produce twice as much software in the same amount of time. That's a net win for everybody!

My point is, I wouldn't be scared if you're currently learning to code. It's true that AI will (and already is) capable of building a lot of useful stuff almost entirely on its own. But that "almost" is key, and I don't foresee that changing any time soon

Manba: linkedin