<?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 Tchokouani Edy Michel on Medium]]></title>
        <description><![CDATA[Stories by Tchokouani Edy Michel on Medium]]></description>
        <link>https://medium.com/@edytchokouani?source=rss-3058869e6702------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Tchokouani Edy Michel on Medium</title>
            <link>https://medium.com/@edytchokouani?source=rss-3058869e6702------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 13:23:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@edytchokouani/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[️ Architecture Hexagonale & Clean Code en Java : La clé pour des applications robustes et…]]></title>
            <link>https://medium.com/@edytchokouani/%EF%B8%8F-architecture-hexagonale-clean-code-en-java-la-cl%C3%A9-pour-des-applications-robustes-et-4548111b10a4?source=rss-3058869e6702------2</link>
            <guid isPermaLink="false">https://medium.com/p/4548111b10a4</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[spring-boot]]></category>
            <dc:creator><![CDATA[Tchokouani Edy Michel]]></dc:creator>
            <pubDate>Wed, 26 Feb 2025 20:17:53 GMT</pubDate>
            <atom:updated>2025-02-26T20:17:53.862Z</atom:updated>
            <content:encoded><![CDATA[<h3>🏗️ Architecture Hexagonale &amp; Clean Code en Java : La clé pour des applications robustes et évolutives</h3><p>Le développement d’applications Java évolue rapidement, et pourtant, beaucoup de projets finissent par devenir des <strong>monolithes spaghetti</strong> difficiles à maintenir. Les dépendances s’entrelacent, les services deviennent de plus en plus couplés, et chaque modification risque de casser une partie du système.</p><p>C’est là qu’intervient <strong>l’architecture hexagonale</strong>, une approche qui permet de concevoir des systèmes évolutifs, testables et bien structurés.</p><p>Dans cet article, nous allons voir :<br>✅ <strong>Pourquoi les applications Java deviennent difficilement maintenables ?</strong><br>✅ <strong>Les principes de l’architecture hexagonale</strong> et comment les appliquer en Java (avec Spring Boot).<br>✅ <strong>Un exemple de projet structuré avec une séparation claire des couches.</strong><br>✅ <strong>Les avantages de cette approche</strong> et comment elle favorise un clean code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UUdUdxOEQR3iWgMPPWSisQ.jpeg" /></figure><h3>🚨 Le problème des monolithes mal structurés</h3><p>Dans beaucoup d’applications Java, l’architecture classique ressemble à ceci :</p><blockquote>/src<br> ├── controllers/<br> ├── services/<br> ├── repositories/<br> ├── models/</blockquote><p>Cette structure paraît logique, mais elle entraîne souvent un <strong>couplage excessif entre les couches</strong> :<br>❌ <strong>Les services appellent directement les repositories</strong>, rendant difficile leur remplacement ou leur testabilité.<br>❌ <strong>Les contrôleurs sont remplis de logique métier</strong>, ce qui complique leur évolution.<br>❌ <strong>Chaque changement dans la base de données impacte toute l’application</strong>, rendant le code fragile.</p><p>Ce couplage crée un effet boule de neige : <strong>plus on ajoute de fonctionnalités, plus l’application devient un cauchemar à maintenir.</strong></p><h3>🔷 L’architecture hexagonale : une approche plus propre</h3><p>L’<strong>architecture hexagonale</strong> (ou <strong>Ports and Adapters</strong>, introduite par Alistair Cockburn) propose de <strong>séparer clairement le cœur de l’application</strong> des détails d’implémentation comme la base de données, les frameworks et les interfaces utilisateurs.</p><h3>📌 Principe clé</h3><p><strong>Le cœur métier ne dépend pas des détails techniques.</strong> Ce sont les <strong>détails qui doivent s’adapter au domaine métier</strong>, et non l’inverse.</p><h3>📐 Structure de l’architecture hexagonale en Java</h3><blockquote>/src<br> ├── application/ # Cas d’usage &amp; logique métier (Application Layer)<br> ├── domain/ # Entités et règles métier (Domain Layer)<br> ├── infrastructure/ # Implémentations techniques (Infrastructure Layer)<br> ├── adapters/ # Connexions externes (Ports &amp; Adapters)<br> ├── config/ # Configuration Spring Boot</blockquote><p>💡 <strong>Pourquoi cette approche est meilleure ?</strong><br>✅ <strong>Le domaine métier est indépendant</strong> du framework (Spring, Hibernate…).<br>✅ <strong>Les tests unitaires deviennent faciles</strong> car la logique est découplée des dépendances.<br>✅ <strong>L’application est plus modulaire et évolutive</strong> : on peut changer de base de données sans impacter le cœur du système.</p><h3>⚙️ Implémentation en Java avec Spring Boot</h3><h3>1️⃣ Définir le domaine métier</h3><p>Le <strong>domaine</strong> contient les <strong>entités et règles métiers</strong>. Il ne dépend d’aucune base de données ni framework.</p><blockquote>// Domain Layer (Pure Java)<br>public class Account {<br> private String id;<br> private double balance;</blockquote><blockquote>public Account(String id, double balance) {<br> this.id = id;<br> this.balance = balance;<br> }</blockquote><blockquote>public void deposit(double amount) {<br> if (amount &lt;= 0) throw new IllegalArgumentException(“Amount must be positive”);<br> this.balance += amount;<br> }</blockquote><blockquote>public void withdraw(double amount) {<br> if (amount &gt; balance) throw new IllegalStateException(“Insufficient funds”);<br> this.balance -= amount;<br> }<br>}</blockquote><p>👉 Ici, <strong>aucune dépendance Spring Boot ou Hibernate</strong>. <strong>Juste du Java pur.</strong></p><h3>2️⃣ Créer les ports (interfaces)</h3><p>Les ports définissent <strong>les interactions possibles avec le domaine</strong>.</p><blockquote>// Port (Interface)<br>public interface AccountRepository {<br> Account findById(String id);<br> void save(Account account);<br>}</blockquote><h3>3️⃣ Implémenter les Adapters (Détails techniques)</h3><p>Les <strong>adapters</strong> sont les implémentations concrètes des ports.</p><blockquote>// Infrastructure Layer — Implémentation avec Spring Data JPA<br><a href="http://twitter.com/Repository">@Repository</a><br>public class JpaAccountRepository implements AccountRepository {<br> <br> <a href="http://twitter.com/Autowired">@Autowired</a><br> private AccountJpaRepository jpaRepository;</blockquote><blockquote><a href="http://twitter.com/Override">@Override</a><br> public Account findById(String id) {<br> return jpaRepository.findById(id).orElse(null);<br> }</blockquote><blockquote><a href="http://twitter.com/Override">@Override</a><br> public void save(Account account) {<br> jpaRepository.save(account);<br> }<br>}</blockquote><p>🔎 <strong>Les bénéfices</strong> :<br>✅ <strong>Si on change la base de données (MySQL → MongoDB),</strong> seule cette classe est impactée.<br>✅ <strong>Le domaine métier reste intact.</strong></p><h3>4️⃣ Utiliser les services d’application</h3><p>La <strong>couche application</strong> gère les cas d’usage (use cases).</p><blockquote>// Application Layer<br><a href="http://twitter.com/Service">@Service</a><br>public class AccountService {<br> private final AccountRepository accountRepository;</blockquote><blockquote><a href="http://twitter.com/Autowired">@Autowired</a><br> public AccountService(AccountRepository accountRepository) {<br> this.accountRepository = accountRepository;<br> }</blockquote><blockquote>public void deposit(String accountId, double amount) {<br> Account account = accountRepository.findById(accountId);<br> account.deposit(amount);<br> accountRepository.save(account);<br> }<br>}</blockquote><p>Ici, <strong>le service ne dépend que de l’interface AccountRepository</strong> ✅<br>Il peut être <strong>testé facilement avec un mock.</strong> ✅</p><h3>🎯 Les avantages concrets pour votre projet</h3><p>🚀 <strong>Testabilité</strong> → On peut tester la logique métier <strong>sans dépendre de Spring Boot ou d’une base de données</strong>.<br>📦 <strong>Modularité</strong> → Les différentes parties du code sont indépendantes et facilement remplaçables.<br>🔄 <strong>Évolutivité</strong> → Ajoutez une API REST, GraphQL ou une CLI sans modifier la logique métier.</p><h3>📌 Conclusion</h3><p>L’<strong>architecture hexagonale</strong> permet de créer des applications <strong>évolutives, maintenables et faciles à tester</strong>.</p><p>🔥 <strong>Si vous travaillez sur un projet Java avec Spring Boot, adopter cette architecture vous aidera à éviter les pièges du couplage excessif et à bâtir un système robuste.</strong></p><p>💡 <strong>Qu’en pensez-vous ? Avez-vous déjà appliqué cette approche sur vos projets Java ?</strong></p><p>#Java #SpringBoot #CleanCode #Architecture #Développement</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4548111b10a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The starter git commands for beginner]]></title>
            <link>https://medium.com/@edytchokouani/the-starter-git-commands-for-beginner-4fb9ef8f21f5?source=rss-3058869e6702------2</link>
            <guid isPermaLink="false">https://medium.com/p/4fb9ef8f21f5</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[workflow]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[git]]></category>
            <dc:creator><![CDATA[Tchokouani Edy Michel]]></dc:creator>
            <pubDate>Tue, 14 Mar 2023 20:00:07 GMT</pubDate>
            <atom:updated>2023-03-14T20:00:07.416Z</atom:updated>
            <content:encoded><![CDATA[<p>I just want to share with you the 7 importants git for starter</p><p>For starters, git is a decentralized source code versioning tool and as a developer, it is super important to know how to version your source code and git is unique in that it promotes an agile workflow where developers are encouraged to share even the smallest changes more frequently. In turn, changes can be pushed to the deployment pipeline faster than using the common monolithic releases with centralized version control systems, resulting in a faster delivery cycle.<br>For those who are new to git, I will write articles on how to define a git workflow<br>Here we will talk about the 7 basic commands that every developer should master before starting</p><h3>1- Git Clone</h3><p>The git clone command copies an existing repository into a new local repository. The git clone command creates a new directory locally for the repository, copies all the contents of the specified repository, creates the <strong>remotely-tracked branches</strong>, and extracts an initial branch locally.</p><blockquote>git clone &lt; repository url&gt;</blockquote><h3>2- Git Pull</h3><p>The <strong>git pull </strong>command retrieves and download content from a remote repository and <strong>updates the local repository </strong>as soon as it been downloaded. In git-based collaboration workflows, it is common to merge remote upstream changes into you local repository</p><blockquote>git pull</blockquote><h3>3- Git Checkout</h3><p>The <strong>git checkout</strong> command navigates between two different branch in a git repository. Checkout is used to view and make change to different branches. You can check out a past commit in a repository to view how your project appeared in that state</p><blockquote>git checkout &lt;branch name&gt;</blockquote><blockquote>git checkout -b &lt;branch name&gt;</blockquote><h3>4-Git Add</h3><p>The <strong>git add</strong> command adds news or changed files in your working directoryto the git staging area. As you’re working, you change and save a file or multiples files. Then, before you commit, you must git add . This step allows to choose what you are going to commit.</p><blockquote>git add &lt;file path&gt;</blockquote><blockquote>git add .</blockquote><h3><strong>5- Git Commit</strong></h3><p>The <strong>git commit</strong> command is used to recordthe changes in the repository. Every commit contains the index data and commit message and every commit from a parent-child relationship. When we add a file in git, it will take place into staging area. A commit command is used to fetch updates from the staging area to the repository.</p><blockquote>git commit -m “commit message”</blockquote><h3>6- Git Push</h3><p>A <strong>git push</strong> command, when executed, pushed the changes that the user has made on local machine to remote repository. Once the users have clone the remote repository and have made the necessary changes in thier local device, they need to push to the remote repository so that the are shared and used by other users</p><blockquote>git push</blockquote><blockquote>git push — set-upstream &lt;remote branch&gt; &lt;branch name&gt;</blockquote><h3>7-Git branch</h3><p>Git branch provides you the ability to create branches and perform risk-free development in isolated programming space. The <strong>branch</strong> command helps you create, delete, and lists branches. It is the go-to command when it comes to managing any aspect of yours branches no matter if in your local repository or your remote repository.</p><blockquote>git branch &lt;new branch&gt;</blockquote><blockquote>git branch -d &lt;branch name&gt;</blockquote><p>Git has many other commands that allow you to better manage your repositories, but here are the basic commands to master.<br>In prelude to the next article on git workflows, please leave your experiences and your git workflows in comments so that we can discuss them in the next article. Thanks</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4fb9ef8f21f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Qualities of a good developer]]></title>
            <link>https://medium.com/@edytchokouani/the-qualities-of-a-good-developer-e2e9be06072e?source=rss-3058869e6702------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2e9be06072e</guid>
            <category><![CDATA[qualities-of-a-developer]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile-coaching]]></category>
            <category><![CDATA[agile-development]]></category>
            <dc:creator><![CDATA[Tchokouani Edy Michel]]></dc:creator>
            <pubDate>Mon, 30 Jan 2023 15:20:58 GMT</pubDate>
            <atom:updated>2023-01-30T15:20:58.368Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5QHk0SCNCJB8mIIW8V7N7g.png" /></figure><p>Beyond the technical qualities (reducing the technical debt by ensuring the efficiency of the code, improving the readability of the code, refactoring the code, using version control, writing tests, etc.) A good developer must also have non-technical qualities such as: team spirit, autonomy, curiosity, etc. I’ll focus on the ones I consider to be among the most important: communication and empathy.</p><h4>How important is good communication to make you a good developer?</h4><p>The failures of development teams are more often due to the problem of communication than to the problem of competence, as a good developer a good communication allows to :<br>- Clarify user expectations or participate directly in the expression of needs<br>- Ask the right questions to define the scope of the project<br>- To express the points of difficulties and blocking<br>- To point out anomalies and possible vulnerabilities<br>- To train users if necessary<br>- Ensure that there is no gap between the deliverables and the customer’s expectations (which is generally a source of delays, disappointments due to unmet expectations, errors and bugs).<br>- Thus the agile Scrum method comes to help the good developer to overcome this communication problem through the sprint planning, the Daily scrum and the sprint retro giving the developer the possibility to communicate better<br>A good developer must have excellent communication skills. It is therefore important to improve your oral and written communication skills.</p><h4>How to improve your communication skills as a good developer?</h4><h4>1- Learn to listen</h4><p>If you want to be a good excellent communicator, listening is the most important coding skill, good communication happens when all parties hear each other. You can improve your skills by learning not to interrupt others when they are talking. Before you start adding to the conversation, give the other person time to speak.</p><h4>2-Be open to collaboration</h4><p>It is essential to communicate your ideas and work with other developers, this is how collaboration begins.</p><h4>3- Participate in meet-ups and conferences</h4><p>Committing to speaking at a conference or meeting is one of the best ways for a good developer to showcase their communication skills.</p><h4>4- Start a blog</h4><p>Another great way to improve your communication skills is to start your own blog and make it available to the public.</p><p>A good developer must communicate clearly and concisely to be successful in their career.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2e9be06072e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>