<?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 Tigran Tchougourian on Medium]]></title>
        <description><![CDATA[Stories by Tigran Tchougourian on Medium]]></description>
        <link>https://medium.com/@ttchoug?source=rss-8198e51e4403------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*-yBrQIBZtSrO7TX5.jpg</url>
            <title>Stories by Tigran Tchougourian on Medium</title>
            <link>https://medium.com/@ttchoug?source=rss-8198e51e4403------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 02:08:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ttchoug/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[Code needs a friend]]></title>
            <link>https://medium.com/@ttchoug/code-needs-a-friend-5a2d1944cf4?source=rss-8198e51e4403------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a2d1944cf4</guid>
            <category><![CDATA[documentaion]]></category>
            <category><![CDATA[changelog]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[legacy]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Tigran Tchougourian]]></dc:creator>
            <pubDate>Thu, 09 Jan 2020 17:06:01 GMT</pubDate>
            <atom:updated>2020-01-09T17:06:01.299Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*G_WCPvWGfqYvSl_2" /><figcaption>Photo by <a href="https://unsplash.com/@proxyclick?utm_source=medium&amp;utm_medium=referral">Proxyclick Visitor Management System</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Once upon a time there was a little girl called Code. Code was living a nice life, she was changing the condition of people and helping them to be more efficient. Other people were helping Code to become a better girl. But some influenced her, derailing her from her initial purpose, and therefore affecting her behaviour. But Code held on and kept doing what she was best at doing. Today years passed and Code is an old lady. Only a few remember how cool she was.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/445/1*nLdlvbKuN_vWWq97yeQ-vA.png" /><figcaption>Code’s regular lifecycle without good documentation</figcaption></figure><p>Today you have the power to help Code. You must introduce here your friend <a href="https://keepachangelog.com/en/1.0.0/">Changelog</a>. He has a such good memory, he will tells you stories about her, with dates and who was present that day. He will make her happy. And finally Code will shine again and will never be alone any more.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a2d1944cf4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Professional dev vs not so Professional]]></title>
            <link>https://medium.com/@ttchoug/professional-dev-vs-not-so-professional-a01bd139d975?source=rss-8198e51e4403------2</link>
            <guid isPermaLink="false">https://medium.com/p/a01bd139d975</guid>
            <dc:creator><![CDATA[Tigran Tchougourian]]></dc:creator>
            <pubDate>Mon, 01 Apr 2019 08:53:06 GMT</pubDate>
            <atom:updated>2019-04-01T08:53:06.221Z</atom:updated>
            <content:encoded><![CDATA[<h4>Two stories happening at the same time in 2 parallel universe</h4><blockquote>Any resemblance to real people is purely coincidental.</blockquote><h3>Day 1</h3><p>— Hey what happened yesterday, the service was slow, at some point I got <strong>errors</strong> and was not able to work.</p><p>— Oh yeah I checked, it looks like the application took more time to load, so I <strong>increased the timeout</strong>. Nothing to worry about it is back to normal.</p><p>— Hey what happened yesterday, the service was slow and at some point I got errors and was not able to work.</p><p>— I don’t know <strong>yet</strong>, it looks like the application took more time than expected to start. I had to <strong>quick fix</strong>, and will <strong>take the time</strong> to understand <strong>what the real problem is</strong>.</p><h3>A few days later</h3><p>— Hey what happened yesterday, the service was slow <strong>again</strong>, I got errors <strong>again</strong> and was not able to work <strong>again</strong>. This is very frustrating.</p><p>— Yes, we have a <strong>procedure</strong> for that, <strong>when it occurs we increase the timeout</strong>. So don’t worry</p><p>Problem never occurred in this universe again… why ?</p><h4>Time travel machine engaged: Back to day 2</h4><p>Regular job day <strong>Universe One</strong></p><p>While in <strong>Universe Two</strong>, the developer is investigating the problem and found out that there was an OS upgrade that changed the default behaviour of a critical component which was used intensively by its application. After finding out what the real problem was, the developer contacted the team in charge. Here is was they put in place:</p><ul><li>Automatic validation of application after each update on a non production environment.</li><li>Fix the configuration of the component in order to rely on default values provided by the OS.</li><li>Improve the application to give better feedback in case of problems.</li></ul><h4>Universe 0</h4><p>What about you? How many times the same error occur in your day to day job ?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a01bd139d975" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to fail a technical presentation]]></title>
            <link>https://medium.com/@ttchoug/how-to-fail-a-technical-presentation-70c778c5faf4?source=rss-8198e51e4403------2</link>
            <guid isPermaLink="false">https://medium.com/p/70c778c5faf4</guid>
            <category><![CDATA[presentations]]></category>
            <category><![CDATA[swissquote]]></category>
            <category><![CDATA[gradle]]></category>
            <category><![CDATA[technical]]></category>
            <category><![CDATA[maven]]></category>
            <dc:creator><![CDATA[Tigran Tchougourian]]></dc:creator>
            <pubDate>Tue, 05 Dec 2017 18:00:49 GMT</pubDate>
            <atom:updated>2017-12-05T18:00:49.694Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gv60FTAwkv4_1NLXzgHeXw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/RARH8b7N-fw?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Estée Janssens</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>A few days ago I did a presentation about Gradle to some of my co-workers and it failed.</p><p>What I will talk about is known from everyone and will sound obvious but I would like to share this story with you regardless. In order to understand my mindset we need to start from the beginning.</p><p>A few weeks ago I was listening to French podcast about <a href="https://lescastcodeurs.com/2017/08/01/lcc-174-interview-sur-la-build-avec-cedric-champeau-et-arnaud-heritier-partie-1/">Maven vs Gradle</a>. I really enjoyed it and learned more about Gradle. Before, like for most Maven users, Gradle was a Maven-like tool… but the podcast opened my eyes to a new ecosystem and I had to know more about it. I started slowly by watching <a href="https://app.pluralsight.com/library/courses/gradle-fundamentals/table-of-contents">Gradle Fundamentals</a> on <a href="http://pluralsight.com/">pluralsight</a>, talks on <a href="http://youtube.com/">youtube</a>, and reading articles using my best friend google in order to feed my brain with knowledge. I reached a point where I needed to apply this knowledge to a concrete project.</p><blockquote>Let’s give it a shot, after all…</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*iSWjIZqPYP1a9EwNRLJPfg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/v7WyjiyXNr4?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Hal Gatewood</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Learn multiple new technologies at the same time</h3><p>In order to use Gradle, I had to either create a new project or reuse an existing one. I started a new project and I decided to try <a href="https://kotlinlang.org/">Kotlin</a> (another new thing) because I felt comfortable enough with the build tool. <strong>This was my first mistake</strong>. During the next hours I was spending more time looking for examples on Kotlin than I was on my slides or talking about Gradle. At the end of the day I had a new project, built with Gradle using Kotlin and one slide on my presentation. Not really useful…</p><h3><strong>Demonstrate a completely unknown scenario</strong></h3><p>So I tried to tackle the problem with an existing project. Since I was working during my personal time and I didn’t have access to the source code from home, I picked a personal project. The migration was uber easy. I chose a library, <a href="https://bitbucket.org/NargiT00/algorithms">algorithms</a>, and used a Gradle feature to automatically migrate my existing build. Everything worked as expected. But nothing to crazy too demonstrate. I had not made any progress on my presentation.</p><h3>Have neither an objective nor a scope</h3><p>I decided to add more Gradle commands to demonstrate the power of this tool, and start checking all available features it allows. I learned a lot and I was able to envision the benefits. I tried putting everything in the presentation without following a given plan or reaching a certain goal. I was just throwing a bunch of one liners to the face of my audience and trying to tell them what was happening on the screen.</p><h3>Take your time</h3><p>The d-day I did everything wrong! I was so enthusiastic about Gradle, I forgot to manage my time and skip the questions part. I was spending to much time on irrelevant subcommads, and even improvising… The presentation was a mess.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MuA2DTwS1nBTNC49CI-HZA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/OyCl7Y4y0Bk?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Element5 Digital</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Lesson learned</h3><p>I put myself in danger because I tried to learn multiple technologies at the same time, using examples from a world my audience doesn’t understand and without a clear objective. All this led to my speaking time being consumed without giving my audience the opportunity to ask questions.</p><p>I noticed that no matter how much energy you put in a presentation or how much potential the technology has, if you do not follow some basic rules, YOU WILL FAIL.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70c778c5faf4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microservices can help you manage legacy code]]></title>
            <link>https://medium.com/swissquote-engineering/https-medium-com-nargit-microservices-can-help-you-manage-legacy-code-20edf9bb80f8?source=rss-8198e51e4403------2</link>
            <guid isPermaLink="false">https://medium.com/p/20edf9bb80f8</guid>
            <category><![CDATA[how-it-was-built]]></category>
            <category><![CDATA[legacy-code]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[thinking]]></category>
            <dc:creator><![CDATA[Tigran Tchougourian]]></dc:creator>
            <pubDate>Fri, 07 Jul 2017 13:31:56 GMT</pubDate>
            <atom:updated>2017-07-07T13:31:56.748Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*PnOxo3cMLktoN0CtP-m-1w.jpeg" /></figure><p>Today <a href="https://jaxenter.com/microservices-trends-2017-survey-133265.html"><strong>half</strong> of companies choose microservices</a> to build their system. But we tend to forget about the maintenance of code living inside your old application as it’s often not worth migrating. Yes, it hurts the little architect inside you, but…</p><blockquote>“Refactor without real value for your clients is a waste of money.”</blockquote><p>Most of you have heard that and I personally hate it, because it is often correct. Nevertheless, how can we continue to build new features if they depend on old ones? How can we efficiently solve problems if we always refer to a piece of code that is hard to maintain? And finally, how can we be productive if adding a new field on a web page, takes weeks to be deployed in production? No matter what we try to do, a system will only evolve as fast as its weakest component.</p><p>In this blog post, I will try to describe the approach taken by Swissquote and the team I’m working with, in order to solve most of the problems that occur with legacy code. Everything below is the result of engineers improving their everyday lives.</p><h3>Identify legacy code</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*WRifgIMHQSPDz3Y3cyrqlQ.jpeg" /></figure><p>Before doing anything your team must agree which piece of code everyone considers legacy. Plenty of tools exist for managing the health of your code base and give you an objective view. At Swissquote we are building mostly Java Applications using integrated tools in the build pipeline for detecting problems.<a href="https://github.com/findbugsproject/findbugs">Findbugs</a>, <a href="https://github.com/checkstyle/checkstyle">checkstyle</a>, <a href="https://pmd.github.io/">pmd</a>, <a href="https://www.sonarqube.org/">sonarqube</a> (<a href="http://www.sonarlint.org/">sonarlint</a> for your favourite IDE) are tools made for this job. Monitoring each application’s rollback rate is also possible.</p><blockquote>number of rollback * 100 / number of upgrade</blockquote><p>You could also measure the time you spend on basic tasks and the number of tests you have to maintain each time you update the code. Finally, and this is the easiest, try explaining a system’s architecture and boundaries to another developer… If it’s not clear, you just found a good candidate for a microservices upgrade.</p><h3>Microservices to the rescue</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*1yldASyXbz0Pzj4nQrvlSQ.jpeg" /></figure><p>Considering the speed at which our field is moving, a good example of this being the amount of different frameworks <a href="https://nodejs.org/en/">node</a> ecosystem has produced, you should consider microservices a real alternative to your current software (e.g. <a href="https://martinfowler.com/articles/microservices.html">Microservices</a>). It brings strong encapsulation, which allows you to overhaul the code without affecting clients. It’s a matter of time before you switch, not just an option. You need to prepare your infrastructure proactively and be able to accept failure (e.g. <a href="http://highscalability.com/blog/2015/12/1/deep-lessons-from-google-and-ebay-on-building-ecosystems-of.html">Lessons learn from Google and eBay</a>, <a href="https://www.youtube.com/watch?v=kb-m2fasdDY">Uber</a>). Yes, the transition is not only a stack replacement, it also changes your developer’s mindsets and won’t be without pain. Writing monolithic software is way easier than building a service oriented architecture with clear boundaries.</p><blockquote>Don’t be afraid, it is worth it!</blockquote><p>The first iteration when transitioning to services oriented architecture is simply to wrap all of your libraries to microservices. As a consequence, you will be forced to add boundaries to the different domains of your business in order to have a better overview. The legacy code will be only hidden, but now nothing will prevent you from improving it as long as the API doesn’t change. Testing will be affected but guess what, there are tools to do it (e.g. <a href="https://www.getpostman.com/">postman</a>, curl, wget). At the end of the day, it will be far from being perfect, and sometimes you should make compromises, nevertheless the hardest will be achieved.</p><p>As a second step, you will find yourself more mature about your application and it will be time to improve its boundaries and focus on the design. Our team had to improve the current state and we designed an architecture that allows us to be more productive with our old libraries. The naive boundaries imposed with the first iteration encouraged us to improve it for the next version. It simplified a lot the maintenance and documentation, allowing us to deprecate parts of the old code.</p><p>One of the side effects of continuously improving our system through microservices came from other teams. Indeed, inside a company if you have a high coupling with libraries provided by other teams, you will have to deal with it. Rare are the cases where teams will allocate extra time for you. Nevertheless, as we provide better services, teams start migrating to it. By doing this we push the company forward as a whole, not just ourselves.</p><h3>Renew with legacy</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*qwuP_w0RB2_8yZnNRSfG9Q.jpeg" /><figcaption>Legacy Code</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*KtJWIbfCixkd83mmD-J2PQ.jpeg" /><figcaption>Legacy code improved continuously thanks to Microservices</figcaption></figure><p>Every piece of code has its strength and weaknesses. Microservices allow to encapsulate the legacy code and reveal its strengths. Boundaries therefore help improving this legacy code while avoiding negative effects. This great power comes with responsibility, and you will be challenged on new complex problems that will require your expertise.</p><p><em>Images: </em><a href="https://pixabay.com/"><em>https://pixabay.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20edf9bb80f8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swissquote-engineering/https-medium-com-nargit-microservices-can-help-you-manage-legacy-code-20edf9bb80f8">Microservices can help you manage legacy code</a> was originally published in <a href="https://medium.com/swissquote-engineering">Swissquote Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>