<?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[FrichtiTech - Medium]]></title>
        <description><![CDATA[Stories from Frichti&#39;s Tech team. - Medium]]></description>
        <link>https://medium.com/frichtitech?source=rss----4318c23c8821---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>FrichtiTech - Medium</title>
            <link>https://medium.com/frichtitech?source=rss----4318c23c8821---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 04:41:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/frichtitech" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[ASTs: How Frichti use them for large & easy refactoring]]></title>
            <link>https://medium.com/frichtitech/asts-how-frichti-use-them-for-large-easy-refactoring-958f845ca120?source=rss----4318c23c8821---4</link>
            <guid isPermaLink="false">https://medium.com/p/958f845ca120</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[abstract-syntax-tree]]></category>
            <category><![CDATA[eslint-plugin]]></category>
            <category><![CDATA[babel]]></category>
            <category><![CDATA[eslint]]></category>
            <dc:creator><![CDATA[Axel Mohamed Sadat]]></dc:creator>
            <pubDate>Mon, 18 Oct 2021 08:02:20 GMT</pubDate>
            <atom:updated>2021-10-20T08:10:45.964Z</atom:updated>
            <content:encoded><![CDATA[<p>In this post, we are introducing how to use <em>Abstract syntax trees (AST)</em> to create some eslint custom rules in order to make refactoring much easier and code more suited to your guidelines.</p><h3>Refactoring</h3><p>Refactoring is one of the most important parts of the frontend engineer’s job. It is very broad and can go from simple tasks like changing the variable’s name, a function or a component to a complete architecture restructuration, without changing functionalities or introducing regressions.</p><p>And as you know… sometimes… refactoring large projects with an historical background and some technical debts could be really painful especially when tasks are just boring like renaming hundreds of variables and sources of imports across hundreds of files.</p><h3>The problem</h3><p>Last year, our awesome design’s team released “La Recette”, the first version of the <a href="http://frichti.co/">Frichti’s</a> <a href="https://atomicdesign.bradfrost.com/chapter-1/">design system</a>. It was a real enhancement for the frontend devs team, as it helps us to improve our development flow and the communication between the product team and developers .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pLy87QS7vtucpyEQHNpL8w.png" /></figure><p>However, the implementation of a new design system in the code base wasn’t as easy as we thought because of many reasons:</p><ul><li>Colors naming conventions have changed to be more consistent and some colors have totally evolved as you can see the matching table below:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YMZ3zdn97PiBXJ3rmzaPqw.png" /></figure><ul><li>We also seized the day of those changes to create a separate npm package in order to reuse our design system through our different frontend apps. That way, the source of import of colors has changed drastically, and we had to convert the whole code base this way:</li></ul><pre>/** <br>** Old legacy code<br>**/<br>import { DEPRECATED_COLORS, PRODUCT_CARD_WIDTH } from &#39;@contants/index&#39;</pre><pre>const StyledProductCard = styled.div`<br>  background-color: ${DEPRECATED_COLORS.black};<br>  width: ${PRODUCT_CARD_WIDTH};<br>`</pre><pre>/**<br>** New code<br>**/<br>import COLORS from &#39;@frichti/la-recette/colors&#39;<br>import { PRODUCT_CARD_WIDTH } from &#39;@contants/index&#39;</pre><pre>const StyledProductCard = styled.div`<br>  background-color: ${COLORS.dark[900]};<br>  width: ${PRODUCT_CARD_WIDTH};<br>`</pre><p>The problem with those challenges was that it was too risky to do a “<em>search and replac</em>e” in the whole code base as we could face some cases where the colors were not consistent. Also, developers have to know the matching array and we should inform them for each deprecated color the equivalent one in the new design system. So, we asked ourselves : <em>how can we handle such a tricky subject ?</em></p><h3>ASTs to rescue…</h3><blockquote><em>“An Abstract Syntax Tree, or AST, is a tree representation of the source code of a computer program that conveys the structure of the source code.” </em><a href="https://deepsource.io/glossary/ast/">https://deepsource.io/glossary/ast/</a></blockquote><p>To illustrate the AST representation of add function in JavaScript, for example, would look like the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8ePHJOItb7U-t4wCIMY7AQ.png" /><figcaption><a href="https://resources.jointjs.com/demos/javascript-ast"><em>https://resources.jointjs.com/demos/javascript-ast</em></a></figcaption></figure><p>Here we have our Program which is the first node of our tree and then we have a node that defines each action or statement occurring in our code below:</p><pre>function add(a, b) {<br>  return a + b;<br>}</pre><p>Of course, this tree could also be represented as a <a href="https://developer.mozilla.org/en-US/docs/Learn/JavaScript/Objects/JSON">JSON (JavaScript Object Notation)</a>. Concerning our initial problem, for instance:</p><pre>import { DEPRECATED_COLORS, PRODUCT_CARD_WIDTH } from &#39;@contants/index&#39;</pre><p>will be represented as the JSON below using the <a href="https://github.com/babel/babel/tree/main/eslint/babel-eslint-parser"><strong>babel-eslint</strong></a> parser:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/965/1*IeBA2zcO-uxLO8-9aEr-RQ.png" /><figcaption><a href="https://astexplorer.net/#/gist/1ee8aaabdb761bc290664c2ce224e312/fd5f20a95292840c999547deaf1c5b33020d6bdd">https://astexplorer.net/#/gist/1ee8aaabdb761bc290664c2ce224e312/fd5f20a95292840c999547deaf1c5b33020d6bdd</a></figcaption></figure><h3>Our solution</h3><p>The solution that we found out for this problem (and many others that I’ll list at the end of this post) was to create a custom eslint rule using ASTs. The idea was to warn the developer who works on a file that uses a deprecated color that he must replace it by the new color and suggest him (or better, auto fix the issue) the equivalent color.</p><p>Now, let’s see how we can create our first custom rule!</p><h4>First step: create the plugin</h4><p>As we knew that we would create other rules in the future, we decided to create a global eslint plugin to contain all our frontend rules. I’ll not break down here how to create an npm package, there are tons of articles about that, but what you should know is that an eslint plugin should respect a naming convention. The package name should be prefixed by eslint-plugin-*.</p><p>In our case we named our package as:</p><pre>@frichti/eslint-plugin-frontend-rules</pre><h4>Second step: create our rule</h4><p>Here we will firstly create a rule that will disallow usage of a specific named variable (DEPRECATED_COLORS in our example) and suggest a matching variable (COLORS in this case).</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b3dfcfd28bf536150d78b00b5e583dc0/href">https://medium.com/media/b3dfcfd28bf536150d78b00b5e583dc0/href</a></iframe><p>And here we are!! 🎉🎉</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZxUriNOzw0I4GtB5Hrnrfg.png" /><figcaption><a href="https://astexplorer.net/#/gist/1ee8aaabdb761bc290664c2ce224e312/87b52388d975ed6e9f15b1dcbc3fa65d784a3aef">https://astexplorer.net/#/gist/1ee8aaabdb761bc290664c2ce224e312/87b52388d975ed6e9f15b1dcbc3fa65d784a3aef</a></figcaption></figure><p>By removing the comments on the fixer, the code will automatically be resolved into this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZUV7D_T0i-4VKw0MmD8kJg.png" /><figcaption><a href="https://astexplorer.net/#/gist/1ee8aaabdb761bc290664c2ce224e312/e27af3bbee4a3c05fd471beffdfc7a9c4d2520b4">https://astexplorer.net/#/gist/1ee8aaabdb761bc290664c2ce224e312/e27af3bbee4a3c05fd471beffdfc7a9c4d2520b4</a></figcaption></figure><h3>Conclusion</h3><p>Our rule is more configurable and offers some other options like matching object properties with new ones, as we could replace the DEPRECATED_COLORS.black by the new COLORS.dark[900] for instance.</p><p>Finally, our package is available on npm and the whole code can be found <a href="https://github.com/frichti/eslint-plugin-no-deprecated-variable/">on Github</a>. Feel free to install the npm package or contribute with new pull request.</p><p>Of course, this example is kept simple in order to understand some of ASTs pros and what it offers. A lot of other things can be done using them like babel plugins, codemods….</p><p>At <a href="http://frichti.ci/">Frichti</a>, we internally created a lot of other eslint rules to remain consistent in our code base, reinforce some guidelines rules or make some long refactoring tasks easier to develop. For example, we have:</p><ul><li>A rule that disallows calling analytics methods more than once in another method.</li><li>A rule that disallows direct xState context assignment without passing by assign (the @xstate/immer one or native one) method.</li><li>And a lot of other specific cases rules</li></ul><p>Thanks for reading, feel free to comment or reach out for questions !</p><p>Cheers 🍻</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=958f845ca120" width="1" height="1" alt=""><hr><p><a href="https://medium.com/frichtitech/asts-how-frichti-use-them-for-large-easy-refactoring-958f845ca120">ASTs: How Frichti use them for large &amp; easy refactoring</a> was originally published in <a href="https://medium.com/frichtitech">FrichtiTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Improve your Kotlin code with Detekt]]></title>
            <link>https://medium.com/frichtitech/improve-your-kotlin-code-with-detekt-65795656b1ed?source=rss----4318c23c8821---4</link>
            <guid isPermaLink="false">https://medium.com/p/65795656b1ed</guid>
            <category><![CDATA[detekt]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[kotlin]]></category>
            <category><![CDATA[linter]]></category>
            <category><![CDATA[gradle]]></category>
            <dc:creator><![CDATA[Jordan Gout]]></dc:creator>
            <pubDate>Mon, 11 Oct 2021 12:52:39 GMT</pubDate>
            <atom:updated>2021-10-11T13:27:30.564Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*HEvspHNNfS3Mw-JYg64vqw.png" /></figure><p>As a developer you have your own coding style and keeping a codebase both consistent and maintainable in a project with multiple developers can be challenging.</p><p>During a code review, you want to focus on business logic, algorithmic, coding patterns and not on code styling, on variable naming, this is why you should use linters.</p><p>This article will focus on <a href="https://github.com/detekt/detekt">Detekt</a>, a static code analysis tool for Kotlin.</p><p>Detekt comes with multiple rules sets like <a href="https://detekt.github.io/detekt/style.html"><em>style</em></a>, <a href="https://detekt.github.io/detekt/complexity.html"><em>complexity</em></a>, <a href="https://detekt.github.io/detekt/naming.html"><em>naming</em></a>, and <a href="https://detekt.github.io/detekt"><em>others</em></a> and allowed to easily create you own rules.</p><p><strong>Add Detekt to your project</strong></p><blockquote><em>Note : On this article, code sample will used Gradle Kotlin DSL on a multi modules android project</em></blockquote><p>You need to add Detekt dependency to you buildSrc gradle file :</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/dda099714d0d5664c30b84909c5d1700/href">https://medium.com/media/dda099714d0d5664c30b84909c5d1700/href</a></iframe><p>You can use Detekt’s default task like <strong>./gradlew detekt</strong> but on this exemple I want to run Detekt only once on multiple modules. I need to create a plugin to define custom tasks and settings:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4969b2d91f83ad9c6b751165c72e0797/href">https://medium.com/media/4969b2d91f83ad9c6b751165c72e0797/href</a></iframe><p>In the code snippet above, we are setting the source directory of the project (projectDir), then we are defining two glob filters to run Detekt on all .kt and .kts files and finally we are ignoring the resources and the build folders</p><p>Finally, you need to enable the Detekt plugin on the gradle’s file at the root of your project:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K1mzngC-Iy9GnImhGg0e4w.png" /><figcaption>Apply custom your Detekt plugin to project</figcaption></figure><p><strong>Configure Detekt’s rules</strong></p><p>Now you need to select rules you want to apply to your project. You can either use <strong>buildUponDefaultConfig</strong> property or create your own config file.</p><p>Check <a href="https://detekt.github.io/detekt/configurations.html">Detekt docs</a> to create your own config file.</p><p><strong>Let’s run Detekt</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IS-1Zp5ONbl9wk3UGeqwIw.png" /></figure><p>Now Detekt is ready, but you may have some issues as above. In that case you can choose to fix them all but what if you can’t right now or what if your project is already in production and you have a couple hundred issues?</p><p>You can use <strong>@Supress</strong> annotation to ignore a single issue. You should use this option in the worst case only. To ignore existing issues you should use baseline.</p><p><strong>Create baseline file to ignore legacy issues</strong></p><p>We need to modify our Detekt plugin:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a47d113cbc047c3f8a7526c7270e73f4/href">https://medium.com/media/a47d113cbc047c3f8a7526c7270e73f4/href</a></iframe><p>Now we need to run <strong>./gradlew detektAllBaseline</strong> to ask Detekt to create our baseline file.</p><p>Let’s retry to run ./<strong>gradlew detektAll</strong> task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wsm-fWhZbH8fnUijGSpNYA.png" /></figure><p>All existing issues are now ignored so you can focus on new development and takes time to remove thoses previous issues.</p><p><strong>Going further</strong></p><ul><li>Install <a href="https://github.com/detekt/detekt-intellij-plugin">Detekt’s IntellJ plugin</a> to be warned during development phase</li><li>Run Detekt on your CI</li><li>Create your <a href="https://detekt.github.io/detekt/extensions.html#custom-rulesets">own rules</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65795656b1ed" width="1" height="1" alt=""><hr><p><a href="https://medium.com/frichtitech/improve-your-kotlin-code-with-detekt-65795656b1ed">Improve your Kotlin code with Detekt</a> was originally published in <a href="https://medium.com/frichtitech">FrichtiTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Better dependencies management with Kotlin DSL]]></title>
            <link>https://medium.com/frichtitech/better-dependencies-management-with-kotlin-dsl-553ce80c144e?source=rss----4318c23c8821---4</link>
            <guid isPermaLink="false">https://medium.com/p/553ce80c144e</guid>
            <category><![CDATA[gradle]]></category>
            <category><![CDATA[dsl]]></category>
            <category><![CDATA[kotlin]]></category>
            <category><![CDATA[gradle-kotlin-dsl]]></category>
            <dc:creator><![CDATA[Umut TEKE]]></dc:creator>
            <pubDate>Tue, 23 Mar 2021 10:18:27 GMT</pubDate>
            <atom:updated>2021-03-23T10:18:27.240Z</atom:updated>
            <content:encoded><![CDATA[<h3>Better dependencies management with Kotlin DSL — Scale your configuration</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*LK-QTWoFYe_JnG1FV2givg.png" /></figure><p>Let’s see in this article, how to migrate to <a href="https://docs.gradle.org/current/userguide/kotlin_dsl.html">Gradle Kotlin DSL</a> to properly centralize your <a href="https://gradle.org/">Gradle</a> dependencies.<br>DSL means <a href="https://www.jetbrains.com/mps/concepts/domain-specific-languages/">Domain-Specific Language</a> targeting to a particular kind of problem, rather than a general purpose language like Java aimed at any kind of software problem.<br>Thereby Kotlin DSL is a language dedicated to Gradle to build configuration in Kotlin instead of Groovy.</p><h4>Why Gradle Kotlin DSL will benefit you ?</h4><p>When you start developing in Kotlin, you could write your build configuration scripts in Kotlin. Groovy is not easy to manage.<br>In addition to the language, one of the main interests of this new syntax is the auto-completion offered by statically typed Kotlin. Unlike Groovy, which is dynamic, Android Studio struggles to set up the methods and parameters for you and reports input errors.<br>In order to take advantage of the new improvements made since version 3 of the Android plugin for Gradle, Google advises us to divide our projects into modules when our functional scope is sufficiently provided. This means that you have to manage the Gradle configurations in each module and keep control of the dependencies versions.</p><h4>How do we usually start managing our dependencies ?</h4><p>You probably started by adding dependencies manually which requires a lot of manual changes to updates libraries version.<br>Simple example of two modules <strong>feature_a</strong> and <strong>feature_b</strong> having some common dependencies.</p><pre><strong>feature_a/build.gradle</strong></pre><pre>dependencies {<br>   implementation &quot;androidx.appcompat:appcompat:1.2.0&quot;<br>   implementation &quot;androidx.constraintlayout:constraintlayout:<a href="https://mvnrepository.com/artifact/androidx.constraintlayout/constraintlayout/2.0.1">2.0.1</a>&quot;<br>   implementation &quot;androidx.recyclerview:recyclerview:1.1.0&quot;<br>   implementation &quot;com.airbnb.android:lottie:<a href="https://mvnrepository.com/artifact/com.airbnb.android/lottie/3.4.4">3.4.4</a>&quot;<br>}</pre><pre><strong><br>feature_b/build.gradle</strong></pre><pre>dependencies {   <br>   implementation &quot;androidx.appcompat:appcompat:1.2.0&quot;<br>   implementation &quot;androidx.fragment:fragment-ktx:1.1.0&quot;<br>   implementation &quot;androidx.transition:transition:<a href="https://mvnrepository.com/artifact/androidx.transition/transition/1.3.1">1.3.1</a>&quot;<br>   implementation &quot;com.airbnb.android:lottie:<a href="https://mvnrepository.com/artifact/com.airbnb.android/lottie/3.4.4">3.4.4</a>&quot;<br>}</pre><h4>How to ensure that common dependencies have the same version ?</h4><p>Google recommends to set <a href="https://developer.android.com/studio/build/gradle-tips.html#configure-project-wide-properties">extra properties</a> in root <strong>build.gradle</strong> file for version centralization.<br>But we go further and go through the Kotlin configuration for Gradle which is more readable and friendly.</p><p>First we update root Gradle build configuration script to get kotlin plugin.</p><pre><strong>build.gradle.kts</strong></pre><pre>buildscript <strong>{<br>    </strong><em>repositories </em><strong>{<br>        </strong>google()<br>        jcenter()<br>    <strong>}<br>    </strong>dependencies <strong>{<br>        </strong><em>classpath</em>(&quot;com.android.tools.build:gradle:4.0.1&quot;)<br>        <strong><em>classpath</em>(&quot;org.jetbrains.kotlin:kotlin-gradle-plugin:1.4.21&quot;)</strong><br>    <strong>}<br>}<br><br></strong>allprojects <strong>{<br>    </strong><em>repositories </em><strong>{<br>        </strong>google()<br>        jcenter()<br>    <strong>}<br>}<br><br></strong><em>tasks</em>.<em>register</em>(&quot;clean&quot;, Delete::class)<strong>{<br>    </strong>delete(<em>rootProject</em>.<em>buildDir</em>)<br><strong>}</strong></pre><p>Next, we create a new <strong>buildSrc</strong> module. This module is a Gradle feature allowing you to define tasks and tool kits to write build scripts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*FJtufiBYZ2lNawVfQRilPQ.png" /></figure><p>We start to add a build configuration script file like any module.<br>However, this script is in Kotlin (with <strong>.kts</strong> extension for Kotlin Script) and we apply the Kotlin DSL plugin to it as shown below.</p><pre><strong>buildSrc/build.gradle.kts</strong></pre><pre>plugins {<br><strong>    `kotlin-dsl`<br></strong>}<br><br>repositories {<br>    jcenter()<br>}</pre><p>Next step, we create our Kotlin properties in a file that we could name <strong>Dependencies.kt</strong> to declare our dependencies and our versions.</p><pre><strong>buildSrc/src/main/kotlin/Dependencies.kt</strong></pre><pre>object Versions {<br>   const val appCompat = &quot;1.2.0&quot;<br>   const val constraintLayout = &quot;<a href="https://mvnrepository.com/artifact/androidx.constraintlayout/constraintlayout/2.0.1">2.0.1</a>&quot;<br>   const val recyclerView = &quot;1.1.0&quot;<br>   const val transition = &quot;<a href="https://mvnrepository.com/artifact/androidx.transition/transition/1.3.1">1.3.1</a>&quot;<br>   const val lottie = &quot;<a href="https://mvnrepository.com/artifact/com.airbnb.android/lottie/3.4.4">3.4.4</a>&quot;<br>}<br><br>object Libraries {   <br>   val androidx = AndroidX<br>   const val lottie = &quot;com.airbnb.android:lottie:${Versions.lottie}&quot;<br>}<br><br>object AndroidX {<br>   const val appCompat = &quot;androidx.appcompat:appcompat:${Versions.appCompat}&quot;<br>   const val constraintLayout = &quot;androidx.constraintlayout:constraintlayout:${Versions.constraintLayout}&quot;<br>   const val recyclerView = &quot;androidx.recyclerview:recyclerview:${Versions.recyclerView}&quot;<br>   const val transition = &quot;androidx.transition:transition:${Versions.transition}&quot;<br>}</pre><p>The dependencies are more readable and enable centralization for better control.<br>Finally, start a Gradle synchronization. We can now access and apply our dependencies to the configuration scripts to the previous modules.</p><pre><strong>feature_a/build.gradle.kts</strong></pre><pre>dependencies {   <br>   implementation(Libraries.androidX.appCompat)<br>   implementation(Libraries.androidX.constraintLayout)<br>   implementation(Libraries.androidX.recyclerView)<br>   implementation(Libraries.lottie)<br>}</pre><pre><strong>feature_b/build.gradle.kts</strong></pre><pre>dependencies {<br>   implementation(Libraries.androidX.appCompat)<br>   implementation(Libraries.androidX.fragment)<br>   implementation(Libraries.androidX.transition)<br>   implementation(Libraries.lottie)<br>}</pre><p>See below an example of autocompletion displayed from Kotlin DSL.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iXJbJLGJtAIOqQ6qHUNtrw.png" /></figure><p>Note that the transformation of your configuration scripts is not required. You can continue using Groovy combined with Kotlin DSL.</p><p>In conclusion, the DSL allows you to master your dependencies and have centralized management when your project takes on a larger scale.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=553ce80c144e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/frichtitech/better-dependencies-management-with-kotlin-dsl-553ce80c144e">Better dependencies management with Kotlin DSL</a> was originally published in <a href="https://medium.com/frichtitech">FrichtiTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>