<?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 Fajar Hikmal on Medium]]></title>
        <description><![CDATA[Stories by Fajar Hikmal on Medium]]></description>
        <link>https://medium.com/@fajarhikmal214?source=rss-fa02688c0b7a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*9LOPin8ZUcAxkie-hg0cRg.jpeg</url>
            <title>Stories by Fajar Hikmal on Medium</title>
            <link>https://medium.com/@fajarhikmal214?source=rss-fa02688c0b7a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 19:31:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@fajarhikmal214/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[Accidental Stoic: When You Realize Your Entire Life Is Governed by 2,300-Year-Old Books]]></title>
            <link>https://medium.com/@fajarhikmal214/the-stoic-mindset-navigating-social-dynamics-without-losing-your-mind-9656f4ac08c2?source=rss-fa02688c0b7a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9656f4ac08c2</guid>
            <category><![CDATA[stoicism]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[workplace]]></category>
            <dc:creator><![CDATA[Fajar Hikmal]]></dc:creator>
            <pubDate>Tue, 07 Jul 2026 15:36:59 GMT</pubDate>
            <atom:updated>2026-07-08T16:15:27.942Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A sudden realization of how a stack of old books quietly rewrote my entire worldview.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zK04OFr2-b_yy4TwOuw3Kw.jpeg" /><figcaption>Current view of the book stack on my desk</figcaption></figure><h3>Introduction: The Sudden Realization</h3><p>It started as a completely ordinary day. I was staring at a stack of books that I had intentionally piled up on my bed — Marcus Aurelius, Epictetus, Seneca, Cicero, Said Nursi, and Aristotle. I had owned them for several years. For the longest time, I thought they were just ordinary books. Paper, ink, and dust-catchers.</p><p>Then, a sudden realization hit me like a physical blow. A wave of shock and raw emotion washed over me as the dots connected in my head. I blurted out to myself:</p><blockquote>“Damn it, I just realized all these books changed my perspective over the years.”</blockquote><p>I never consciously tried to be a wise person. I never sat down to study philosophy to sound smart or put on a persona. I was just living my life, calculating my moves, and trying to survive the daily grind. But without me even realizing it, this heavy stack of historical wisdom had quietly slipped into my subconscious. They had completely rewritten how my mind works.</p><h3>Section 1: The Modern Reality Check</h3><p>Looking back at the book that impacted me the most — <em>Meditations</em> by Marcus Aurelius — I realized I had fully internalized one of the most famous opening rules in philosophical history. Marcus woke up every morning and gave himself a harsh reality check:</p><blockquote><em>“The people I deal with today will be meddling, ungrateful, arrogant, dishonest, jealous, and surly.”</em></blockquote><p>I live this reality every day. In various layers of this world, disrespect is common. Daily social dynamics often test your patience, push your boundaries, and trigger your emotional buttons. My natural, spontaneous response to encountering this kind of toxicity or disrespect has always been absolute silence. It is my way of hitting the pause button rather than reacting impulsively.</p><p>For a long time, I felt a lingering sense of guilt about this detachment. When I stay silent and choose to ignore difficult behavior for a few days, a small voice in my head worries, <em>“Am I the bad guy here? Is it my fault for not rushing to fix this communication breakdown?”</em> In a culture that demands constant engagement and instant replies, choosing to step back can easily feel like a personal failure.</p><p>But framing this through the lens of ancient literature changed everything. Epictetus famously taught <strong>“The Stone Analogy.”</strong> He explained that if you stand in front of a giant boulder and scream insults at it, the stone remains cold, unmoved, and unharmed. By choosing silence in the face of life’s daily drama, I wasn’t just ignoring someone; I was being the stone. I was refusing to hand over my peace of mind to someone else’s bad behavior. I realized I don’t owe anyone a moral debt to fix their emotional immaturity. My silence is my shield.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tjY75fJWHiFaWh2p" /><figcaption>Photo by <a href="https://unsplash.com/@bondikitt987?utm_source=medium&amp;utm_medium=referral">Keith Bond</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Section 2: The Anatomy of “Groupthink”</h3><p>This silence and detachment become an incredible asset when you step out of your personal space and into broader social circles or group discussions.</p><p>Imagine a classic scenario we have all witnessed: a group of people gathers to make a decision or discuss an idea. Sitting in that circle, one or two people clearly spot a fatal flaw or a massive risk in the plan. Their objective logic tells them that the collective decision is heavily compromised.</p><p>Yet, what usually happens next? The room falls silent out of fear or a simple desire for comfort. People choose artificial harmony over conflict. They stay quiet, nod, and agree just to fit in. In psychology, this is called <strong>Groupthink</strong>. When everyone in a group is thinking exactly the same way, the reality is that nobody is actually thinking.</p><p>Because the books have trained you to be unmoved like Epictetus’s stone, you don’t waste your energy on petty arguments or defensive reactions. Instead, your deliberate silence gives you the objective clarity to observe exactly what others miss. You gain the courage to become a healthy anomaly — what modern critical thinking calls a <strong>Devil’s Advocate</strong>. Speaking up with a dissenting view in a social setting is not about being toxic or disagreeable. It is about having the personal courage to challenge assumptions to save the group from its own blind spots.</p><h3>Section 3: Separating Ideas from Identity through “Cognitive Empathy”</h3><p>Standing as the lone voice of dissent among a circle of nodding people drains your social battery rapidly. Many analytical minds experience deep emotional burnout because they absorb the collective tension into their own hearts.</p><p>This is where you apply <strong><em>Cognitive Empathy</em></strong>. Instead of absorbing emotional drama, you use your intellect to understand another person’s thought structure and motives, without sacrificing your own emotional stability.</p><p>In daily relationships, this translates into two strict rules:</p><ul><li><strong>Attack the Logic, Never the Persona:</strong> Direct your arguments purely at the facts and the objective scenario — never at the personal capability of the person speaking.</li><li><strong>Maintain Healthy Boundaries:</strong> You can remain supportive, listen with absolute respect, and speak with courtesy. But you must draw a sharp mental line so that other people’s emotional chaos does not ruin your personal peace.</li></ul><h3>Section 4: Preserving Your Social Battery via “Ataraxia”</h3><p>Ancient Greek philosophy emphasizes an ideal state of mind known as <strong><em>Ataraxia</em></strong> — an untroubled, tranquil mind that cannot be shaken by external storms. In a landscape often fueled by social theater and unnecessary drama, <em>Ataraxia</em> is my ultimate shield.</p><p>The master key to achieving it is mastering the <strong>Dichotomy of Control</strong>:</p><ul><li><strong>Things Within Your Control:</strong> The depth of your thoughts, your personal values, your tone of voice, your respectfulness, and your internal choice to remain silent or speak.</li><li><strong>Things Outside Your Control:</strong> Other people’s egos, social politics, sudden shifts in relationships, and whether people like your opinion or not.</li></ul><p>Pour 100% of your energy into the first bucket and completely detach from the second. Once you have delivered your honest, objective thoughts, your personal duty is fulfilled. Whether the group embraces it or frowns upon it is completely outside your control. It has absolutely no right to ruin your night.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0YP0DHxbwcApjj9x" /><figcaption>Photo by <a href="https://unsplash.com/@punkidu?utm_source=medium&amp;utm_medium=referral">Ella Ivanescu</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3><strong>Conclusion: The Value of the Honest Anomaly</strong></h3><p>Social pleasantries and everyday courtesy are simply the “social taxes” we pay to coexist in any community. We must always respect the people around us. However, respecting others does not mean blind compliance or losing ourselves.</p><p>Social dynamics will always be unpredictable, and interpersonal drama will always exist. But by bringing timeless principles from that stack of books on your bed into your daily life, you stop being a passive passenger just trying to survive from day to day.</p><p>You become an anchor — a grounded, highly valuable, and tranquil individual who serves as an honest anomaly in a world that often settles for mere compliance.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9656f4ac08c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Manifesto Pertumbuhan: Sebuah Pilihan Sadar untuk Melangkah]]></title>
            <link>https://medium.com/@fajarhikmal214/manifesto-pertumbuhan-sebuah-pilihan-sadar-untuk-melangkah-242deaeb1ea0?source=rss-fa02688c0b7a------2</link>
            <guid isPermaLink="false">https://medium.com/p/242deaeb1ea0</guid>
            <dc:creator><![CDATA[Fajar Hikmal]]></dc:creator>
            <pubDate>Mon, 16 Jun 2025 23:15:19 GMT</pubDate>
            <atom:updated>2025-06-16T23:15:19.114Z</atom:updated>
            <content:encoded><![CDATA[<p>Ada momen dalam karier setiap orang di mana jalan di depan tampak bercabang. Satu jalan setapak menawarkan kehangatan dan keamanan dari wilayah yang sudah dikenal. Jalan yang lain, yang lebih terjal dan berkabut, menjanjikan pemandangan baru dengan risiko tersesat. Selama berbulan-bulan, saya berdiri di persimpangan itu, bergulat dengan dua suara dalam diri saya yang sama-sama kuat dan sama-sama benar. Tulisan ini adalah upaya saya untuk mengurai perdebatan batin itu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QOJhxv08PSfxXZv8" /><figcaption>Photo by <a href="https://unsplash.com/@chris_robert?utm_source=medium&amp;utm_medium=referral">chris robert</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Bagian 1: Tesis — Paradoks Kenyamanan</h3><p>Fondasi argumen saya untuk melangkah berakar pada sebuah paradoks: bagaimana sesuatu yang pada dasarnya baik, seperti kenyamanan, bisa menjadi sumber stagnasi. Rutinitas yang tadinya adalah guru disiplin yang baik, perlahan terasa seperti selimut yang terlalu nyaman. Saya belajar untuk memandangnya sebagai apa yang belakangan saya kenal dengan istilah filosofis, <strong><em>preferred indifferent</em></strong> — sesuatu yang berharga untuk dimiliki, layaknya kesehatan atau stabilitas, namun ia bukanlah tujuan akhir dari sebuah perjalanan. Di titik itulah, panggilan untuk bertumbuh terasa lebih mendesak daripada kebutuhan untuk tetap hangat di bawah selimut itu.</p><p>Konsep <em>preferred indifferent</em> ini menjadi lensa yang sangat kuat untuk saya. Ia mengajarkan bahwa banyak hal dalam hidup — seperti stabilitas, kenyamanan, dan keamanan finansial — adalah hal-hal yang ‘lebih disukai’. Wajar jika kita menginginkannya, dan keliru jika kita menganggapnya buruk. Namun, mereka bukanlah tujuan akhir dari sebuah kehidupan yang bermakna.</p><p>Pandangan ini membantu saya membingkai ulang narasi umum di sekitar saya, yang seringkali memandang pekerjaan tetap di satu tempat hingga pensiun sebagai pencapaian puncak. Saya tidak mengatakan pandangan itu sepenuhnya salah. Tentu ada kebijaksanaan di dalamnya; sebuah hidup yang terlindung dari badai ketidakpastian sudah pasti membawa ketenangan.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9ojmwoI-FYZjSdPw" /><figcaption>Photo by <a href="https://unsplash.com/@foxxmd?utm_source=medium&amp;utm_medium=referral">Matt Foxx</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Namun, pertanyaan yang terus mengganggu saya bukanlah ‘bagaimana cara untuk aman?’, melainkan ‘berapa banyak kesempatan untuk bertumbuh yang tanpa sadar saya tukar dengan rasa aman itu?’ Tesis saya tetap tegas: kita mungkin bisa berkembang di satu tempat, tetapi potensi pertumbuhan yang tak terbatas seringkali berada di luar pagar nyaman yang kita bangun sendiri.</p><p>Saya mulai merasakan apa yang bisa disebut ‘biaya dari tidak bertindak’. Ketika pertanyaan-pertanyaan baru berhenti muncul dan tantangan terasa seperti pengulangan, sebuah alarm internal berbunyi. Di titik inilah keputusan untuk melangkah keluar bukanlah tanda ketidakpuasan, melainkan sebuah pilihan sadar untuk melakukan <em>voluntary discomfort</em>. Sama seperti seseorang pergi ke gym untuk mengangkat beban demi otot yang lebih kuat, saya memilih tantangan baru ini agar jiwa dan pikiran saya tidak atrofi. Ini bukan pelarian, ini adalah latihan.</p><p>Apakah di tempat baru nanti akan lebih baik, lebih nyaman, atau lebih mudah? Sejujurnya, saya tidak tahu. Bisa jadi ini adalah keputusan yang keliru. Tapi satu hal yang saya tahu pasti: saya siap menghadapi apa pun yang datang. Karena tujuannya bukanlah untuk menemukan ‘tempat yang lebih baik’, tetapi untuk menjadi ‘pribadi yang lebih kuat’. Saya punya pilihan yang sangat aman untuk tinggal, dan justru karena itulah, keputusan untuk pergi ini menjadi sebuah praktik sadar untuk menempa diri.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hSYZy928BeYX8Jrs" /><figcaption>Photo by <a href="https://unsplash.com/@busgram?utm_source=medium&amp;utm_medium=referral">Büşra Salkım</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Saya teringat pada para bijak di masa lalu yang sengaja tidur di lantai keras atau makan makanan sederhana. Bukan karena mereka tidak mampu membeli kasur empuk atau hidangan mewah, tetapi karena mereka mengerti sesuatu yang fundamental: kekuatan sejati tidak dibangun di atas kenyamanan, melainkan di atas tantangan yang kita pilih untuk dihadapi.</p><h3>Bagian 2: Antitesis — Bukankah Ini Sebuah Pelarian?</h3><p>Tetapi setelah semua argumen untuk melangkah tersusun rapi, saya merasakan ada yang mengamati dari sudut ruangan pikiranku. Itu adalah bagian diriku yang paling skeptis, yang melipat tangannya dan bertanya dengan tenang,</p><blockquote>‘Sudah selesaikah kau mencoba meyakinkan dirimu sendiri? Mari kita bicara tentang apa yang sebenarnya terjadi: apakah ini sebuah langkah maju, atau sebuah langkah menghindar?’</blockquote><p>Suara ini berargumen bahwa ujian karakter yang sesungguhnya tidak terletak pada kemampuan kita mencari lingkungan yang ideal, tetapi pada kemampuan kita untuk menempa ketenangan di tengah lingkungan yang tidak sempurna. Ia berbisik bahwa lingkungan kerja yang sulit bukanlah penjara, melainkan <em>gymnasium</em> —sebuah tempat latihan yang paling efisien untuk menempa otot kesabaran, pengendalian diri, dan bahkan kebijaksanaan.</p><p>Pertanyaan yang diajukan suara ini sangat menusuk: Di mana lagi kau bisa belajar tentang batas kesabaranmu jika tidak setiap hari diuji? Bagaimana kau bisa benar-benar memahami arti ketenangan jika kau selalu lari dari kekacauan? Dengan pergi, jangan-jangan kau bukan hanya meninggalkan pekerjaan, tetapi juga meninggalkan kesempatan paling otentik untuk menempa kebajikan dari bahan-bahan yang paling kasar dan nyata.</p><p>Argumen untuk bertahan ini terasa sangat personal, karena sejujurnya saya telah menjalankannya. Ini mengingatkan saya pada percakapan dengan seorang teman yang membuat saya bertanya, “Apakah semua alasan saya ini hanyalah pembenaran yang saya ciptakan untuk berlindung?”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*N9HXHmruvOVi1zg1" /><figcaption>Photo by <a href="https://unsplash.com/@markusspiske?utm_source=medium&amp;utm_medium=referral">Markus Spiske</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Kesadaran ini bukanlah hal baru. Setahun yang lalu, saya berdiri di persimpangan yang sama, dan nasihat seorang teman menahan saya: <strong>“Mungkin kita belum sesiap itu. Masih banyak yang bisa dipelajari di sini.”</strong></p><p>Dan nasihat itu benar. Saya memutuskan tinggal, didorong oleh rasa penasaran yang jujur: saya ingin tahu bagaimana akhir dari cerita yang dinamis ini. Dan saya bersyukur atas keputusan itu. Setiap benturan menjadi pelajaran, terasa seperti gerinda yang mempertajam pemahaman, bukan pukulan yang melemahkan.</p><p>Pengalaman itu mengajarkan saya bahwa lingkungan yang menantang memang adalah arena terbaik untuk bertumbuh. Pengalaman inilah yang membuat argumen untuk bertahan begitu kuat dan menusuk. Ia bukan lagi sebuah ide abstrak, tetapi sebuah kebenaran yang telah saya alami.</p><p>Justru pengalaman itulah yang melahirkan pergulatan terbesar saya sekarang. Jika bertahan dan belajar dari kesulitan adalah keputusan yang tepat setahun lalu, apa yang membuatnya menjadi pilihan yang kurang tepat hari ini?</p><h3>Bagian 3: Sintesis — Memilih Arena Pertarungan yang Tepat</h3><p>Setelah bergulat dengan kedua argumen ini, saya tidak menemukan jawaban yang mudah. Keduanya terasa benar dalam konteksnya masing-masing. Kunci untuk maju bukanlah dengan memilih satu kebenaran dan membuang yang lain, tetapi dengan mengajukan pertanyaan yang lebih dalam. Pertanyaan yang akhirnya menggeser fokus saya adalah: <strong>“Apakah saya lari <em>dari</em> sebuah tantangan, atau saya lari <em>menuju</em> sebuah tanggung jawab?”</strong></p><p>Bagi saya, tanggung jawab terbesar itu adalah untuk memberikan <strong>kontribusi yang paling berdampak</strong> dengan potensi yang saya miliki. Saya menyadari ada kerinduan yang mendalam akan sebuah peran di mana hubungan antara usaha yang saya kerahkan dan hasil yang tercipta terasa lebih langsung dan lebih nyata. Ini bukan berarti kesempatan itu tidak ada akhir-akhir ini, tetapi saya merasakan panggilan untuk mencari sebuah “pertarungan” di mana saya bisa memfokuskan seluruh energi saya pada target yang lebih spesifik dan terukur.</p><p>Inilah yang memantapkan segalanya. Keputusan ini tidak pernah tentang memilih antara ‘sulit’ dan ‘mudah’. Ini adalah tentang <strong>memilih arena pertarungan yang tepat.</strong> Bertahan di arena di mana semangat saya tidak lagi bisa berkobar seratus persen pada akhirnya terasa seperti tindakan yang kurang bertanggung jawab — baik untuk lingkungan yang mengandalkan saya, maupun untuk potensi diri saya.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lVdo-aE3MbHOpziM" /><figcaption>Photo by <a href="https://unsplash.com/@grstocks?utm_source=medium&amp;utm_medium=referral">GR Stocks</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Maka, saya tidak sedang lari dari tantangan; saya sedang berlari menuju tantangan yang lebih selaras dengan di mana saya bisa memberi nilai tambah terbesar saat ini.</p><p>Dan mungkin, pada akhirnya, pertanyaan ini bukan hanya untuk saya. Di arena mana <em>Anda</em> sedang bertarung? Dan apakah itu pertarungan yang tepat untuk Anda, saat ini?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=242deaeb1ea0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Engineering Metrics: Driving Continuous Improvement in Agile Team]]></title>
            <link>https://medium.com/@fajarhikmal214/engineering-metrics-driving-continuous-improvement-in-agile-team-13b9be1d9854?source=rss-fa02688c0b7a------2</link>
            <guid isPermaLink="false">https://medium.com/p/13b9be1d9854</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[engineering-metrics]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[continuous-improvement]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Fajar Hikmal]]></dc:creator>
            <pubDate>Wed, 19 Feb 2025 23:01:44 GMT</pubDate>
            <atom:updated>2025-02-20T08:16:40.192Z</atom:updated>
            <content:encoded><![CDATA[<p>I kept wondering why Agile teams always end up stuck, merely performing ceremonies that provide no value and failing to make any improvements to enhance the team’s quality over time.</p><p>In the past few weeks, I held a sharing session in my division to share my experience on utilizing metrics to support the improvement of team quality.</p><p>My experience in 2022, when I joined a team to develop a product, made me realize something. As we worked on many features to meet user needs, we rarely received feedback on what we developed. I kept wondering whether what we built had any impact on users — whether they struggled to use it or if they didn’t use it at all.</p><p>Besides that, stakeholders often conflicted with each other regarding their perspectives on how a feature should be implemented. Without supporting data, team decisions were often swayed by subjective opinions, which in reality, might only represent a small fraction of users rather than the entire user base.</p><p>Even though this is a business problem, I believe engineering faces the same challenge. Without data, making objective decisions becomes difficult.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Aa98zLBxYuzeopWEEOw8ZQ.png" /></figure><p>This time, I want to explain that metrics are essential for supporting decision-making and improving team quality using meaningful numbers.</p><p>For me, the common problem that very often on the team when they try to adopt agile is team only perform agile ceremonies (standups, retros, reviews, etc.) without the value itself and not find any improvements.</p><p>Also, Agile values are misunderstood or not fully integrated into daily work. Decisions rely on intuition instead of data, leading to inconsistent progress.</p><p>When we try to measure some metrics, it leads us to data-driven decision-making, helps us align our work with business goals, and brings Agile values for meaningful improvements.</p><p>There are three key points that we try to measure:</p><h3><strong>1. Delivery Metrics (How Fast &amp; Reliable We Deliver)</strong></h3><p>In this section, there are several metrics that can be used to measure how fast and how reliable we are in delivering services to users.</p><p>One of the metrics we measure is <strong>Cycle Time</strong>. I got a reference from the book <em>The Engineering Leader’s Guide to Cycle Time</em> by Bryan Helmkamp. There are actually four stages to implementing Cycle Time, but not all of them have been implemented yet. However, there is already a lot that can be improved from these metrics. In fact, the book mentions that <strong>Time to Open</strong> (the first stage we implemented) has the greatest impact on overall Cycle Time.</p><p>The measured metrics are derived from <strong>Pull Request (PR) activities</strong> within the team when delivering features. These include measuring:</p><ul><li>The <strong>number of PRs</strong> completed by each team member in each sprint.</li><li>The number of <strong>lines changed</strong> in each PR.</li><li>The <strong>trend of open PRs</strong> per day or even per hour, which slightly represents when we are most productive.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QexC7GYQCdM51UIhrv0k0w.png" /></figure><p>Additionally, another key metric for measuring how quickly we deliver value to users is <strong>Deploy Frequency</strong>. This metric indicates how efficient and responsive we are in our delivery process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jFHydQyE_Dd6YBuSQWcnbA.png" /><figcaption><strong>Deployment Frequency</strong> per Month for 2024</figcaption></figure><p>One of the main reasons why frequent deployments are crucial is that they help <strong>minimize potential issues</strong>. The less frequently we deploy, the harder it becomes to test changes and identify bugs. When deployments are infrequent, a large number of code changes accumulate, making it more challenging to isolate and fix issues. By deploying more frequently, we can catch problems earlier, streamline testing, and ensure a more stable and reliable system.</p><p>There are many more metrics that can be used to measure how fast and reliable we are in delivering value. The ones mentioned above are just a few aspects of <strong>Cycle Time</strong>, <a href="https://dora.dev/guides/dora-metrics-four-keys/"><strong>DORA Metrics</strong></a>, or other relevant references. These metrics provide valuable insights into our development process, helping us identify areas for improvement and enhance overall efficiency.</p><h3><strong>2. Quality Metrics (How Good Is Our Work?)</strong></h3><p>Next, we have <strong>quality metrics</strong>, which help measure how well we perform our work. Once again, there are many references available for this, but one of the key metrics we focus on is <strong>Defect Rate</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*61NtUGIqiRDXvtgNX8i7Aw.png" /><figcaption>Number of <strong>Defects</strong> and <strong>Incidents</strong> in a sprint</figcaption></figure><p>This metric originates from <strong>Quality Assurance (QA) </strong>team member and reflects how many defects occur in each sprint. We’ve observed that our defect rate tends to fluctuate significantly, which is why we regularly discuss it during <strong>Sprint Retrospectives</strong> to find ways to reduce it. A high defect rate means we often have to <strong>redo work multiple times</strong>, which leads to inefficiencies and delays — especially when we are not thorough in our initial development process.</p><p>To mitigate this, we have identified several <strong>action plans</strong>, including:</p><ul><li><strong>Conducting test case reviews</strong> between engineers and QA to ensure that engineers review all test cases before passing them to QA, minimizing defects early.</li><li><strong>Adopting a “QA as a mindset” approach</strong> since we have limited QA resources. This encourages engineers to take ownership of quality throughout the development process.</li><li><strong>Implementing test files (unit test, integration test, or even E2E test) on the engineering side</strong> to catch errors early and reduce the likelihood of defects reaching production.</li></ul><p>By incorporating these strategies, we aim to improve code quality, reduce rework, and ensure a smoother, more efficient development process.</p><h3><strong>3. Collaboration &amp; Agile Adoption Metrics</strong></h3><p>Last but not least is the <strong>collaboration process</strong> and the<strong> adoption of Agile </strong>metrics itself. One of the key aspects that can be measured is <strong>Team Happiness</strong>. I believe that a happy team is more likely to foster better collaboration, which is essential in Agile, as it emphasizes teamwork and communication.</p><p>To measure <strong>Team Happiness</strong>, we can:</p><ul><li>Conduct <strong>offline standup meetings</strong> to improve team interactions.</li><li><strong>Run surveys</strong> with targeted questions about how happy team members feel working in the team.</li><li>Analyze the results to evaluate whether team happiness contributes to better collaboration.</li></ul><p>Another metric that I personally find valuable is <strong>Sprint Completion</strong>, which is best visualized using a <strong>burndown chart</strong>. A burndown chart helps track work progress over time, enabling teams to:</p><ul><li>Monitor completed tasks.</li><li>Forecast sprint completion.</li><li>Identify bottlenecks early.</li><li>Ensure steady progress toward project goals.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JEbozBbt-DiMPa-S2mqHzw.png" /></figure><p>By reviewing the <strong>burndown chart</strong> daily, we implement one of Agile’s core pillars: <strong>Inspection</strong>. The goal is to evaluate whether the team is progressing as planned, identify potential blockers early, and make necessary adjustments to ensure a smooth and efficient sprint execution.</p><h3>Final Thoughts</h3><p>From all the metrics we measure, it doesn’t mean that they must always reach the planned targets and consistently increase. Of course, that is what we expect, and ideally, it should be that way to indicate that our team is continuously improving. However, there are often cases where some metrics experience normal or even significant declines.</p><p>The key point is that we must conduct evaluations through retrospectives to find out what went wrong, what happened, and other insights from the sprint we went through. This ensures that there is always room for improvement, and that is what makes the process more valuable than anything else.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13b9be1d9854" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Solving Some Challenges in HackerRank]]></title>
            <link>https://medium.com/@fajarhikmal214/solving-some-challenges-in-hackerrank-9d00efb9635c?source=rss-fa02688c0b7a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d00efb9635c</guid>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[pseudocode]]></category>
            <category><![CDATA[hackerrank]]></category>
            <category><![CDATA[algorithms]]></category>
            <dc:creator><![CDATA[Fajar Hikmal]]></dc:creator>
            <pubDate>Sun, 08 Jan 2023 15:36:27 GMT</pubDate>
            <atom:updated>2023-01-08T15:43:56.735Z</atom:updated>
            <content:encoded><![CDATA[<p>As a first step to starting a career as a software engineer, especially a Backend Engineer in 2023, it would be a good idea to refresh and hone your problem-solving skills to improve how you work to be more effective and efficient.</p><p>When we solve problems especially in programming, we often solve problems by coding directly. Which sometimes makes us a little difficult because we don’t do any preparation such as Problem Identification and Problem Analysis. One of common tools in pre-code planning is Pseudocode and flowcharts.</p><p>Pseudocode is a false code used to describe how a computer program or an algorithm works. It uses annotations and text written in English because it’s meant for humans to read instead of computers.</p><p>A <a href="https://www.zenflowchart.com/flowchart">flowchart</a> is a type of diagrammatic representation using shapes and flow lines to illustrate a computer program, an algorithm, or a process. The process symbol used in a flow chart includes ovals, rectangles, diamonds, flow lines, and more to indicate various types of steps.</p><p>Below are some challenges that I tried to complete with various variations of difficulty.</p><p><a href="https://www.hackerrank.com/challenges/find-digits/problem?isFullScreen=true"><strong>Find Digits</strong></a></p><pre>This program will calculate the number of digits of the input request by determining whether the number is a divisor or not.<br><br>SET total to zero<br><br>GET list of numbers by transform from total number<br>GET length of number lists<br><br>LOOP through each number in the list<br> IF total number able to devide by number THEN<br>  INCREMENT total<br>END LOOP<br><br>RETURN total</pre><p>This is an implementation of the challenge mentioned in the pseudocode above written in the TypeScript programming language.</p><pre>function findDigits(n: number): number {<br>    let total: number = 0;<br>    <br>    const numbers: number[] = Array.from(String(n), (n) =&gt; Number(n));<br>    const length: number = numbers.length;<br>    <br>    for (let i in numbers) {<br>        const res: any = n / numbers[i];<br>        <br>        if (res % 1 == 0) {<br>            total++;<br>        }<br>    }<br>    <br>    return total;<br>}</pre><p><a href="https://www.hackerrank.com/challenges/the-time-in-words/problem?isFullScreen=true">The Time in Words</a></p><pre>This program will convert time into words<br><br>SET minute list of minutes in words<br>SET hour list of hours in words<br>SET oCloak to &quot;o&#39; clock&quot;<br><br>Function minuteLabel<br>  minute: integer representing of a minute<br>  <br>  IF minute = one THEN<br>    RETURN minute<br><br>  ELSE<br>    RETURN minutes<br>Endfunction<br><br>Function isQuarter<br>  minute: integer representing of a <br>  <br>  IF minute = thirty THEN<br>    RETURN half<br> <br>  ELSE IF minute = fifteen THEN<br>    RETURN quarter<br>  <br>  ELSE<br>    SET minute from minute list by its index<br>    RETURN minute minuteLabel(minute)<br>Endfunction<br><br>Function timeInWords<br>  SET hour from hour list by its index<br>  <br>  IF minute = zero THEN<br>   SET past to null<br>  ELSE IF minute &lt;= thirty THEN<br>   SET past to true<br>  ELSE<br>   SET past to false<br>  <br>  IF past = null THEN<br>   RETURN hour oCloak<br>  <br>  IF past = true THEN<br>   RETURN isQuarter(minute) past hour<br>  <br>ELSE<br>   SUBTRACT hour index by one<br>   <br>   SET hour from hour list by its index<br>   SET minute to sixty minus minute<br>  <br>   RETURN isQuarter(minute) to minute<br>Endfunction</pre><p><a href="https://www.hackerrank.com/challenges/strange-advertising/problem?isFullScreen=true">Viral Advertising</a></p><pre>This program will accumulate the number of people who like ads on social media every day<br><br>SET people to five<br>SET cumulative to zero<br>SET eachShare to three<br><br>LOOP through each day of the several days<br> SET likes to half a turn down the number of people<br> ADD cumulative to likes<br><br> SET people to peopleLikes plus eachShare<br>END LOOP<br><br>RETURN cumulative</pre><p>Maybe completing challenges like these doesn’t add to our expertise significantly, but small things done consistently will produce something good.</p><p>References :</p><p><a href="https://www.zenflowchart.com/guides/pseudocode-flowchart">https://www.zenflowchart.com/guides/pseudocode-flowchart</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d00efb9635c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>