<?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 Mirko Di Lucia on Medium]]></title>
        <description><![CDATA[Stories by Mirko Di Lucia on Medium]]></description>
        <link>https://medium.com/@mirkodilucia?source=rss-893593c067dd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jn1YK4EnFtTop2L-TJDrPw.jpeg</url>
            <title>Stories by Mirko Di Lucia on Medium</title>
            <link>https://medium.com/@mirkodilucia?source=rss-893593c067dd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:57:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mirkodilucia/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[Harmonizing Design and Development: The Collaborative Power of Elty App Design System]]></title>
            <link>https://medium.com/@mirkodilucia/harmonizing-design-and-development-the-collaborative-power-of-elty-app-design-system-a1b81417281a?source=rss-893593c067dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1b81417281a</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[react-native]]></category>
            <dc:creator><![CDATA[Mirko Di Lucia]]></dc:creator>
            <pubDate>Tue, 15 Oct 2024 09:05:51 GMT</pubDate>
            <atom:updated>2024-10-15T09:05:51.572Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uhF1C_7ZLCLenUQPyNhrVA.png" /></figure><p>At Elty, we recently embarked on a journey to develop a brand-new design system as part of a larger rebranding initiative. This wasn’t just a visual refresh — it was an opportunity to streamline our entire development process, improve performance, and build a system that would allow us to scale effortlessly in the future.</p><p>As a developer, you understand the importance of a streamlined development process and consistent UI in creating successful applications.</p><p>Our design team delivered an exciting vision as part of our company’s rebranding. We had just two months to restyle our entire mobile app and refactor the existing design system. As developers, we immediately understood the gravity of this challenge: it wasn’t just about making things look good; it was about laying down the foundation for a sustainable, scalable, and efficient codebase.</p><p>In this article, I’ll walk you through the steps we took to build this design system, how we collaborated with our design team, and the lessons we learned along the way.</p><h3>The Essence of Design Systems</h3><p>A design system serves as the foundation of a product’s UI, providing a consistent set of styles, components, and guidelines that create a seamless and visually cohesive experience for users.</p><p>During our evaluation of various libraries to aid in this process, we encountered challenges related to performance and integration. Ultimately, we decided to build our custom design library specifically for the mobile app, leveraging the capabilities and flexibility that React Native offers.</p><h3>Build Up Design System from the foundation</h3><p>The first step was gathering a clear set of requirements. Our design team provided us with a detailed rebranding guide that outlined colors, typography, iconography, and various UI components. However, these were just visual guidelines. As developers, we needed to interpret these into reusable components and styles that could be applied consistently across the app.</p><p>Here’s what we aimed to achieve:</p><ul><li><strong>Consistency:</strong> Ensuring that every button, text input, and header followed the new visual guidelines.</li><li><strong>Performance:</strong> Since our product needed to run smoothly on both high-end and low-end devices, performance optimization was critical.</li><li><strong>Scalability:</strong> The new system had to be flexible enough for future feature development without unnecessary rewrites.</li></ul><p>We quickly realized that achieving these goals required more than just swapping out colors and fonts. It required us to rethink the architecture of our components and create a design system that would empower both the developers and the design team.</p><h3>Collaboration with Designers</h3><p>The opportunity to rebrand our products, allows us to reduce the gap between designers and developers, making collaboration smoother and more efficient. Here’s how to make the most of this collaboration:</p><ol><li><strong>Start with the Basics:</strong> The foundational components, such as buttons, text fields, and cards. These elements form the building blocks of the application UI.</li><li><strong>Share Design Tokens:</strong> Provide designers with the design tokens we defined in the theme. This ensures that the colors, typography, and spacing used in the designs are consistent with the implementation.</li><li><strong>Apply Design Tokens:</strong> Use the design tokens to defined earlier to maintain consistency. This ensures that the same colors, typography, and spacing are used consistently across the app.</li><li><strong>Component Preview:</strong> Use tools like Figma or Sketch to create component previews that designers can review. This helps designers understand how components look and behave in the app.</li><li><strong>Iterative Feedback:</strong> Encourage designers to provide iterative feedback on the implementation. They can use the app in development or view interactive prototypes to assess the user experience and suggest improvements.</li><li><strong>Collaborate:</strong> Invite developers to the Figma project. They can inspect the components, copy code snippets, and provide feedback directly within Figma.</li></ol><h3>Documenting the Design System</h3><p>Clear documentation is essential for the success of a design system. As a developer, we play a crucial role in documenting the technical aspects of the system:</p><ol><li><strong>Component Usage:</strong> Document how to use each component, including examples and recommended props, including variations, states, and any specific interactions.</li><li><strong>Design Tokens:</strong> Provide a comprehensive list of design tokens, including values, use cases, and updates made over time.</li><li><strong>Responsive Design Guidelines:</strong> Explain how components adapt to different screen sizes and orientations.</li><li><strong>Developer Handoff:</strong> Offer guidelines for other developers on how to use the new DS to implement components and styles.</li></ol><h3>Iteration, Continuous Improvement, and Maintenance</h3><p>A design system is a living entity that evolves. As a developer, we play a role in maintaining and improving the design system as the app grows and new design requirements arise. Encourage regular review meetings between designers and developers to address challenges, improvements, and new design needs. Use versioning tools in figma and storyblock and commenting features to track changes and maintain a record of discussions.</p><h3>Conclusion</h3><p>Developing a design system for a React Native app using Figma is a powerful way to establish a common language between designers and developers. It promotes consistency, speeds up development, and results in a better user experience.</p><p>By setting up design tokens, creating styled components, collaborating effectively with designers, and documenting the system comprehensively, we create a powerful design system that helps to accelerate the development of future features.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1b81417281a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Streamlining Excellence: Navigating Our Mobile App’s Functional Review Process]]></title>
            <link>https://medium.com/@mirkodilucia/streamlining-excellence-navigating-our-mobile-apps-functional-review-process-0388a279c49d?source=rss-893593c067dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/0388a279c49d</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Mirko Di Lucia]]></dc:creator>
            <pubDate>Wed, 15 Nov 2023 08:55:59 GMT</pubDate>
            <atom:updated>2023-11-15T08:55:59.374Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CRrsO-6yUzNiWgUDsXP0Hg.png" /></figure><p>In today’s fast-paced world, mobile app development is a constant race to innovate, iterate, and deliver a flawless user experience. To achieve this, a seamless functional review process is essential. In this article, we’ll explore how to streamline this process using a combination of GitHub Actions, and Expo updates, making your development workflow more efficient and reducing the time to market for your mobile apps.</p><h3>The Importance of a Robust Functional Review Process</h3><p>Before we dive into the technical details, let’s emphasize the significance of a robust functional review process. This process ensures that your mobile app meets quality standards, is free of critical bugs, and provides a consistent user experience. Failing to establish an effective review process can lead to user dissatisfaction, revenue loss, and damage to your app’s reputation.</p><h3>Leveraging GitHub Actions for Continuous Integration</h3><p>GitHub Actions is a powerful tool that allows you to automate various tasks in your software development workflow. By integrating GitHub Actions into your mobile app development process, you can automate build and testing procedures, ensuring that every code change is thoroughly evaluated.</p><ol><li><strong>Setting up GitHub Actions Workflow</strong>: Create a GitHub Actions workflow that triggers every push to the main branch. This workflow should include steps for building the app, running tests, and generating artifacts.</li><li><strong>Automated Testing</strong>: Incorporate automated testing suites into your workflow. This ensures that new code changes don’t introduce critical regressions. Consider using popular testing frameworks like Jest for React Native apps.</li><li><strong>Code Linting</strong>: Include code linting and prettier check tools to maintain code quality. Tools like ESLint and TypeScript can catch potential issues early in the development process.</li><li><strong>Static Analysis</strong> Using external statics analysis check to maintain clean code, and detect duplications and code smells</li><li><strong>Translations report</strong> check if our apps maintains consistency between translations in differents languages</li><li><strong>QR Code generation</strong> for human overview of the task. I’ll explain later in this articles</li></ol><h3>Expo Updates for Effortless Over-the-Air Updates</h3><p>Expo is a helpfull tool for React Native development, offering a range of features that simplify the app development process. One standout feature is Over-the-Air (OTA) updates, which allow you to deliver updates to your app without requiring users to download a new version from an app store.</p><ol><li><strong>Implementing Expo Updates</strong>: Configure your app to use Expo updates. This enables you to push critical bug fixes, performance improvements, and new features to users quickly.</li><li><strong>Version Management</strong>: Maintain a clear versioning strategy for your app. Use semantic versioning to ensure consistency and clarity when rolling out updates.</li><li><strong>Automated the functional review process</strong>: integrated with github actions help the team in DaVinci to stay aligned on the development of the product</li></ol><pre># 1. Setup node<br># 2. Setup Expo<br># 3. Load dependencies<br># 4. Publish eas update on banch<br>- name: Publish eas update on branch<br>  id: preview<br>  run: |<br>  yarn workspace &lt;project-name&gt; eas update <br>    --branch=${{ github.head_ref }} <br>    --message=&quot;Preview of branch ${{ github.head_ref }}&quot;<br>  EAS_UPDATE_URL=&quot;&lt;app-bundle-id&gt;://expo-development-client/?url=https://u.expo.dev/&lt;app-identifier-in-expo&gt;&amp;channel-name=${{ github.head_ref }}&quot;<br>  URL_ENCODED_UPDATE_SCHEME=&quot;$(node -e &quot;console.log(encodeURIComponent(&#39;$EAS_UPDATE_URL&#39;))&quot;)&quot;<br>  QR_IMG_URL=&quot;https://api.qrserver.com/v1/create-qr-code/?size=128x128&amp;data=$URL_ENCODED_UPDATE_SCHEME&quot;<br>  echo &quot;eas-update-url=$EAS_UPDATE_URL&quot; &gt;&gt; $GITHUB_OUTPUT<br>  echo &quot;eas-update-url-qr-url=$QR_IMG_URL&quot; &gt;&gt; $GITHUB_OUTPUT<br># 5. Comment deployment link with QR code<br></pre><p><strong>The Agile process</strong></p><p>Our Agile process for introducing new functionalities into production consists of these simple steps:</p><ol><li><strong>PM &amp; Marketing: </strong>Propose and introduce a new service/feature to our app.</li><li><strong>Project Manager (PM): </strong>Decide how to distribute different types of tasks between designers and developers.</li><li><strong>Designers: </strong>With the use of Figma designers create new screens and components for development. Include this information in a story within a Kanban board.</li><li><strong>Developers: </strong>Develop the assigned task. Request another developer to review their code.</li><li><strong>Designers (Post-Development): </strong>Participate in a functional review to ensure that programmers have correctly implemented the task.</li><li><strong>Pull Request (PR) Process: </strong>When a developer opens a Pull Request on our repository, GitHub Actions automatically initiate.<br>As part of these actions, a QR code is generated and added to GitHub comments and the corresponding task on the Kanban board.</li><li><strong>DaVinci App Integration: </strong>Designers, using the installed DaVinci app, can scan the QR code to access the build associated with the code in the pull request.</li><li><strong>Review and Approval: </strong>After reviewing the build, designers have the authority to approve the task, marking it as ready for merging into the main branch.</li></ol><p>By following these streamlined steps, our Agile process ensures effective collaboration across all’s figures every team in our company, leveraging tools like Figma, GitHub Actions, and the DaVinci app to enhance efficiency and maintain the quality of our software development lifecycle.</p><p><strong>The importance of humans in this process</strong></p><p>The importance of human supervision during the functional review process cannot be overstated. While automated testing and code analysis tools play a crucial role in identifying potential issues and ensuring code quality, human intervention adds a layer of nuanced understanding and critical evaluation that is irreplaceable.</p><p>Incorporating human supervision into the functional review process brings several advantages. Firstly, human reviewers, particularly designers who have an intimate knowledge of the app’s user interface and design principles, can assess the user experience comprehensively.</p><ul><li>They can identify subtleties and nuances that automated tools might overlook, ensuring that the app not only functions correctly but also provides a seamless and intuitive experience for end-users.</li><li>Secondly, human reviewers contribute to the detection of potential design inconsistencies or deviations from the established design guidelines.</li></ul><p>This human touch is invaluable in maintaining a cohesive and visually appealing user interface, aligning with the overall user experience strategy.</p><p>Furthermore, human supervision ensures that the functionality aligns with the initial design intent and user requirements. Designers can evaluate whether the implemented features meet the project’s design specifications and whether any adjustments are needed to enhance usability or visual aesthetics.</p><p>In summary, the inclusion of human supervision in the functional review process acts as a crucial checkpoint to guarantee that the app not only meets technical requirements but also excels in user satisfaction and aligns with the overarching design vision. This blend of automated tools and human expertise creates a robust and comprehensive evaluation process, ultimately leading to the delivery of a high-quality and user-friendly product.</p><p>A streamlined functional review process is the backbone of successful mobile app development. This approach not only improves the quality of your app but also accelerates your time to market, giving a competitive edge in the dynamic world of mobile app development.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0388a279c49d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mobile App Development: Confronting and Conquering Challenges]]></title>
            <link>https://medium.com/@mirkodilucia/mobile-app-development-confronting-and-conquering-challenges-6bf5a09d2c37?source=rss-893593c067dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/6bf5a09d2c37</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Mirko Di Lucia]]></dc:creator>
            <pubDate>Wed, 20 Sep 2023 09:43:51 GMT</pubDate>
            <atom:updated>2023-09-20T09:43:51.346Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J4ci_dUlCSmkRQoVBOxr1Q.png" /></figure><p>In October 2022, I joined DaVinci Salute, an Italian startup focused on innovate the national healthcare market by leveraging the power of technology.</p><p>I started as a full-stack developer for the web app, but soon after, an opportunity presented itself when the developer who had created the mobile app left for a new position at one of the FAANG companies.</p><p>When DaVinci offered me the chance to spearhead the continued development of a mobile app, I saw it not just as a task, but as a call to action. This was an opportunity to take part in shaping the future of technology and user experiences. Accepting the challenge meant stepping out of my comfort zone and embracing new responsibilities, but it also meant contributing to a project that had the potential to impact thousands of users. Drawing from my previous experiences in developing mobile apps using React Native, I find myself well-equipped to seamlessly take up the reins.</p><p>Throughout this article, I will share valuable insights and advice on how to navigate a challenge similar to the one I undertook.</p><p><strong>1. Understanding the Project Architecture</strong></p><p>Getting up to speed with an existing project’s architecture is a pivotal challenge.</p><ul><li>Layout of components</li><li>Navigation</li><li>State management</li><li>Network Integration</li><li>Libraries</li><li>Security measures</li><li>UI/UX</li><li>Design system</li><li>Information Flows</li></ul><p>Start by meticulously studying the codebase, analyzing the folders structure, and identifying key modules. Reach out to your team for guidance and documentation that could help you comprehend the project’s architecture better.</p><p><strong>2. Knowledge of Libraries and Dependencies</strong></p><p>React Native projects often rely on numerous third-party libraries and dependencies. Familiarize yourself with these libraries’ functionalities, usage, and potential pitfalls is essential. Ensure you have access to documentation and be prepared to invest time in experimentation to understand how these components integrate into the project.</p><p>Comparing different libraries within a React Native project can be an essential step in gaining a better understanding of its architecture and implementation. Here’s how this process can help:</p><ul><li><strong>Informed library choices</strong>: Within a React Native project, you might face decisions regarding various libraries for similar tasks, such as state management or network integration. Comparing available options will help you select the library that best suits the project’s needs based on compatibility, features, and performance.</li><li><strong>Understanding existing solutions:</strong> Examining different libraries will give you a clearer idea of the solutions the team has chosen previously. This could lead you to discover innovative approaches and best practices that you could apply in other parts of the project.</li><li><strong>Hands-on experience:</strong> Designing and developing small experiments using different libraries will allow you to gain practical insight into their capabilities and limitations. This hands-on experience can guide you in making informed decisions when implementing complex features within the project.</li></ul><p><strong>3. Syncing with the Team Workflow</strong></p><p>When I moved into app development. The workflow team wasn’t complete yet.</p><p>So adapting to the team’s workflow, version control practices, and communication channels became a daunting task.</p><p>Like other companies, we use tools like:</p><ul><li><strong>Git </strong>to manage code changes effectively, and receive a review each time we introduce a new feature or a fix.</li><li><strong>CI/CD</strong> pipelines to release new versions of the app in AppStore and Google Play</li><li><strong>Shortcut</strong> to take track, plan and organize new features and bugs to solve</li></ul><p>But also we use some special handcraft tools like:</p><ul><li><strong>Functional Review</strong> pipeline, based on eas update that helps the design team to review a task completed by the developer without accessing the codebase</li><li><strong>Slack notification channels</strong> to avoid using real push notifications, email, and sms in the staging environment</li><li><strong>Slack bots</strong> for real-time monitoring of app incidents in production</li><li><strong>Custom design system</strong> based on tailwind and deeply integrated with Figma</li></ul><p>Gaining knowledge of these tools led me to communicate out of the box with the design team and other non-tech people at DaVinci.</p><p><strong>4. Grasping UI/UX Guidelines</strong></p><p>The app has already been under development for two years, we have a large set of existing UI components and existing guidelines in place.</p><p>Our app does use a proprietary design system. We use these approaches to follow the web app style, trying to emulate Tailwind.</p><p>The entire design system stays on Figma boards where developers can understand and adhere to these guidelines provided by the design team to maintain a consistent user experience.</p><p>Studying any existing design documentation and discussing with designers to clarify any ambiguities is crucial.</p><p>In DaVinci, we believe in strong collaboration among teams. Often developers and designers collaborate to make decisions on how we implement new sections in our apps.</p><p>Normally, our process that brings an idea to life starts from the design team that ideate the app template on Figma for a new section of the app and choosing the best:</p><ul><li><strong>Colors</strong></li><li><strong>Spacings</strong></li><li><strong>Typography</strong></li><li><strong>Components</strong></li><li><strong>Screen</strong></li><li><strong>App Information Flow</strong></li><li><strong>Behavior</strong></li></ul><p>The new sections are overseen by tech leads, who make decisions on task creation and work distribution among the development team to bring Figma boards to life.</p><p>During iterations, when a developer’s task successfully passes the code review, the design team conducts a functional review to ensure adherence to the guidelines presented on the Figma boards.</p><p>This harmonious partnership transforms concepts into tangible, user-centric experiences, elevating the DaVinci app to a level of excellence that seamlessly blends innovation and aesthetics.</p><p><strong>5. Adhering to Best Practices</strong></p><p>Ensuring that the app code aligns with industry best practices is crucial for maintainability and scalability. However, learning these best practices while jumping into an ongoing project can be challenging.</p><p>I dedicate time to research and understanding React Native coding standards, component scaffolding, state management best practices, networking layer, navigation, and the custom UI library.</p><p>After that, I started to write a list of the pros and cons of all design choices for the app.</p><p>Extract from it all the things that need refactoring following the TDD practices to avoid breaking the application.</p><p>In particular, we focus on:</p><ol><li><strong>Navigation Hierarchy Testing</strong>: Develop a comprehensive test suite that covers the navigation flow in the app. As you refactor the navigation to support a deeper hierarchy (if necessary), these tests will serve as a safety net, ensuring that navigation remains functional and intuitive.</li><li><strong>Enhance Caching with Testing</strong>: Introduce robust tests for caching mechanisms to handle varying data sizes and scenarios. As you refactor to improve caching, these tests will ensure data integrity and cache performance while avoiding regressions.</li></ol><p><strong>6. Communication with the previous developer</strong></p><p>The previous developer, a talented individual, demonstrated remarkable skills in independently developing a React Native app from scratch. His expertise allowed us to define the entire app lifecycle, from the initial concept to deployment. His control over core React Native concepts, such as component-based architecture and JSX, allowed them to create well-structured and efficient code.</p><p>An open line of communication with the developer to discuss design decisions and architectural choices.</p><p>Discuss with them the hidden intricacies within the code base to dispel any doubts.</p><p>Their insights can provide a wealth of information that aids your participation in the project.</p><p>With a strong grasp of the state management library, the developer ensured the app’s data flow was seamless and predictable. They showcased a keen ability to implement complex UI designs, making the app visually appealing while maintaining responsiveness across different devices.</p><p>My previous experiences in developing a mobile app in react native make it possible for me to pick up the reins without needing to delve deep into the implementation specifics.</p><p><strong>7. Balancing Speed and Quality</strong></p><p>The urge to catch up and swiftly contribute could potentially compromise code quality. Establishing equilibrium between timely delivery and upholding code excellence stands as a critical objective. We readily extend the timeline when necessary to ensure your contributions exhibit both efficiency and robustness.</p><p>To strike an optimal balance between quality and velocity, we’ve embraced a pre commit phase where code undergoes rigorous checks:</p><ul><li><strong>Prettier:</strong> Ensuring adherence to app-wide formatting guidelines.</li><li><strong>ESLint:</strong> Upholding rule compliance.</li><li><strong>TypeScript Compiler (TSC): </strong>Requiring error-free, warning-free builds.</li><li><strong>Unit Tests:</strong> Safeguarding components integrity to prevent any compromise.</li></ul><p>At every step, our emphasis remains on delivering at pace without compromising the integrity of our codebase.</p><p>Finally, the code review and functional review processes culminate in a comprehensive assessment of the development efforts, ensuring both the technical aspects and user-centric functionalities align seamlessly with the project’s goals.</p><p><strong>Conclusion</strong></p><p>Joining a React Native project that’s already in progress can be a challenge, but it’s also an opportunity for growth and skill development. By tackling the challenges of understanding architecture, libraries, team workflows, UI/UX guidelines, debugging, best practices, and communication effectively, you can smoothly transition into your new role and contribute meaningfully to the project’s success. Remember that learning from your colleagues, seeking guidance, and staying calm and patient will be key factors in your journey to becoming a valuable asset to the team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6bf5a09d2c37" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Test-Driven Development (TDD)]]></title>
            <link>https://medium.com/@mirkodilucia/test-driven-development-tdd-ae2db87ce042?source=rss-893593c067dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae2db87ce042</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[solid]]></category>
            <category><![CDATA[softare-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[test-driven-development]]></category>
            <dc:creator><![CDATA[Mirko Di Lucia]]></dc:creator>
            <pubDate>Sun, 10 Sep 2023 17:28:33 GMT</pubDate>
            <atom:updated>2023-09-10T17:35:13.369Z</atom:updated>
            <content:encoded><![CDATA[<h4>A Comprehensive Overview</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9J-aGX4x6GQnKE9LnYwanQ.jpeg" /><figcaption>Photo taken during my trip in Bologna</figcaption></figure><h3><strong>1. Introduction to TDD</strong></h3><p>Test-Driven Development (TDD) is a software development approach where developers write automated tests for a piece of functionality before they write the actual code to implement that functionality.</p><p>TDD places a strong emphasis on the continuous validation of code through automated testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/460/0*W537ZKxl_FlGkJN1" /><figcaption><strong>Kent Beck</strong>, a renowned software engineer and author, is credited with formalizing the TDD methodology in the early 2000s as part of Extreme Programming (XP).</figcaption></figure><h3><strong>2. TDD Process</strong></h3><p>The TDD process typically follows a cycle of three phases:</p><ul><li><strong>Red</strong>: In this phase, write the test that we suppose to fail</li><li><strong>Green</strong>: When a test passes, write the code necessary to pass the test</li><li><strong>Refactor</strong>: improve the code quality and reduce complexities</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lo31yjJW9mGy7F8sfhn2Rg.jpeg" /><figcaption>TDD process</figcaption></figure><h3><strong>3. Key Benefits of TDD</strong></h3><p>TDD holds significant importance in software development due to its ability to:</p><ul><li><strong>Early Issue Detection</strong>: TDD catches defects and design flaws at an early stage breaking code behaviour</li><li><strong>Enhanced Code Quality: </strong>promotes the creation of modular, well-structured code that is easier to understand and maintain</li><li><strong>Accelerated Debugging: </strong>It speeds up debugging by quickly identifying regressions when tests fail and aiding in pinpointing issues</li><li><strong>Improved Collaboration: </strong>by providing clear specifications through test cases, enhancing communication within development teams</li><li><strong>Confidence in Changes:</strong> Developers can confidently make changes knowing that passing tests validate the correctness of their modifications</li></ul><h3><strong>4. TDD Habits</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GDWTAjm4fyz8mxlM" /></figure><p>Practicing TDD consistently and maintaining a focus on test-driven development as a fundamental part of the development process</p><ul><li><strong>Running Tests Frequently:</strong> Frequent test execution is crucial for detecting issues early.</li><li><strong>Refactoring Regularly:</strong> Refactoring involves improving code without altering its functionality.</li><li><strong>Keeping Test Cases Up-to-Date</strong>: As the codebase evolves, tests must evolve with it.</li></ul><h3><strong>5. MOB Programming</strong></h3><p><strong>Collaborative Excellence</strong></p><p>MOB Programming is a software development technique where an entire team collaboratively works on a single task or user story using a single computer.</p><p><strong>How It Works:</strong></p><ul><li><strong>All the team</strong> gather around one workstation, with one person at the keyboard (the “driver”).</li><li><strong>The driver:</strong> writes code based on the team’s discussions and decisions.</li><li><strong>The navigator:</strong> helps guide the direction of the code and ensures it aligns with the team’s goals and standards, he also asks questions and research solutions.</li><li><strong>Other team members:</strong> actively participate by offering suggestions, discussing solutions, and reviewing code.</li><li><strong>Periodically rotation: </strong>of roles to ensure everyone’s involvement.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*69nQuJUITEUN9miv" /><figcaption>A typical MOB session</figcaption></figure><p><strong>Benefits</strong></p><ul><li><strong>Enhanced Collaboration: </strong>MOB Programming fosters real-time communication and knowledge sharing among team members, resulting in stronger collaboration and a shared understanding of the codebase.</li><li><strong>Reduced Silos: </strong>Team members become familiar with different aspects of the project, reducing dependencies on individual experts and siloed knowledge.</li><li><strong>Higher Code Quality:</strong> Continuous peer review and collective decision-making lead to improved code quality, fewer bugs, and better design decisions.</li><li><strong>Rapid Problem Solving:</strong> Issues are addressed promptly as the entire team brainstorms solutions, leading to faster problem-solving and quicker development cycles.</li><li><strong>Increased Learning: </strong>Team members can learn from each other, accelerating the onboarding of new team members and skill development.</li><li><strong>Ownership and Accountability</strong>: The team collectively owns the code, fostering a sense of shared responsibility and accountability.</li></ul><p><strong>Challenges</strong></p><ul><li><strong>Resource Intensive: </strong>MOB Programming may require additional resources, such as extra workstations.</li><li><strong>Role Fatigue:</strong> The driver may experience mental fatigue if not rotated frequently.</li></ul><h3>6. Transformation Priority Premise</h3><p>TPP defines a hierarchy of transformations that should be followed in TDD:</p><ul><li>TPP suggests that there is an ideal sequence for transforming code to achieve simplicity and maintainability incrementally.</li><li>Following this transformation hierarchy in TDD helps developers make incremental changes to their code while maintaining working tests.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/122/1*tDtbQ2F1sHymexdEMBccEg.png" /><figcaption>Sequence for transforming and simplify code</figcaption></figure><h3>7. Principles for Cleaner Code for Cleaner Code</h3><p>Object Calisthenics is a set of ten guiding principles aimed at promoting clean, maintainable, and efficient code. These principles help developers write code that is more readable, modular, and less error-prone.</p><ol><li><strong>One Level of Indentation Per Method</strong>: Keep your methods focused and easy to understand by limiting the number of nested blocks.</li><li><strong>Avoid the ELSE Keyword</strong>: Reduce code complexity by finding ways to structure your conditionals without using “else.”</li><li><strong>Wrap All Primitives and Strings</strong>: Encapsulate primitive data types in custom classes to enhance code readability and maintainability.</li><li><strong>First-Class Collections</strong>: Wrap collections in your own classes to encapsulate behavior and promote reusable code.</li><li><strong>One Dot Per Line</strong>: Limit the chaining of method calls to enhance code clarity and reduce complexity.</li><li><strong>No Abbreviations</strong>: Use descriptive names for variables and functions to improve code comprehension.</li><li><strong>Keep All Entities Small</strong>: Maintain small classes and methods to simplify debugging and maintenance.</li><li><strong>Limit Instance Variables</strong>: Avoid classes with more than two instance variables to ensure focused and cohesive classes.</li><li><strong>No Public Getters/Setters/Properties</strong>: Encapsulate data within your classes and avoid exposing internal state.</li><li><strong>All Classes Must Have State</strong>: Ensure that each class has a specific, meaningful purpose and encapsulates relevant state.</li></ol><h3>Conclusions</h3><p>We covered key points related to Test-Driven Development (TDD):</p><p>TPP helps developers make incremental changes to their code in a systematic way, prioritizing simplicity and maintainability.</p><p>By understanding these key points, developers can harness the power of TDD, cultivate effective habits, and apply the Transformation Priority Premise to create high-quality and maintainable software.</p><p>I have written this story after attending the first module about TDD with <a href="https://alcor.academy/">Alcor academy</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae2db87ce042" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>