ចូលបណ្តាញសង្គមរបស់យើង
អត្ថបទថ្មីៗបំផុត
មើលអត្ថបទទាំងអស់
ហេតុអ្វី Supply Chain Attacks ក្លាយជាហានិភ័យធំបំផុតសម្រាប់សុវត្ថិភាព Software
ស្វែងយល់ពី supply chain attacks វាធ្វើការយ៉ាងម៉េច និងហេតុអ្វីវាជាហានិភ័យធំបំផុតសម្រាប់សុវត្ថិភាព software
Frontend សម័យឥឡូវ៖ លើសពីការធ្វើ UI គឺការយល់ដឹងពី System ទាំងមូល
ស្វែងយល់ពីការវិវត្តនៃ Frontend Engineering ដែលកំពុងក្លាយជា Full-stack។ ហេតុអ្វីបានជា Framework ដូចជា Next.js ផ្លាស់ប្តូរតួនាទីរបស់យើងពីអ្នកឌីហ្សាញ Layout មកជាអ្នកគ្រប់គ្រង Infrastructure និងយុទ្ធសាស្ត្រ Backend?
សិក្សា Framework មិនបានធានាថាអ្នកនឹងមានការងារបានទេ
ស្វែងយល់ពីអ្វីទៅជា Framework និងហេតុអ្វីបានជា ការសិក្សា Framework ដោយខ្លួនឯងមិនគ្រប់គ្រាន់ដើម្បីធានាថាអ្នកនឹងមានការងារបាននៅក្នុងក្រុមហ៊ុន IT ទេ។
វីដេអូថ្មីៗបំផុត
មើលវីដេអូទាំងអស់
ចំណាយ $0 លើ ChatGPT ! បង្កើត AI Agent ប្រើលើ Server ខ្លួនឯង (Local LLM) ជួយខ្ញុំគ្រប់គ្រង Server
ចំណាយ $0 លើ ChatGPT ! បង្កើត AI Agent ប្រើលើ Server ខ្លួនឯង (Local LLM) ជួយខ្ញុំគ្រប់គ្រង Server 🚀 ព័ត៌មានវគ្គសិក្សា Full-stack Development Bootcamp (ជំនាន់ទី៧): https://t.me/tfdTech/278 📚 វគ្គសិក្សា Data Science & AI ៖ https://t.me/tfdTech/236 🔗 ចូលរួមក្រុម Telegram របស់ខ្ញុំ៖ https://t.me/tfdTech នៅក្នុងវីដេអូនេះ ខ្ញុំនឹងបង្ហាញអ្នកទាំងអស់គ្នាអំពីរបៀបបង្កើត AI Agent ផ្ទាល់ខ្លួន ដើម្បីតាមដានសុខភាព Server (Home Lab) ដោយមិនចាំបាច់ចំណាយលុយលើ API Key របស់ ChatGPT ឬ Google Gemini ឡើយ។ In this video, I demonstrate how to build and deploy a local AI agent specifically designed to monitor Home Lab server health without spending a single cent on external API keys like ChatGPT or Gemini. យើងនឹងសិក្សាអំពីការប្រើប្រាស់ Ollama ដើម្បី Run Model តូចៗដូចជា IBM Granite 3.3 2B, Google Gemma 2 2B, និង TinyLlama 1B។ ខ្ញុំនឹងបង្ហាញពីរបៀបដែល AI យល់ពីសំណួររបស់យើង (Intent Classification) ហើយទៅទាញយកទិន្នន័យពី Server ដូចជា CPU, RAM និង Storage មកប្រាប់យើងតាមរយៈ Telegram បែបសង្ខេប និងឆ្លាតវៃ។ We explore the architecture using an AI VM running Ollama and compare three "Tiny LLMs": IBM Granite 3.3 2B, Google Gemma 2 2B, and TinyLlama 1B. You will see how we use these models as "Intent Classifiers" to turn Telegram questions into real-time server data (CPU usage, RAM, and Storage). We also discuss the challenge of "Hallucinations" in small models and why some models perform better than others for technical tasks. IG: https://www.instagram.com/darachaukh/ YouTube: https://youtube.com/@tfdevs Website: https://www.tfdevs.com/ Linkedin: https://www.linkedin.com/in/qiang-cun-zhi/ TikTok: https://www.tiktok.com/@chaudarakh?_r=1&_t=ZS-91PipW1NUEU Telegram Channel: https://t.me/tfdTech Facebook Page: https://www.facebook.com/ChauDaraScienceEngineer 00:00 Introduction: AI summarizing Home Lab status 00:22 The benefits of AI in Home Lab monitoring 01:10 Building an AI Agent for free (No API keys) 01:36 Special Promotion: Full-stack Development Bootcamp Gen 7 02:25 Architecture: AI VM and Ollama Runtime setup 03:45 Using LLMs as "Intent Classifiers" 04:53 Workflow: From Telegram question to API data 06:19 Comparing Tiny LLMs: IBM Granite vs. Google Gemma vs. TinyLlama 07:48 Understanding AI Hallucinations in small models 08:31 Live Testing: Why TinyLlama 1B struggled 09:40 Live Testing: IBM Granite success with CPU & Storage 10:52 Live Testing: Google Gemma 2 performance 11:51 Conclusion: Privacy and cost-saving advantages
ហេតុអ្វី Website ដើរយឺត? តោះស្វែងយល់ពី SSR និង CSR! | Server Side vs Client Side Rendering | TFDevs
ហេតុអ្វី Website ដើរយឺត? តោះស្វែងយល់ពី SSR និង CSR! | TFDevs តើអ្នកធ្លាប់ឆ្ងល់ទេថា ហេតុអ្វីបានជា Website ខ្លះចូលទៅឃើញ Screen ពណ៌សរង់ចាំយូរ ហើយខ្លះទៀតចូលទៅឃើញ Content ភ្លាម? នោះគឺដោយសារបច្ចេកទេស Rendering។ វីដេអូនេះនឹងបង្ហាញអ្នកពីដំណោះស្រាយដើម្បីធ្វើឱ្យ Website លឿន និងមានប្រសិទ្ធភាពបំផុត។ Ever wondered why some websites show a blank white screen while loading, while others appear instantly? It all comes down to the rendering strategy. We dive deep into SSR and CSR to show you how to build faster, smoother web experiences for your users. កុំភ្លេចចុច Subscribe ដើម្បីតាមដានវីដេអូថ្មីៗអំពីបច្ចេកវិទ្យា និងការសរសេរកូដ! 🔗 ចូលរួមក្រុម Telegram របស់ខ្ញុំ៖ https://t.me/tfdTech 📚 វគ្គសិក្សា Full-stack: https://t.me/tfdTech/278 📚 វគ្គសិក្សា Data Science & AI ៖ https://t.me/tfdTech/236 This video provides a clear and practical comparison between Server-Side Rendering (SSR) and Client-Side Rendering (CSR), the two primary methods for displaying content on the web. Hosted by Chhunny, the tutorial uses a simple analogy to help developers choose the right architecture for their projects. 1. The Core Analogy To make the concepts easy to understand, the speaker compares them to dining experiences: SSR (The Restaurant): Like a restaurant where you order food and it arrives fully cooked and ready to eat. The server (kitchen) does all the work before the food reaches your table. CSR (The Hotpot/Grill): Like a hotpot or BBQ place where the server brings you raw ingredients (code), and you have to cook it yourself (the browser executes the code) before you can eat. 2. Technical Differences SSR (Server-Side Rendering): How it works: When a user requests a page, the server prepares the full HTML file (including data from databases or APIs) and sends it to the browser. SEO: Excellent. Search engines like Google can easily "read" the content because the HTML is fully populated. Speed: Fast "First Contentful Paint" (users see content quickly), but it can be taxing on the server. Frameworks: Next.js, Nuxt.js. CSR (Client-Side Rendering): How it works: The server sends a nearly empty HTML file and a large JavaScript bundle. The user's browser then executes that JavaScript to fetch data and build the page. SEO: Difficult. Search engine crawlers often see an "empty" page because the content isn't there until the JavaScript runs. Speed: Faster "Time to First Byte" (the initial response is quick), but users often see a "white screen" while the browser cooks the data. Frameworks: React.js, Vue.js. 3. Performance Comparison The video breaks down key metrics: SEO: SSR wins because the content is visible in the source code. Server Load: CSR wins because the server only hosts static files, whereas SSR requires the server to render pages for every single request. Interactivity: SSR pages are interactive almost immediately, while CSR requires the full JavaScript bundle to be downloaded and executed first. 4. Practical Demonstration The speaker demonstrates a "Live Test" by disabling JavaScript in the browser: CSR Website: Becomes a blank page (it fails because it relies entirely on the browser's JavaScript "cooking"). SSR Website: Still displays all text and images (it succeeds because the server already "cooked" the page). Conclusion: Which should you choose? Choose SSR if you are building a public website where SEO and fast initial loading are critical (e.g., E-commerce, Blogs, News sites). Choose CSR if you are building Internal Tools, Dashboards, or web apps where SEO doesn't matter and you want to save on server costs. 00:00 - Introduction to SSR & CSR 00:54 - The Restaurant & Hotpot Analogy 02:15 - How SSR (Server-Side Rendering) Works 02:52 - How CSR (Client-Side Rendering) Works 05:10 - Key Metrics: TTFB, FCP & SEO 06:45 - Server Load Comparison 08:30 - When to use SSR vs CSR 10:50 - Live Demo: Disabling JavaScript Test 12:15 - Conclusion IG: https://www.instagram.com/darachaukh/ YouTube: https://youtube.com/@tfdevs Website: https://www.tfdevs.com/ Linkedin: https://www.linkedin.com/in/qiang-cun-zhi/ TikTok: https://www.tiktok.com/@chaudarakh?_r=1&_t=ZS-91PipW1NUEU Telegram Channel: https://t.me/tfdTech Facebook Page: https://www.facebook.com/ChauDaraScienceEngineer #WebDev #SSR #CSR #NextJS #ReactJS #SEO #KhmerDeveloper #ProgrammingKhmer #TechCambodia #FullstackDevelopment
AI កំពុងធ្វើឱ្យការ Hack កាន់តែស្រួល! Vercel ត្រូវបានគេ Hack? រឿងដែល Developer ត្រូវដឹងដើម្បីការពារ
AI កំពុងធ្វើឱ្យការ Hack កាន់តែស្រួល! Vercel ត្រូវបានគេ Hack? រឿងដែល Developer ត្រូវដឹងដើម្បីការពារ តើអ្នកកំពុងពឹងផ្អែកទាំងស្រុងលើ Vercel មែនទេ? បន្ទាប់ពីមានករណី Security Hack កាលពីពេលថ្មីៗនេះ យើងត្រូវងាកមកមើលពីសារៈសំខាន់នៃការយល់ដឹងពី Infrastructure ឬការរៀបចំ Server ដោយខ្លួនឯងវិញ។ In light of recent security concerns with platforms like Vercel, it’s time to talk about why "easy" hosting isn't always "safe" hosting. In this video, we discuss how AI is lowering the barrier for hackers and why every developer should master their own infrastructure. កុំភ្លេចចុច Subscribe ដើម្បីតាមដានវីដេអូថ្មីៗអំពីបច្ចេកវិទ្យា និងការសរសេរកូដ! 🔗 ចូលរួមក្រុម Telegram របស់ខ្ញុំ៖ https://t.me/tfdTech 📚 វគ្គសិក្សា Full-stack: https://t.me/tfdTech/235 📚 វគ្គសិក្សា Data Science & AI ៖ https://t.me/tfdTech/236 ចំណុចសំខាន់ៗក្នុងវីដេអូ៖ ១. ករណី Vercel Hack: តើវាប៉ះពាល់ដល់ Developer យ៉ាងដូចម្តេច? ២. AI និងការ Hack: របៀបដែល AI ជួយឱ្យ Hacker ងាយស្រួលរកចន្លោះប្រហោង។ ៣. ហេតុអ្វីត្រូវរៀន Server: សារៈសំខាន់នៃការយល់ពី Docker, K8s, Nginx និង SSL។ ៤. តិកនិកសុវត្ថិភាព: * ការប្តូរ (Rotate) Environment Variables ជាប្រចាំ។ * ការកំណត់សិទ្ធិប្រើប្រាស់ (Principle of Least Privilege)។ * ការការពារ (Encrypt) ទិន្នន័យសំខាន់ៗក្នុង System។ ៥. ការគ្រប់គ្រង Server ខ្លួនឯង: ហេតុអ្វីបានជាខ្ញុំសម្រេចចិត្តប្រើ HomeLab ដើម្បីសុវត្ថិភាពខ្ពស់។ កុំគ្រាន់តែចេះសរសេរកូដ ត្រូវយល់ពីរបៀបការពារ Project របស់អ្នកឱ្យបានរឹងមាំផងដែរ។ IG: https://www.instagram.com/darachaukh/ YouTube: https://youtube.com/@tfdevs Website: https://www.tfdevs.com/ Linkedin: https://www.linkedin.com/in/qiang-cun-zhi/ TikTok: https://www.tiktok.com/@chaudarakh?_r=1&_t=ZS-91PipW1NUEU Telegram Channel: https://t.me/tfdTech Facebook Page: https://www.facebook.com/ChauDaraScienceEngineer