<?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 Adrian Pothuaud on Medium]]></title>
        <description><![CDATA[Stories by Adrian Pothuaud on Medium]]></description>
        <link>https://medium.com/@adrianpothuaud?source=rss-73db18d1c271------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*eB9rwLdinIeTiOtDDIcYWg.jpeg</url>
            <title>Stories by Adrian Pothuaud on Medium</title>
            <link>https://medium.com/@adrianpothuaud?source=rss-73db18d1c271------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 15:09:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adrianpothuaud/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[Feature Driven Development in a Node.js backend project]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">What if you just forget everything you know about REST API best practices and just want to focus on a Feature-Driven approach?</p><p class="medium-feed-link"><a href="https://medium.com/@adrianpothuaud/feature-driven-development-in-a-node-js-backend-project-008872f76c35?source=rss-73db18d1c271------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@adrianpothuaud/feature-driven-development-in-a-node-js-backend-project-008872f76c35?source=rss-73db18d1c271------2</link>
            <guid isPermaLink="false">https://medium.com/p/008872f76c35</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[backend]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Adrian Pothuaud]]></dc:creator>
            <pubDate>Mon, 13 Oct 2025 14:22:08 GMT</pubDate>
            <atom:updated>2025-10-14T06:19:54.211Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Creating a RAG process for selectors using Cypress and Ollama]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">AI-powered element selection for Cypress using natural language descriptions</p><p class="medium-feed-link"><a href="https://medium.com/@adrianpothuaud/creating-a-rag-process-for-selectors-using-cypress-and-ollama-e6cdd8228db3?source=rss-73db18d1c271------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@adrianpothuaud/creating-a-rag-process-for-selectors-using-cypress-and-ollama-e6cdd8228db3?source=rss-73db18d1c271------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6cdd8228db3</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[cypress]]></category>
            <dc:creator><![CDATA[Adrian Pothuaud]]></dc:creator>
            <pubDate>Mon, 15 Sep 2025 08:01:31 GMT</pubDate>
            <atom:updated>2025-09-26T08:58:24.071Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Why I abandon Copilot and AI stuff for Pausely and other side projects?]]></title>
            <link>https://medium.com/@adrianpothuaud/why-i-abandon-copilot-and-ai-stuff-for-pausely-and-other-side-projects-c019b41d697f?source=rss-73db18d1c271------2</link>
            <guid isPermaLink="false">https://medium.com/p/c019b41d697f</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[github-copilot]]></category>
            <category><![CDATA[side-hustle]]></category>
            <dc:creator><![CDATA[Adrian Pothuaud]]></dc:creator>
            <pubDate>Sat, 13 Sep 2025 19:49:49 GMT</pubDate>
            <atom:updated>2025-09-13T19:49:49.161Z</atom:updated>
            <content:encoded><![CDATA[<p>✋ Hi! I am Adrian, a software engineer in software quality and test automation since 10 years.</p><p>A few years ago I started trying to develop small side projects each time I found a little idea that could help me first and then try to deploy and see if it solves the same problem for other few people.</p><p>This year, 2025, I started using the Pomodoro technique daily to help me stay focus working from home. I also try to renew with sport trying to maintain several street workout training sessions a week, and instoring healthy routines each day (ex: 5 mn jump rope between 2 tasks while working).</p><p>I realise that I could bring both concepts together and it may be fun and helpful to fight sedentarity for most people with the rise of remote working nowadays.</p><p>And it was the era of copilot and coding agents so I had to try and I was completely bluffed by it, I even bought copilot premium and Jetbrains AI (Junie) coding agent license to kickstart the project.</p><p>It was interesting and growing really fast. I had the first viable version of the application in a few hours and a very little amount of prompts.</p><p>i began by asking things and doing myself and quickly I moved into just prompting and letting the agent code for me, with the very minimum of human check, the. quickly refresh and test the app.</p><p>It was surprisingly close to what I had in mind and even adding details to the app I had never thought about myself. That’s when I started to feel something strange: I was shipping fast, but I wasn’t really building anymore. The sense of craft, the little frustrations that make you understand your own product deeper, were gone.</p><p>Instead of creating, I was just curating AI output. And for a side project that was supposed to be fun, that killed the motivation pretty quickly.</p><p>So I took a step back. I asked myself: what do I really want from these projects? Do I want to outsource the joy of building to an agent, or do I want to struggle, learn, and maybe grow something that reflects my own hands and brain?</p><p>That’s when I decided to pause Copilot and AI stuff for a while, and focus on <strong>Pausely</strong>. A tool simple enough to be built without an AI coding army, but meaningful enough to help me (and maybe others) fight the sedentary trap of remote work.</p><p>Working on Pausely the “manual” way feels slower, yes. But it also feels real. I understand every line of code, every decision, every trade-off. And at the end of the day, that’s what I was looking for when I started building side projects in the first place.</p><p>AI is powerful, and I’m not closing the door on it forever. But for now, I want to enjoy the process again — not just the result.</p><p>Si, yes, at the moment Pausely may be down or broken for a moment. But I am rebuilding it myself and it will be online very soon!</p><p>The new app will be very basic, no big efforts on design system and stuff like that, but I want to reship basic features quickly so I can make it run for me and maybe other people. Then I will be able to continue to build and grow it later.</p><p>Thanks for reading, if you enjoyed this article, give it a cap! Or if you just want to discuss about your own experience with AI agents feel free to comment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c019b41d697f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your Brain Feels Like Fried Mush by 3 PM? Yeah, Mine Too. Let’s Fix That.]]></title>
            <link>https://medium.com/@adrianpothuaud/your-brain-feels-like-fried-mush-by-3-pm-yeah-mine-too-lets-fix-that-260810381251?source=rss-73db18d1c271------2</link>
            <guid isPermaLink="false">https://medium.com/p/260810381251</guid>
            <category><![CDATA[work-life-balance]]></category>
            <category><![CDATA[lifestyle]]></category>
            <category><![CDATA[habits]]></category>
            <category><![CDATA[pomodoro]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Adrian Pothuaud]]></dc:creator>
            <pubDate>Wed, 09 Jul 2025 09:28:36 GMT</pubDate>
            <atom:updated>2025-07-09T09:28:36.152Z</atom:updated>
            <content:encoded><![CDATA[<p>Let’s be real. The modern workday is a chaotic mess. 😵‍💫</p><p>You open your laptop with the best intentions, ready to crush your to-do list. But then… <em>ping</em>. A Slack message. <em>Buzz</em>. An email. “Ooh, a new YouTube video!” And before you know it, it’s lunchtime, and the only thing you’ve accomplished is developing an impressive level of anxiety.</p><p>I was stuck in that exact cycle. I tried all the fancy-pants productivity apps with a million features. They just added more noise. I wanted something that would get out of my way and just let me <em>work</em>.</p><p>Since I couldn’t find it, I built it. Say hello to <strong>Pausely</strong> 👋.</p><p><a href="https://pausely.vercel.app/">https://pausely.vercel.app</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TGhqA45de2XzKGTPQ-_toQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*octUY2bLO-d1tB2YUnlZKw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pS8bbZ6MQJEPvC4IFrmccg.png" /></figure><h4>So, What the Heck is Pausely?</h4><p>Pausely is a dead-simple, no-BS web timer designed for one thing: to help you get in the zone and actually get stuff done.</p><p>It’s not another complicated system you have to learn. It’s a tool that gently nudges you: “Okay, time to grind for a bit.” and then, “Nice one! Now go touch some grass for five minutes.” 🌿</p><p>It’s for anyone who’s ever fallen down a Wikipedia rabbit hole when they were supposed to be working. Students, coders, writers, designers… if your job involves a screen, this is for you. No downloads, no sign-ups. Just open a tab and go.</p><h4>The Good Stuff (aka Features)</h4><p>I kept things minimal on purpose. Every feature is there to help, not to distract.</p><ul><li><strong>A Clean Look (with a sexy Dark Mode 🌙):</strong> It’s easy on the eyes, whether you’re a dark mode demon or a light mode purist. It looks great on your giant monitor and on your phone when you’re pretending to work from a café.</li><li><strong>You’re the Boss of Your Time:</strong> Don’t like the default 25-minute work session? Change it. Want longer breaks? Go for it. Pausely remembers your settings so you don’t have to fiddle with it every time.</li><li><strong>It Just Works™:</strong> The timer automatically cycles between work, short breaks, and long breaks. You don’t have to think about it. Just follow the flow and watch your productivity soar. 🚀</li><li><strong>Focus is Universal:</strong> Pausely speaks multiple languages because the struggle to focus is a global phenomenon. 🌍</li></ul><h4>My Little Side Project</h4><p>Pausely was born from too many cups of coffee and a genuine need to reclaim my own focus. It’s been a passion project, and I’m constantly tweaking it. It’s not perfect, but it’s honest work, and it’s helped me immensely. I hope it can help you too.</p><h4>Ready to Un-fry Your Brain?</h4><p>Stop procrastinating on your procrastination tool search. Give Pausely a try. It’s free, it’s simple, and it might just be the thing that helps you find your flow again.</p><p><strong>Check out Pausely here: </strong><a href="https://pausely.vercel.app/"><strong>https://pausely.vercel.app</strong></a></p><p>I’m dying to know what you think. Love it? Hate it? Have a brilliant idea? Drop a comment below or hit me up on social media. I’m all ears! 👂</p><p>And if you find it useful, do me a solid and share it with a friend. We all know someone who could use a little more focus in their life.</p><p>Now go get some work done! 😉</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=260810381251" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Feature-Driven Development with TypeScript, Express, and Zod: A Modern Approach to API Development…]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">Today, I&#x2019;m excited to share with you a game-changing approach that has transformed how I build backend APIs with Feature-Driven&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@adrianpothuaud/feature-driven-development-with-typescript-express-and-zod-a-modern-approach-to-api-development-e5e7c79d8961?source=rss-73db18d1c271------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@adrianpothuaud/feature-driven-development-with-typescript-express-and-zod-a-modern-approach-to-api-development-e5e7c79d8961?source=rss-73db18d1c271------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5e7c79d8961</guid>
            <category><![CDATA[clean-architecture]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[backend-development]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Adrian Pothuaud]]></dc:creator>
            <pubDate>Fri, 06 Jun 2025 09:19:41 GMT</pubDate>
            <atom:updated>2025-09-26T08:58:20.939Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Supercharge Your E2E Tests: Cross-Platform Text Selectors in Webdriver.IO]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">Hey Testers! Ever feel like you&#x2019;re writing the same test logic three times just to cover Web, Android, and iOS? Read my article!</p><p class="medium-feed-link"><a href="https://medium.com/@adrianpothuaud/supercharge-your-e2e-tests-cross-platform-text-selectors-in-webdriver-io-25508e40fc86?source=rss-73db18d1c271------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@adrianpothuaud/supercharge-your-e2e-tests-cross-platform-text-selectors-in-webdriver-io-25508e40fc86?source=rss-73db18d1c271------2</link>
            <guid isPermaLink="false">https://medium.com/p/25508e40fc86</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[test-automatio]]></category>
            <category><![CDATA[end-to-end-testing]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[webdriver]]></category>
            <dc:creator><![CDATA[Adrian Pothuaud]]></dc:creator>
            <pubDate>Mon, 12 May 2025 13:38:20 GMT</pubDate>
            <atom:updated>2025-09-27T00:18:30.624Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[ 5 Essential Test Automation Rules for a Reliable and Scalable Testing Strategy]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">Avoid common pitfalls and maximize your automation success with these practical, battle-tested guidelines.</p><p class="medium-feed-link"><a href="https://medium.com/@adrianpothuaud/5-essential-test-automation-rules-for-a-reliable-and-scalable-testing-strategy-cc7b34e1acca?source=rss-73db18d1c271------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@adrianpothuaud/5-essential-test-automation-rules-for-a-reliable-and-scalable-testing-strategy-cc7b34e1acca?source=rss-73db18d1c271------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc7b34e1acca</guid>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[flaky-tests]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Adrian Pothuaud]]></dc:creator>
            <pubDate>Mon, 17 Feb 2025 05:40:59 GMT</pubDate>
            <atom:updated>2025-10-01T05:39:19.435Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Testing is Doubting… and That’s a Good Thing! Become a Software Quality Assurance Engineer]]></title>
            <link>https://medium.com/@adrianpothuaud/testing-is-doubting-and-thats-a-good-thing-become-a-software-quality-assurance-engineer-4972526e7fcc?source=rss-73db18d1c271------2</link>
            <guid isPermaLink="false">https://medium.com/p/4972526e7fcc</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[Adrian Pothuaud]]></dc:creator>
            <pubDate>Sun, 10 Nov 2024 06:26:56 GMT</pubDate>
            <atom:updated>2024-11-10T20:04:40.592Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/478/1*zj7lspMs0DqM6NPvK5P03w.png" /></figure><p>Hey everyone! 👋</p><p>Today, we’re diving into an exciting career that’s often overlooked but absolutely crucial in the world of software development: <strong>Software Quality Assurance Engineer</strong>.</p><p>Maybe you’re a developer, a project manager, or even someone with no tech background at all… It doesn’t matter! If you’re curious, detail-oriented, and love finding those hidden flaws, this career might surprise you. 😉</p><h3>Why is this job so important?</h3><p>Imagine: you just downloaded a new mobile app. It looks great, seems super convenient… but as soon as you try to create an account, <em>crash</em>! Frustrating, right?</p><p>That’s where the Software Quality Assurance Engineer comes in. Their role? To ensure the software works correctly, is stable, performs well, and meets user needs. Basically, they’re there to prevent bugs and unpleasant surprises! 🕵️‍♀️</p><h3>What makes a good tester?</h3><ul><li><strong>Curiosity above all!</strong> A good tester is like a detective. They need to be able to put themselves in the user’s shoes, imagine all possible scenarios, even the most improbable ones. “What if I press this button 10 times in a row? What if I enter a wacky birthdate?” 🤔</li><li><strong>An analytical and rigorous mind.</strong> Identifying a bug is good. Understanding where it comes from and reproducing it to fix it is even better! The QA Engineer must be methodical and precise in their analysis. 🔎</li><li><strong>Strong communication skills.</strong> Knowing how to clearly explain a problem to developers is essential. The QA Engineer must be able to write clear and concise reports, and communicate effectively with different team members. 🗣️</li><li><strong>Adaptability and patience.</strong> The software world is constantly evolving. New tools and technologies are always emerging. The QA Engineer must be able to adapt and learn continuously. And yes, sometimes you need to be patient to track down a stubborn bug! 🧘‍♂️</li></ul><h3>What does it actually involve?</h3><p>The daily life of a Software Quality Assurance Engineer is varied:</p><ul><li><strong>Analyzing user needs</strong> and software specifications.</li><li><strong>Designing and executing tests</strong> (functional tests, performance tests, security tests…).</li><li><strong>Identifying and documenting bugs.</strong></li><li><strong>Automating tests</strong> for greater efficiency.</li><li><strong>Collaborating with developers</strong> to fix errors.</li><li><strong>Ensuring the overall quality of the software.</strong></li></ul><h3>Why consider this career?</h3><ul><li><strong>It’s a future-proof career!</strong> With the increasing digitalization of our society, the demand for Software Quality Assurance Engineers is constantly growing. 🚀</li><li><strong>It’s a stimulating and varied job.</strong> You’ll never get bored! Each project is different, each bug is a new challenge to overcome. 💪</li><li><strong>It’s a meaningful job.</strong> By contributing to the quality of software, you improve the user experience and participate in the creation of innovative products. ✨</li></ul><p>So, what do you think? Whether you come from the tech world or a completely different field, don’t hesitate to explore this path! Many training courses and resources are available to support you.</p><p>And if you have any questions, feel free to ask in the comments! 😉</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4972526e7fcc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Reviewed Uncle Bob Clean Code Videos as a Software Quality Engineer — This is what I learned]]></title>
            <link>https://medium.com/@adrianpothuaud/i-reviewed-uncle-bob-clean-code-videos-as-a-software-quality-engineer-this-is-what-i-learned-4b21d15f0f89?source=rss-73db18d1c271------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b21d15f0f89</guid>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[clean-code]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Adrian Pothuaud]]></dc:creator>
            <pubDate>Thu, 07 Nov 2024 12:39:42 GMT</pubDate>
            <atom:updated>2024-11-07T12:39:42.514Z</atom:updated>
            <content:encoded><![CDATA[<h3>I Reviewed Uncle Bob Clean Code Videos as a Software Quality Engineer — This is what I learned</h3><p><strong>💬 Robert Martin</strong>; Also known as <strong>Uncle Bob</strong>, is a known figure in <strong>Software Engineering</strong> for his recommendations and writings and specificaly while looking for “<strong>Clean Code</strong>”.</p><p>🧑‍💻 While working as Software Quality Team Lead at Happn, a French social and dating application company, we’ve seen a new CTO arriving and one of the first things he did was a weekly tech meeting to review <strong>Uncle Bob</strong>’s videos on YouTube; which was really interesting and pushed us (both the tech and QA teams) to review our processes and incorporate more best practices.</p><p>💡 Here I would like to share with you what I learned from it and what I think is the most interesting in terms of software quality.</p><p>But before to dive into my understanding; let me bring to you those videos:</p><ul><li>📹 <a href="https://www.youtube.com/watch?v=7EmboKQH8lM"><strong>Clean Code — Uncle Bob / Lesson 1</strong></a></li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F7EmboKQH8lM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D7EmboKQH8lM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F7EmboKQH8lM%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e944856974efd49b22206a88166e108e/href">https://medium.com/media/e944856974efd49b22206a88166e108e/href</a></iframe><ul><li>📹 <a href="https://www.youtube.com/watch?v=2a_ytyt9sf8"><strong>Clean Code — Uncle Bob / Lesson 2</strong></a></li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F2a_ytyt9sf8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D2a_ytyt9sf8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F2a_ytyt9sf8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/25d9d8258278d9ef14ff685edf898429/href">https://medium.com/media/25d9d8258278d9ef14ff685edf898429/href</a></iframe><ul><li>📹 <a href="https://www.youtube.com/watch?v=Qjywrq2gM8o"><strong>Clean Code — Uncle Bob / Lesson 3</strong></a></li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FQjywrq2gM8o%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DQjywrq2gM8o&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FQjywrq2gM8o%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e109b141902455373a3ec0975eac8d3f/href">https://medium.com/media/e109b141902455373a3ec0975eac8d3f/href</a></iframe><ul><li>📹 <a href="https://www.youtube.com/watch?v=58jGpV2Cg50"><strong>Clean Code — Uncle Bob / Lesson 4</strong></a></li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F58jGpV2Cg50%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D58jGpV2Cg50&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F58jGpV2Cg50%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e3947321f1c2713c90aecc2cfbcf4391/href">https://medium.com/media/e3947321f1c2713c90aecc2cfbcf4391/href</a></iframe><ul><li>📹 <a href="https://www.youtube.com/watch?v=sn0aFEMVTpA"><strong>Clean Code — Uncle Bob / Lesson 5</strong></a></li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fsn0aFEMVTpA%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dsn0aFEMVTpA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fsn0aFEMVTpA%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f1784f7ee4996007d80b48b37ba34762/href">https://medium.com/media/f1784f7ee4996007d80b48b37ba34762/href</a></iframe><ul><li>📹 <a href="https://www.youtube.com/watch?v=l-gF0vDhJVI"><strong>Clean Code — Uncle Bob / Lesson 6</strong></a></li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fl-gF0vDhJVI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dl-gF0vDhJVI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fl-gF0vDhJVI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/1e56b641441ea3ee99ef6a4b8e929422/href">https://medium.com/media/1e56b641441ea3ee99ef6a4b8e929422/href</a></iframe><p>👀 Now let’s review them one by one…</p><h3>Lesson 1: The Importance of Clean Code</h3><p>In this first video, Uncle Bob sets the stage by explaining why clean code is crucial. He emphasizes that code is read far more often than it’s written, and messy code leads to:</p><ul><li><strong>Increased development time:</strong> It’s harder to understand and modify messy code, leading to wasted time and effort.</li><li><strong>Higher defect rates:</strong> Bugs are more likely to hide in convoluted code.</li><li><strong>Reduced team morale:</strong> Working with messy code is frustrating and demotivating.</li></ul><p>Uncle Bob argues that writing clean code is a professional responsibility and a matter of craftsmanship.</p><blockquote><em>“Clean code always looks like it was written by someone who cares.” — Uncle Bob</em></blockquote><p>He introduces the concept of code smells, which are indicators of deeper problems in the code. Some common code smells include:</p><ul><li><strong>Long methods:</strong> Methods that do too much are difficult to understand and maintain.</li><li><strong>Large classes:</strong> Classes with too many responsibilities are hard to reason about.</li><li><strong>Duplicated code:</strong> Repeated code blocks increase the risk of inconsistencies and errors.</li></ul><p><strong>Key takeaway:</strong> Clean code is essential for efficient software development and a healthy development team.</p><h3>Lesson 2: Naming and Comments</h3><p>This lesson focuses on the importance of meaningful names and effective comments. Uncle Bob stresses that names should be:</p><ul><li><strong>Descriptive:</strong> They should clearly indicate the purpose of the variable, function, or class.</li><li><strong>Unambiguous:</strong> There should be no confusion about what the name represents.</li><li><strong>Meaningful:</strong> The name should convey the intent of the code.</li></ul><p>He also provides guidance on using comments effectively:</p><ul><li><strong>Explain the “why,” not the “what”:</strong> Comments should clarify the reasoning behind the code, not just restate what the code already says.</li><li><strong>Keep comments concise and to the point:</strong> Avoid writing lengthy paragraphs when a few words will suffice.</li><li><strong>Update comments when the code changes:</strong> Outdated comments can be misleading and confusing.</li></ul><blockquote><em>“Don’t comment bad code — rewrite it.” — Uncle Bob</em></blockquote><p><strong>Key takeaway:</strong> Choosing good names and writing effective comments significantly improves code readability and maintainability.</p><h3>Lesson 3: Functions</h3><p>Uncle Bob dives into the principles of writing clean functions. He advocates for:</p><ul><li><strong>Small functions:</strong> Functions should be short and focused on a single task.</li><li><strong>Limited arguments:</strong> Functions with too many arguments are difficult to understand and use.</li><li><strong>No side effects:</strong> Functions should not modify anything outside their scope unexpectedly.</li><li><strong>One level of abstraction per function:</strong> Functions should operate at a consistent level of detail.</li></ul><p>He also discusses the importance of using descriptive function names and avoiding code duplication within functions.</p><blockquote><em>“Functions should do one thing. They should do it well. They should do it only.” — Uncle Bob</em></blockquote><p><strong>Key takeaway:</strong> Writing small, focused functions with clear names and no side effects leads to more modular and maintainable code.</p><h3>Lesson 4: Classes</h3><p>This lesson explores the principles of clean class design. Uncle Bob recommends:</p><ul><li><strong>Small classes:</strong> Classes should have a single, well-defined responsibility.</li><li><strong>High cohesion:</strong> The methods within a class should be closely related to each other and the class’s purpose.</li><li><strong>Low coupling:</strong> Classes should be loosely coupled to other classes to minimize dependencies.</li></ul><p>He also discusses the importance of encapsulation, which is the practice of hiding internal data and implementation details from other classes.</p><blockquote><em>“Classes should be small, with a clear and concise purpose.” — Uncle Bob</em></blockquote><p><strong>Key takeaway:</strong> Designing classes with a clear responsibility, high cohesion, and low coupling improves code organization and reduces complexity.</p><h3>Lesson 5: The SOLID Principles</h3><p>Uncle Bob introduces the SOLID principles, a set of five design principles that promote modularity, flexibility, and maintainability in object-oriented programming:</p><ul><li><strong>Single Responsibility Principle (SRP):</strong> A class should have only one reason to change.</li><li><strong>Open/Closed Principle (OCP):</strong> Software entities should be open for extension but closed for modification.</li><li><strong>Liskov Substitution Principle (LSP):</strong> Subtypes should be substitutable for their base types without altering the correctness of the program.</li><li><strong>Interface Segregation Principle (ISP):</strong> Clients should not be forced to depend on methods they don’t use.</li><li><strong>Dependency Inversion Principle (DIP):</strong> High-level modules should not depend on low-level modules. Both should depend on abstractions.</li></ul><p>He explains how applying these principles can lead to more robust and adaptable software designs.</p><p><strong>Key takeaway:</strong> The SOLID principles provide a framework for creating well-structured and maintainable object-oriented code.</p><h3>Lesson 6: Error Handling</h3><p>In this final lesson, Uncle Bob discusses the importance of effective error handling. He emphasizes:</p><ul><li><strong>Using exceptions instead of return codes:</strong> Exceptions provide a more structured and informative way to handle errors.</li><li><strong>Providing context with exceptions:</strong> Include relevant information in exception messages to aid in debugging.</li><li><strong>Don’t return null:</strong> Returning null can lead to NullPointerExceptions. Consider using exceptions or optional types instead.</li><li><strong>Don’t pass null:</strong> Passing null as an argument can cause unexpected behavior.</li></ul><p>He also discusses the importance of writing code that is resilient to errors and can gracefully recover from unexpected situations.</p><blockquote><em>“Error handling should be clear, concise, and informative.” — Uncle Bob</em></blockquote><p><strong>Key takeaway:</strong> Effective error handling is crucial for creating reliable and robust software.</p><h3>Conclusion</h3><p>Uncle Bob’s Clean Code video series provides valuable insights into writing high-quality code. By following his principles and best practices, developers can create software that is:</p><ul><li><strong>Easier to read and understand:</strong> This leads to faster development and fewer bugs.</li><li><strong>More maintainable and adaptable:</strong> Changes can be made more easily and with less risk.</li><li><strong>More reliable and robust:</strong> Effective error handling improves software stability.</li></ul><p>As a Software Quality Engineer, I found these videos to be incredibly helpful in reinforcing the importance of clean code and providing practical guidance on how to achieve it. I highly recommend this series to any developer who wants to improve their coding skills and create better software.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b21d15f0f89" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A real AI application for automation testing — Stabilise your automation tests with RAG]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@adrianpothuaud/a-real-ai-application-for-automation-testing-stabilise-your-automation-tests-with-rag-cd87479124b6?source=rss-73db18d1c271------2"><img src="https://cdn-images-1.medium.com/max/1613/1*wijv7JLcBfvmOxFRarZwbA.jpeg" width="1613"></a></p><p class="medium-feed-snippet">Enhance anyautomation frameworks with RAG for stable selector strategies! No implementation details but the complete method and examples.</p><p class="medium-feed-link"><a href="https://medium.com/@adrianpothuaud/a-real-ai-application-for-automation-testing-stabilise-your-automation-tests-with-rag-cd87479124b6?source=rss-73db18d1c271------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@adrianpothuaud/a-real-ai-application-for-automation-testing-stabilise-your-automation-tests-with-rag-cd87479124b6?source=rss-73db18d1c271------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd87479124b6</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[flaky-tests]]></category>
            <dc:creator><![CDATA[Adrian Pothuaud]]></dc:creator>
            <pubDate>Tue, 05 Nov 2024 04:27:21 GMT</pubDate>
            <atom:updated>2026-05-11T14:11:30.639Z</atom:updated>
        </item>
    </channel>
</rss>