<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Sajan Nepali on Medium]]></title>
        <description><![CDATA[Stories by Sajan Nepali on Medium]]></description>
        <link>https://medium.com/@read.sajan.blog?source=rss-cfaa77925930------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*NZFyqxcjO1yEFZSz</url>
            <title>Stories by Sajan Nepali on Medium</title>
            <link>https://medium.com/@read.sajan.blog?source=rss-cfaa77925930------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:50:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@read.sajan.blog/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How AI is Reshaping the developer workflow]]></title>
            <link>https://medium.com/@read.sajan.blog/how-ai-is-reshaping-the-developer-workflow-b4e6e3a3c95a?source=rss-cfaa77925930------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4e6e3a3c95a</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[code-generation]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[development-process]]></category>
            <dc:creator><![CDATA[Sajan Nepali]]></dc:creator>
            <pubDate>Sun, 06 Jul 2025 08:40:47 GMT</pubDate>
            <atom:updated>2025-07-06T08:40:47.712Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="AI Tools for developer workflow" src="https://cdn-images-1.medium.com/max/980/0*Pq1C1pP7_TNFBHRh.png" /></figure><p>Remember when the biggest productivity hack was learning keyboard shortcuts? It felt like magic editing multiple line of code at once. Those days are officially over. AI isn’t just changing how we code it is rewriting entire process.</p><p>Previously developer workflow used to look like this: Think → Google → Stack Overflow → Copy → Paste → Debug → Repeat. Now it’s more like: Think → Ask AI → Review → Ship. It has changed the fundamentals how code is written, tested and maintained. While challenges remain, the potential benefits of increased productivity, improved code quality and reduced development time are driving widespread adoption across the industry. People are getting afraid that they will be replaced by AI but it’s not about the it is about increasing developer capabilities to create better software faster and more reliably than ever before. Its the next chapter in the ongoing evolution of software development.</p><p>Here are some of AI Coding tools that has really helped me ship features faster.</p><h3>AI Powered Code Completion and Generation</h3><h4>Github Copilot: The Swiss Army Knife</h4><figure><img alt="Github Copilot Logo" src="https://cdn-images-1.medium.com/max/334/0*ow5iPApqJZhnyM08" /></figure><p><strong>Free Tier Details:</strong></p><ul><li><strong>2,000 code completions per month</strong> (about 80 per working day)</li><li><strong>50 chat requests per month</strong> (including Copilot Edits)</li><li>Access to both GPT-4o and Claude 3.5 Sonnet models</li><li>Available directly in VS Code with your GitHub account</li><li>Students, teachers, and open-source maintainers get free Pro access</li></ul><h4>Cursor: The IDE That Thinks</h4><figure><img alt="Cursor AI Logo Image" src="https://cdn-images-1.medium.com/max/1024/0*dr7nUMLS1O3k11Li" /></figure><p><strong>Free Tier Details:</strong></p><ul><li><strong>Basic code completions</strong> (unlimited)</li><li><strong>Limited AI chat</strong> (around 50 queries per month)</li><li>Access to standard AI models for basic suggestions</li><li><strong>Upgrade required</strong> for advanced features like Agent mode, code refactoring, and premium models</li><li><strong>Pro Plan</strong>: $20/month for 500 fast premium requests + unlimited completions</li></ul><h4>Tabnine: The Predictive Powerhouse</h4><figure><img alt="Tabnine Logo" src="https://cdn-images-1.medium.com/max/410/0*lqS-3IquOInSDh5d" /></figure><p><strong>Free Tier Details (Tabnine Basic):</strong></p><ul><li><strong>Unlimited code completions</strong> using basic AI models</li><li><strong>Basic personalization</strong> that learns your coding style</li><li><strong>Local processing</strong> — your code never leaves your machine</li><li><strong>Access to Claude 3.5 Sonnet</strong> for completions</li><li><strong>Multi-language support</strong> (30+ programming languages)</li><li><strong>Recent upgrade</strong>: Now includes more AI agents and advanced personalization features</li></ul><p><strong>Why developers love it</strong>: Tabnine runs locally, so your proprietary code never leaves your machine. Plus, it supports over 30 programming languages and integrates with virtually every IDE.</p><h4>Amazon CodeWhisperer: The Enterprise Beast</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*Rwb6kYCnOgYTh0UO.png" /></figure><p><strong>Free Tier Details:</strong></p><ul><li><strong>Individual Tier</strong>: Completely free for solo developers</li><li><strong>Unlimited code suggestions</strong> for supported languages</li><li><strong>Basic security scanning</strong> to detect vulnerabilities</li><li><strong>Professional Tier</strong>: Paid version with organization-level features</li><li><strong>No monthly limits</strong> on the free individual tier</li></ul><p><strong>Enterprise advantage</strong>: Comes with legal protection against copyright claims and integrates seamlessly with AWS services.</p><h3>AI Powered Code Reviews</h3><p><strong>CodeRabbit</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FkOta9KEW1UGn8vm.png" /></figure><p>Provides contextual code review comments, understands code intent, and suggests improvements</p><p><strong>Free Tier Details:</strong></p><ul><li>Limited to public repositories, basic review features</li><li>PR Summarization</li></ul><p><strong>Codacy</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/425/0*fekih3vTIArYB8wT" /></figure><p>AI-driven code quality analysis across multiple languages</p><p><strong>Free Tier Details:</strong></p><ul><li>Limited to 4 private repositories, basic quality gates</li><li>One-click integration with VSCode, Cursor and Windsurf</li><li>Supports TypeScript, JavaScript, Python &amp; Java</li></ul><h3>Automated Testing and Quality Gates</h3><p><strong>Testim</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/364/0*-hGF041PBn0BvF24.jpg" /></figure><p>AI-powered test automation that adapts to UI changes</p><p><strong>Free Tier Details:</strong></p><ul><li>Limited test runs per month, basic test creation</li><li>Blazing fast test creation using AI</li><li>Explain identifies and simplify debug</li></ul><p><strong>Mabl</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/0*8UTRD2SqlzSZXFQC" /></figure><p>Intelligent test automation with self-healing capabilities</p><p><strong>Free Tier Details:</strong></p><ul><li>End to End UI and API testing for web apps</li><li>Unlimited local and CI and parallel runs</li><li>Adaptive auto healing with GenAI</li><li>Web, Mobile and CLI support</li><li>Limited test runs, basic browser testing only</li></ul><p><strong>Qodo( Previously Codium)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kf4iuVX1-3oFEXK0" /></figure><p><strong>Free Tier Details:</strong></p><ul><li>Code review and automated test detection</li><li>Generate Code documentation</li><li>Quality unit and component tests generation</li></ul><p><strong>whybug: Debugging and Problem Resolution</strong></p><p>Conversational debugging that explains error messages, you can write your error message and get a detailed explanation with suggested fixes</p><h3>MintLify and Swimm: Documentation That Writes Itself</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GlQ4v5OBia3SCemj.png" /></figure><p>Generates comprehensive documentation form your code. They understand function purposes, parameter meanings, and even create usage examples. The documentation stays updated as your code evolves. We saved over 8 hours per week on documentation tasks alone.</p><p><strong>Free Tier Details:</strong></p><ul><li>Free of single editor, with git sync</li><li>Supports API playground, React Components and has Web editor support</li></ul><h3>How to improve your workflow</h3><h4>Start Small, Think Big</h4><ol><li><strong>Pick one tool</strong> and master it. Don’t try to adopt everything at once.</li><li><strong>Question everything</strong> the AI suggests. Trust, but verify.</li><li><strong>Learn from the AI</strong>. Pay attention to the patterns and techniques it uses.</li><li><strong>Share your experiences</strong>. The AI coding community is incredibly collaborative.</li></ol><h4>The New Skills You Need</h4><ul><li><strong>Prompt engineering</strong>: Learning how to communicate effectively with AI</li><li><strong>AI code review</strong>: Understanding how to evaluate AI-generated code</li><li><strong>Tool integration</strong>: Knowing how to chain AI tools together for maximum productivity</li></ul><p>The developers incorporating AI to their workflow aren’t just becoming more productive but more creative, more ambitious and frankly I more excited about coding than ever in years.</p><p>What’s your experience with AI Coding Tools? Have you found your new favorite AI assistant? Share in the comments, the future of coding is changing and we must adapt to it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4e6e3a3c95a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[20 React Libraries That Will Get You Hired in 2025]]></title>
            <link>https://medium.com/@read.sajan.blog/20-react-libraries-that-will-save-you-hours-of-development-time-in-2025-8086a22551e9?source=rss-cfaa77925930------2</link>
            <guid isPermaLink="false">https://medium.com/p/8086a22551e9</guid>
            <category><![CDATA[industry-practices]]></category>
            <category><![CDATA[medium]]></category>
            <category><![CDATA[react-libraries]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[react-native]]></category>
            <dc:creator><![CDATA[Sajan Nepali]]></dc:creator>
            <pubDate>Wed, 22 Jan 2025 04:44:50 GMT</pubDate>
            <atom:updated>2025-01-22T13:20:23.815Z</atom:updated>
            <content:encoded><![CDATA[<h3>20 React Libraries That will Get You Hired in 2025</h3><ol><li><strong>nx / npm workspace</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BmBRqAFR3_9n5YXc.png" /></figure><p>What it does: Think of it as a smart project manager that helps you organize multiple apps and packages in one repository. If you are project doesn’t have multiple apps it may not be suitable for you. Also setup is tedious not worth time spending setting it up for small scale project.</p><p>Learning Resources:</p><ul><li>Official Documentation: <a href="https://nx.dev/getting-started/intro">https://nx.dev/getting-started/intro</a></li><li>Tutorial Article: <a href="https://nevra.medium.com/setting-up-a-full-stack-web-application-using-nx-workspace-4b035bb63a80">https://nevra.medium.com/setting-up-a-full-stack-web-application-using-nx-workspace-4b035bb63a80</a></li><li>YouTube Tutorial: “Nx Tutorial — Nx Workspace for React Applications” by Nrwl: <a href="https://www.youtube.com/watch?v=E188J7E_MDU">https://www.youtube.com/watch?v=E188J7E_MDU</a></li></ul><p><strong>2. Eslint</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*M9cIyYeezuzr5cFN.png" /></figure><p>What it does: Like a strict teacher that checks your code for mistakes and style issues.</p><p>Learning Resources:</p><ul><li>Official Guide: <a href="https://eslint.org/docs/user-guide/getting-started">https://eslint.org/docs/user-guide/getting-started</a></li><li>YouTube: “ESLint + Prettier + TypeScript Setup” by Ben Awad: <a href="https://www.youtube.com/watch?v=mg_pDqszL3g">https://www.youtube.com/watch?v=mg_pDqszL3g</a></li><li>Configuration Guide: <a href="https://eslint.org/docs/user-guide/configuring">https://eslint.org/docs/user-guide/configuring</a></li></ul><p><strong>3. Typescript</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2uMNz7g9gLcA70q9.jpg" /></figure><p>What it does: Adds type safety to JavaScript, making it easier to catch errors before running your code.</p><ul><li>Learning Resources:</li><li>Official Handbook: <a href="https://www.typescriptlang.org/docs/handbook/intro.html">https://www.typescriptlang.org/docs/handbook/intro.html</a></li><li>Interactive Learning: <a href="https://www.typescriptlang.org/play">https://www.typescriptlang.org/play</a></li><li>YouTube Course: “TypeScript Course for Beginners” by Academind: <a href="https://www.youtube.com/watch?v=BwuLxPH8IDs">https://www.youtube.com/watch?v=BwuLxPH8IDs</a></li></ul><p><strong>4. Husky</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*LAI_RKND2uEddi9C.jpeg" /></figure><p>What it does: Ensures code quality by running checks before commits.</p><p>Learning Resources:</p><ul><li>Official Documentation: <a href="https://typicode.github.io/husky/">https://typicode.github.io/husky/</a></li><li>Setup Guide: <a href="https://medium.com/@mariokandut/how-to-add-husky-to-react-233f0ca48752">https://medium.com/@mariokandut/how-to-add-husky-to-react-233f0ca48752</a></li><li>YouTube Tutorial: “Git Hooks with Husky” by Traversy Media: <a href="https://www.youtube.com/watch?v=ZXW6Jn6or1w">https://www.youtube.com/watch?v=ZXW6Jn6or1w</a></li></ul><p><strong>5. Vitest</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/895/0*oex-kx_pTKfKJfg1.png" /></figure><p>What it does: Fast testing framework for Vite-based projects.</p><p>Learning Resources:</p><ul><li>Official Documentation: <a href="https://vitest.dev/">https://vitest.dev/</a></li><li>Getting Started: <a href="https://vitest.dev/guide/">https://vitest.dev/guide/</a></li><li>YouTube Tutorial: “Testing React with Vitest” by Jack Herrington: <a href="https://www.youtube.com/watch?v=G-4zgIPHfJ4">https://www.youtube.com/watch?v=G-4zgIPHfJ4</a></li></ul><p><strong>6. i18next</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YA7FtLUOKTBnNVu_" /></figure><p>What it does: Provides internationalization framework for React applications, making it easy to manage multiple languages and translations.</p><p><strong>Learning Resources:</strong></p><ul><li>Documentation: <a href="https://www.i18next.com/">https://www.i18next.com/</a></li><li>React Integration Guide: <a href="https://react.i18next.com/">https://react.i18next.com/</a></li><li>Interactive Tutorial: <a href="https://www.i18next.com/overview/getting-started">https://www.i18next.com/overview/getting-started</a></li><li>“React i18next Tutorial” by Codevolution: <a href="https://www.youtube.com/watch?v=w04LXKluL1U">https://www.youtube.com/watch?v=w04LXKluL1U</a></li><li>“Internationalization in React” by Academind: <a href="https://www.youtube.com/watch?v=txHU6lrsa3o">https://www.youtube.com/watch?v=txHU6lrsa3o</a></li><li>“Complete i18n Guide”: <a href="https://phrase.com/blog/posts/react-i18n-app/">https://phrase.com/blog/posts/react-i18n-app/</a></li><li>“Step by Step i18next Integration”: <a href="https://dev.to/adrai/how-to-properly-internationalize-a-react-application-using-i18next-3hdb">https://dev.to/adrai/how-to-properly-internationalize-a-react-application-using-i18next-3hdb</a></li></ul><p><strong>7. zod/yup</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/848/0*yzEUfhkMOyEah_bG.jpeg" /></figure><p>What it does: Validates data with a schema-based approach.</p><p>Learning Resources:</p><ul><li>Zod Documentation: <a href="https://zod.dev/">https://zod.dev/</a></li><li>Yup Documentation: <a href="https://github.com/jquense/yup">https://github.com/jquense/yup</a></li><li>Tutorial: <a href="https://blog.logrocket.com/schema-validation-typescript-zod/">https://blog.logrocket.com/schema-validation-typescript-zod/</a></li></ul><p><strong>8. react-hook-form</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*T5ozbdyObj56qHZ3" /></figure><p>What it does: Manages form state and validation with excellent performance.</p><p>Learning Resources:</p><ul><li>Official Documentation: <a href="https://react-hook-form.com/">https://react-hook-form.com/</a></li><li>Getting Started: <a href="https://react-hook-form.com/get-started">https://react-hook-form.com/get-started</a></li><li>YouTube Tutorial: “React Hook Form Tutorial” by Codevolution: <a href="https://www.youtube.com/watch?v=bU_eq8qyjic">https://www.youtube.com/watch?v=bU_eq8qyjic</a></li></ul><p><strong>9. axios</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zM3itvJv5y22ZqBc.png" /></figure><p>What it does: Makes API calls easier and more powerful with features like interceptors.</p><p>Learning Resources:</p><ul><li>GitHub Documentation: <a href="https://github.com/axios/axios">https://github.com/axios/axios</a></li><li>Tutorial: <a href="https://blog.logrocket.com/how-to-use-axios-with-react/">https://blog.logrocket.com/how-to-use-axios-with-react/</a></li><li>YouTube Guide: “Axios Crash Course” by Traversy Media: <a href="https://www.youtube.com/watch?v=6LyagkoRWYA">https://www.youtube.com/watch?v=6LyagkoRWYA</a></li></ul><p><strong>10. React Query/ Tanstack Query</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pbS6I643eINNmxUm.png" /></figure><ul><li>What it does: Manages server state and caching in React applications.</li><li>Learning Resources:</li><li>Official Documentation: <a href="https://tanstack.com/query/latest">https://tanstack.com/query/latest</a></li><li>YouTube Tutorial: “React Query Tutorial” by CodeEvolution: <a href="https://www.youtube.com/watch?v=VtWkSCZX0Ec&amp;list=PLC3y8-rFHvwjTELCrPrcZlo6blLBUspd2">https://www.youtube.com/watch?v=VtWkSCZX0Ec&amp;list=PLC3y8-rFHvwjTELCrPrcZlo6blLBUspd2</a></li></ul><p><strong>11. tailwindcss</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*a6wKwuINHfnZHftK.jpg" /></figure><p>What it does: Provides utility classes for rapid UI development.</p><p>Learning Resources:</p><ul><li>Official Documentation: <a href="https://tailwindcss.com/docs">https://tailwindcss.com/docs</a></li><li>Tailwind UI (Components): <a href="https://tailwindui.com/">https://tailwindui.com/</a></li><li>YouTube Course: “Tailwind CSS Full Course” by Net Ninja: <a href="https://www.youtube.com/watch?v=bxmDnn7lrnk">https://www.youtube.com/watch?v=bxmDnn7lrnk</a></li></ul><p><strong>12. Iconify</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*43AU5sI3Vxn-gxi5.jpg" /></figure><p>What it does: Universal icon framework that provides access to over 150,000 icons from different icon sets.</p><p>Learning Resources:</p><ul><li>Documentation: <a href="https://iconify.design/docs/">https://iconify.design/docs/</a></li><li>Icon Search: <a href="https://icon-sets.iconify.design/">https://icon-sets.iconify.design/</a></li><li>React Documentation: <a href="https://iconify.design/docs/icon-components/react/">https://iconify.design/docs/icon-components/react/</a></li><li>Installation: <a href="https://iconify.design/docs/icon-components/react/#install">https://iconify.design/docs/icon-components/react/#install</a></li><li>Usage Tutorial: <a href="https://iconify.design/docs/usage/">https://iconify.design/docs/usage/</a></li></ul><p><strong>13. Shadcn</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZL_YPTmY05sGvMWS" /></figure><p>What it does: Provides ready-to-use React components built with Tailwind.</p><p>Learning Resources:</p><ul><li>Official Documentation: <a href="https://ui.shadcn.com/">https://ui.shadcn.com/</a></li><li>Component Library: <a href="https://ui.shadcn.com/docs/components/accordion">https://ui.shadcn.com/docs/components/accordion</a></li><li>YouTube Tutorial: “Build a Modern UI with shadcn/ui” by Josh tried coding: <a href="https://www.youtube.com/watch?v=dD6VzqNKUJE">https://www.youtube.com/watch?v=dD6VzqNKUJE</a></li></ul><p><strong>14. Tanstack Table</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_rMIMF8e50AptgL1" /></figure><p>What it does: Headless UI library for building powerful tables and datagrids.</p><p>Learning Resources:</p><ul><li>Official Documentation: <a href="https://tanstack.com/table/latest">https://tanstack.com/table/latest</a></li><li>Getting Started: <a href="https://tanstack.com/table/latest/docs/guide/introduction">https://tanstack.com/table/latest/docs/guide/introduction</a></li><li>YouTube Tutorials:</li><li>“TanStack Table Tutorial” by Jack Herrington: <a href="https://www.youtube.com/watch?v=AuLg79Th3xE">https://www.youtube.com/watch?v=AuLg79Th3xE</a></li><li>Advanced Guide: <a href="https://www.youtube.com/watch?v=CQ165vFGLVs">https://www.youtube.com/watch?v=CQ165vFGLVs</a></li></ul><p><strong>15. Tanstack Virtual</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0oCETO76ubZbHKKf.png" /></figure><p>What it does: Handles virtualization for large lists and grids, rendering only visible items for performance.</p><p>Learning Resources:</p><ul><li>Official Documentation: <a href="https://tanstack.com/virtual/latest">https://tanstack.com/virtual/latest</a></li><li>Guide: <a href="https://tanstack.com/virtual/latest/docs/guide/introduction">https://tanstack.com/virtual/latest/docs/guide/introduction</a></li><li>YouTube Tutorials:</li><li>“React Virtual Scrolling” by Jack Herrington: <a href="https://www.youtube.com/watch?v=UrgfPjX97Yg">https://www.youtube.com/watch?v=UrgfPjX97Yg</a></li><li>Implementation Guide: <a href="https://www.youtube.com/watch?v=D5SXS7ILS9w">https://www.youtube.com/watch?v=D5SXS7ILS9w</a></li></ul><p><strong>16. StoryBook</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*XZ7dwd73GRZhxS92" /></figure><p>What it does: Development environment for UI components, allowing you to browse, test, and document components in isolation.</p><p>Learning Resources:</p><ul><li>Official Documentation: <a href="https://storybook.js.org/docs/react/get-started/introduction">https://storybook.js.org/docs/react/get-started/introduction</a></li><li>Tutorial: <a href="https://storybook.js.org/tutorials/">https://storybook.js.org/tutorials/</a></li><li>YouTube Tutorials:</li><li>“Storybook React Tutorial” by LearnWebCode: <a href="https://www.youtube.com/watch?v=BySFuXgG-ow">https://www.youtube.com/watch?v=BySFuXgG-ow</a></li><li>“Storybook 7 Crash Course” by Jack Herrington: <a href="https://www.youtube.com/watch?v=CP_tPt1Wg2s">https://www.youtube.com/watch?v=CP_tPt1Wg2s</a></li></ul><p><strong>17. maestro</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PSDM4X-XBVhhMH8h" /></figure><p>What it does: Used for testing mobile applications that are built using expo or react native.</p><p>Learning Resources:</p><ul><li>Official Documentation: <a href="https://maestro.mobile.dev/">https://maestro.mobile.dev/</a></li><li>Examples: <a href="https://github.com/mobile-dev-inc/maestro">https://github.com/mobile-dev-inc/maestro</a></li><li>YouTube Tutorial: “Painless mobile test automation with Maestro” by Software Testing by Daniel Knott: <a href="https://www.youtube.com/watch?v=EcO1QVtnqxw">https://www.youtube.com/watch?v=EcO1QVtnqxw</a></li></ul><p><strong>18. sonarqube</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3_VSR7BRyydHJTd0.png" /></figure><p>What it does: Continuous code quality inspection.</p><p>Learning Resources:</p><ul><li>Official Documentation: <a href="https://docs.sonarqube.org/">https://docs.sonarqube.org/</a></li><li>Getting Started: <a href="https://docs.sonarqube.org/latest/setup/get-started-2-minutes/">https://docs.sonarqube.org/latest/setup/get-started-2-minutes/</a></li><li>YouTube Tutorial: “SonarQube Tutorial” by Programming Knowledge with Nana: <a href="https://www.youtube.com/watch?v=6vdRvz_LnbQ">https://www.youtube.com/watch?v=6vdRvz_LnbQ</a></li></ul><p><strong>19. Sentry</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*VxAZZ5iScqM0glZc" /></figure><p>What it does: Real-time error tracking and monitoring.</p><p>Learning Resources:</p><ul><li>Official Documentation: <a href="https://docs.sentry.io/">https://docs.sentry.io/</a></li><li>React Integration: <a href="https://docs.sentry.io/platforms/javascript/guides/react/">https://docs.sentry.io/platforms/javascript/guides/react/</a></li><li>YouTube Tutorial: “Error Monitoring with Sentry” by Traversy Media: <a href="https://www.youtube.com/watch?v=kg3GoE2KA0U">https://www.youtube.com/watch?v=kg3GoE2KA0U</a></li></ul><p><strong>20. unleash</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DWLQ72bicISnjtyW.jpg" /></figure><p>What it does: Feature flag management for gradual rollouts.</p><p>Learning Resources:</p><ul><li>Official Documentation: <a href="https://docs.getunleash.io/">https://docs.getunleash.io/</a></li><li>Getting Started: <a href="https://docs.getunleash.io/getting-started">https://docs.getunleash.io/getting-started</a></li><li>YouTube: “Feature Toggles with Unleash” by Unleash: <a href="https://www.youtube.com/watch?v=dPXZZ4CMXZE">https://www.youtube.com/watch?v=dPXZZ4CMXZE</a></li></ul><p><strong>Recommended Learning Path:</strong></p><ol><li>Start with TypeScript fundamentals</li><li>Learn ESLint and Husky for code quality</li><li>Master Tailwind CSS for styling</li><li>Learn React Query for data fetching</li><li>Implement form handling with react-hook-form and zod</li><li>Add testing with Vitest</li><li>Finally, add monitoring with Sentry and feature flags with unleash</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8086a22551e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 Tips for writing clean code]]></title>
            <link>https://medium.com/@read.sajan.blog/10-tips-for-writing-clean-code-bb9c29c62059?source=rss-cfaa77925930------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb9c29c62059</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Sajan Nepali]]></dc:creator>
            <pubDate>Mon, 20 May 2024 15:24:09 GMT</pubDate>
            <atom:updated>2024-05-20T15:24:09.515Z</atom:updated>
            <content:encoded><![CDATA[<p>Even bad code can work, But if code isn’t clean it can bring development to hold. Every year countless hours and significant resources are lost because of poorly written code. But we can prevent it.</p><p><strong>A Simple Scenario</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lsI6XfINnQJXyXCSAz9lDQ.png" /></figure><p>Once I had a situation when my colleague quit his job because he dealt with a REST API on Java that was hard to maintain. He received this project from previous team of developers. Fixing current bugs creates new ones, adding new features creates a new series of bugs and so on (fragile code). The client didn’t want to rebuild the application with a better design, and the developer made the correct decision to …. ?</p><p><em>In order to prevent this scenario. Here are some tips on writing clean code.</em></p><h4>1. Follow style guides</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BsdUcM_IhDso5YVGA2NW5g.png" /></figure><p>We can create our own style guides ensure clean code is written and maintained consistently throughout a project or organization. It includes coding convention, language specific guidelines, architectural patterns. It is best to follow widely accepted style guides. For example: Airbnb Style Guide, Google Style Guide, Standard JS and Idiomatic.js.</p><h4>2. DRY Principle</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AhrExbyYjtjYXXPYOAPmzA.png" /></figure><p>DRY stands for Don’t repeat yourself. Also known as DIE (Duplication is Evil). Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.</p><h4>3. Managing Files and Folder</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/676/0*Srm6nfrNn2F12cBx.png" /></figure><p>Technically, you could write an entire application code within a single file. But that would prove to be a nightmare to read and maintain. You can read more about managing folder structures for your application in my other article: <a href="https://medium.com/@read.sajan.blog/frontend-coding-guidelines-folder-structure-e146b00513fb">[ Frontend Coding Guidelines (Folder Structure) ]</a></p><h4>4. Small Functions</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jQmPlI3hgc_j0gXYRH4r-w.png" /></figure><p>Functions should be small really small. Big functions that have a lot of responsibility should be avoided and split into small ones. Big black box functions are difficult to understand, modify and especially test.</p><h4>5. Avoid Big Functions</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3dsBYHDYq8MPxhr37nKGOw.png" /></figure><p>Code that does it all. Visit this link to read more about importance of avoiding big functions. <a href="https://dmitripavlutin.com/the-art-of-writing-small-and-plain-functions/">[ Art of writing small and plain functions ]</a></p><h4>6. Comments</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3RiTgMWeFDPKYXgPbcq9Kg.png" /></figure><p>Write comments when needed not always. It provides explanatory information about the source code. But do we need comments in our source. Techniques to identify if comment is needed or not.</p><p>a) Is this comment really required and what value does it add ?</p><p>b) Is there a way to improve the code so that commenting is unnecessary.</p><p>c) Am I only covering my mistakes by writing comments ?</p><h4>7. Code Review Process</h4><p>Establish guidelines and coding standards to ensure code quality, catching bugs and issues early and promotes knowledge sharing among team members. A good code review process includes: Guidelines, Code Review Tool ( any SCM like GitLab or GitHub), assigned reviewer, timely review , constructive feedback and proper addressing of the issue.</p><h4>8. Version Control</h4><p>Version Control is essential for managing code changes, collaboration with team members , maintaining a clear history of code modifications. You can read more about version control and branching strategy on my another article<a href="https://medium.com/stackademic/frontend-coding-guidelines-git-workflow-5fe212f139e2">[ Frontend Coding Guidelines (Git Workflow) ]</a></p><h4>9. Deployment Procedures</h4><p>In order to reduce the risk of downtime and issues in production.</p><p>a) Automate deployment using scripts, configuration management systems or deployment pipelines.</p><p>b) Mirror staging environment that mirrors production</p><p>c) Maintain checklist for migrations and scripts to run, deployment process, configuration and requirements.</p><p>d) Define rollback strategy and implement monitoring and logging solution to track health and performance.</p><h4>10. Onboarding and Knowledge Transfer</h4><p>In order to ensure team members are aligned with coding standards, best practices and domain knowledge. Here are some strategies you can follow:</p><p>a) Pair Programming</p><p>b) Code Reviews and Knowledge Sharing Sessions</p><p>c) Coding Challenges</p><p>d) Code Walkthrough</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb9c29c62059" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Git Workflow for large scale applications]]></title>
            <link>https://blog.stackademic.com/frontend-coding-guidelines-git-workflow-5fe212f139e2?source=rss-cfaa77925930------2</link>
            <guid isPermaLink="false">https://medium.com/p/5fe212f139e2</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Sajan Nepali]]></dc:creator>
            <pubDate>Wed, 01 May 2024 03:47:34 GMT</pubDate>
            <atom:updated>2024-06-13T06:53:29.009Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BMnu8mUV_9r4VnLHe8azag.png" /></figure><h3>Introduction</h3><p>This workflow is based on Gitflow, a git branching model that involves the use of feature branches and multiple primary branches. Under this model developers create a feature branch and delay merging it to the main trunk branch until the feature is complete. There are also GitHub Flow and GitLab flow.</p><h3>Recommended Practices for Utilizing Git</h3><ul><li>Make clean, single purpose commit</li><li>Write meaningful commits</li><li>Commit Early &amp; commit often</li><li>Don’t alter published history (use rebase on your local branch only)</li><li>Don’t commit generated files</li></ul><h3>Git branches</h3><h4>Primary Git Branches</h4><ul><li>Master</li><li>Main</li></ul><h4>Environment Branches</h4><ul><li>Development</li><li>Staging</li><li>Production</li></ul><h4>Supporting Branches</h4><ul><li>Bug</li><li>Hotfix</li><li>Release</li><li>Feature</li></ul><h3>Workflow</h3><p>Instead of a single main branch to manage the history of the project. There will be environment branches and supporting branches. The main branch stores the official release history and environment branches serves as an integration branch for supporting branches.</p><p>First we will create an empty environment branch locally and push it to the server.</p><p>Development Branch</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/245/0*rSXjbpMWwDHcvj6w" /></figure><p>Staging Branch</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/245/0*HfCmc7nLafUohAN5" /></figure><h4>Feature branches</h4><p>Each new feature should be in its own branch, which can be pushed to the central repo for backup or collaboration.</p><p><strong><em>Note:</em></strong> Instead of branch off Primary branches, feature branches must use environment branches as their parent branch.</p><p>When the feature is complete it is merged back to its parent branch.</p><p>Feature branches should never directly interact with primary branches.</p><p>While creating a feature branch</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4gPwQD1Mk-2EaBBa" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YulGnBH9kpspQb0W" /></figure><p>While merging the feature branch code</p><h4>Release Branch</h4><p>Once you have developed enough features for a release you create a release branch from the environment branch. Creating this branch will create the next release cycle.</p><p>Note: In the release branch no new feature is added, it will only include bug fixes and documentation generation and other release oriented tasks should go in this branch.</p><p>Once it is ready it is merged to the primary branch tagged with a version number.</p><p>It should be merged back to the environment branch, since the release was initiated.</p><h4>Advantages of using release branch</h4><p>Using this branch will make it possible for one time to polish the current release while another team continues working on the next release.</p><p>Release branch are based on environment branch</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CZYKmFRyNLuy3TIm" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*30OLKCCALDWoKRKQ" /></figure><p>Once the release is ready to ship it will get merged into the primary branch then the release branch will be deleted.</p><p>It’s important to merge back into the environment branch because critical updates may have been added to the release branch and they need to be accessible to new features.</p><h4>Hotfix Branches</h4><p>Hotfix branches are used to quickly patch production releases. Hotfix branches are like release branches and feature branches except they are based on the primary branch instead of the environment branch. This is the only branch that should fork directly from primary branches. As soon as the fix is complete, it should be merged into primary branch and environment branches.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9ydiThtnCvtbcez9" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OzdI3ReUQEWMAyJk" /></figure><h4>Summary</h4><ul><li>Environment branches are created from main branches</li><li>A release branch is created from environment branch</li><li>Feature branch is created from environment branch</li><li>When release branch is done it is merged into environment branch and primary branch</li><li>If an issue is in the primary branch, the hotfix branch is created from the primary branch and after hotfix is completed it is merged back to the primary and environment branch.</li></ul><h4>Naming Conventions</h4><ul><li>Start branch name with temporary git branches group word</li><li>Use unique ids in branch name</li><li>Use hyphens (-) or slash or separator ( _ )</li><li>Avoid long descriptive names</li></ul><p>Example: bug-logo-alignment-issue</p><p>If you are using Jira or any other project management tool in that case we can use following naming convention. {TAG}/{NAME_INITIAL}-{TICKET_ID}-{SHORT_TASK_DESCRIPTION}</p><p>Example: feat/SN-AMS-112-change-dashboard-layout</p><h3>Git commits</h3><p>Git can be thought of as a timeline management utility. Commits are the core building block on a Git project timeline. Commits are created by git commit command to capture state of project at that time.</p><p>Commands</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2d1cp0PuTjOHYCst" /></figure><h4>Semantic commit</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VMcYqKJGo6_Ag7X8" /></figure><h3>Git Rebase</h3><p>If you want to use Rebase, you should only use it in supporting branches or local branches.</p><h4>References</h4><ul><li><a href="https://docs.gitlab.com/ee/topics/gitlab_flow.html">Redirecting...</a></li><li><a href="https://www.atlassian.com/git/tutorials/saving-changes/git-commit">Git Commit | Atlassian Git Tutorial</a></li><li><a href="https://github.com/git-guides/git-commit">Git Guides - git commit</a></li><li><a href="https://www.gitkraken.com/learn/git/best-practices/git-branch-strategy#gitlab-flow-branch-strategy">What is the best Git branch strategy? | Git Best Practices</a></li></ul><p><a href="https://docs.gitlab.com/ee/topics/git/cherry_picking.html">https://docs.gitlab.com/ee/topics/git/cherry_picking.html</a></p><ul><li><a href="https://www.gitkraken.com/learn/git/git-flow">What is Git Flow | How to use Git Flow | Learn Git</a></li><li><a href="https://www.gitkraken.com/learn/git/best-practices/git-branch-strategy#gitlab-flow-branch-strategy">What is the best Git branch strategy? | Git Best Practices</a></li><li><a href="https://www.toptal.com/git/git-workflows-for-pros-a-good-git-guide">Git Workflows for Pros: A Good Git Guide | Toptal®</a></li></ul><h3>Stackademic 🎓</h3><p>Thank you for reading until the end. Before you go:</p><ul><li>Please consider <strong>clapping</strong> and <strong>following</strong> the writer! 👏</li><li>Follow us <a href="https://twitter.com/stackademichq"><strong>X</strong></a><strong> | </strong><a href="https://www.linkedin.com/company/stackademic"><strong>LinkedIn</strong></a><strong> | </strong><a href="https://www.youtube.com/c/stackademic"><strong>YouTube</strong></a><strong> | </strong><a href="https://discord.gg/in-plain-english-709094664682340443"><strong>Discord</strong></a></li><li>Visit our other platforms: <a href="https://plainenglish.io/"><strong>In Plain English</strong></a><strong> | </strong><a href="https://cofeed.app/"><strong>CoFeed</strong></a><strong> | </strong><a href="https://venturemagazine.net/"><strong>Venture</strong></a><strong> | </strong><a href="https://blog.cubed.run/"><strong>Cubed</strong></a></li><li>More content at <a href="https://stackademic.com/"><strong>Stackademic.com</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5fe212f139e2" width="1" height="1" alt=""><hr><p><a href="https://blog.stackademic.com/frontend-coding-guidelines-git-workflow-5fe212f139e2">Git Workflow for large scale applications</a> was originally published in <a href="https://blog.stackademic.com/">Stackademic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Master React Folder Structure]]></title>
            <link>https://blog.stackademic.com/frontend-coding-guidelines-folder-structure-e146b00513fb?source=rss-cfaa77925930------2</link>
            <guid isPermaLink="false">https://medium.com/p/e146b00513fb</guid>
            <category><![CDATA[react-architecture]]></category>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[coding-guideline]]></category>
            <category><![CDATA[folder-structure]]></category>
            <category><![CDATA[maintainable-code]]></category>
            <dc:creator><![CDATA[Sajan Nepali]]></dc:creator>
            <pubDate>Sat, 27 Apr 2024 04:50:50 GMT</pubDate>
            <atom:updated>2024-06-13T07:01:39.518Z</atom:updated>
            <content:encoded><![CDATA[<p>If you haven’t struggled with folder structure and naming issue in your coding journey then you are one heck of lucky guy. Maintaining consistency, accessibility, readability becomes increasingly difficult without a clear structure. It can be especially challenging when using a library compared to framework, which often enforces structure.</p><p>In libraries such as React JS, overall decision about project structure is up to the developers. Defining the guidelines about folder structure will help to ease the burden of maintenance and enhance collaboration among team members.</p><p>Goal of defining the coding guidelines for folder structure are as follows:</p><ul><li>Maintain a clear structure</li><li>Pages Based Organization</li><li>Consistency and Clarity</li><li>Improve onboarding &amp; collaboration</li></ul><p>This folder structure guideline can be used in frontend libraries. I’ll showcase their implementation within the context of a React JS application.</p><h3>Folder Overview</h3><p>This is an overview of our application folder structure except other configuration such eslint, prettier, tsconfig. All folder naming will be in lowercase.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/676/1*a-tQkaV7Ug3AQDRuc0k6zA.png" /></figure><h4>assets</h4><p><em>assets </em>folder will contain the icons, images, fonts used in our application.</p><figure><img alt="assets folder structure" src="https://cdn-images-1.medium.com/max/611/1*ac9X6W0bgxziSW1cRkdILA.png" /></figure><h4>components</h4><p><em>components</em> folder will contain reusable components related to application. In <em>index.ts</em> file we will only import the components and export them back. We will be using dash casing for naming the files.</p><p>Note: All folder will have <strong>index.ts</strong> file which will be used for same purpose exporting all the components or functions from the particular folder.</p><figure><img alt="components folder structure" src="https://cdn-images-1.medium.com/max/618/1*S5JYsiEEho2dSlsgpp4R4g.png" /></figure><h4>hooks</h4><p><em>hooks</em> folder will contain application level hooks. Module specific hooks are stored in respective module folder. File names for hooks typically begin with the “use” keyword and are commonly written in camelCase.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/621/1*tmbTxspTTHCrCd1KOkCEDg.png" /></figure><h4>pages</h4><p><em>pages </em>folder will contain different page of the application. For example a product directory will contain following structure. While it may initially seem like an abundance of folders and files for handling a straightforward module, as the application scales, this structure proves invaluable for efficient code management.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/664/1*mYrBp9GVfCYPFIHJvRR9Qw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/1*wTYNAYVX7O7TGA1ZgPHzXw.png" /></figure><h4>routes</h4><p><em>routes </em>folder will contain the public, private routes and components that will be used for handling the routes access.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/679/1*XrfzVSov9sHe1MH5VA978w.png" /></figure><h4>ui</h4><p><em>ui </em>folder will contain reusable piece of UI components. The are building blocks for the components. <em>ui </em>folder is segregated into multiple sub folders according to the nature of the component.</p><figure><img alt="UI folder overview" src="https://cdn-images-1.medium.com/max/685/1*JdB3vpR-qMuZRmmp9VHDgA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/949/1*HQE6CLr_jaXkcW8v3gu48g.png" /></figure><h4>utils</h4><p><em>utils </em>folder will contain utility functions, helper module, reusable code snippets that can be used across different part of the applications. It helps to promote reusability and maintainability of the code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/676/1*llgSMJ9u2uQpQRFai2h7mQ.png" /></figure><h4>Conclusion</h4><p>While each software application is unique establishing and following the consistent coding guidelines can address many of the common challenges that may arise during the development process. By following these guidelines, you can enhance your productivity and streamline your workflow. We can talk hours about how our application structure should be maintained but the important thing is that you get consent from your team members and all follow the same pattern.</p><p>We can improve this structure even more by separating our ui and logics into separate repo. But that topic is too large to cover in a single article.</p><h3>Stackademic 🎓</h3><p>Thank you for reading until the end. Before you go:</p><ul><li>Please consider <strong>clapping</strong> and <strong>following</strong> the writer! 👏</li><li>Follow us <a href="https://twitter.com/stackademichq"><strong>X</strong></a><strong> | </strong><a href="https://www.linkedin.com/company/stackademic"><strong>LinkedIn</strong></a><strong> | </strong><a href="https://www.youtube.com/c/stackademic"><strong>YouTube</strong></a><strong> | </strong><a href="https://discord.gg/in-plain-english-709094664682340443"><strong>Discord</strong></a></li><li>Visit our other platforms: <a href="https://plainenglish.io/"><strong>In Plain English</strong></a><strong> | </strong><a href="https://cofeed.app/"><strong>CoFeed</strong></a><strong> | </strong><a href="https://venturemagazine.net/"><strong>Venture</strong></a><strong> | </strong><a href="https://blog.cubed.run/"><strong>Cubed</strong></a></li><li>More content at <a href="https://stackademic.com/"><strong>Stackademic.com</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e146b00513fb" width="1" height="1" alt=""><hr><p><a href="https://blog.stackademic.com/frontend-coding-guidelines-folder-structure-e146b00513fb">Master React Folder Structure</a> was originally published in <a href="https://blog.stackademic.com/">Stackademic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>