<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>soft-skill on Blogfolio Najib</title>
    <link>https://najib.id/en/tags/soft-skill/</link>
    <description>Recent content in soft-skill on Blogfolio Najib</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright>
    <lastBuildDate>Thu, 16 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://najib.id/en/tags/soft-skill/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why One Bug Can Take Three Days</title>
      <link>https://najib.id/en/writing/2026/explaining-bugs-to-non-tech/</link>
      <pubDate>Thu, 16 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://najib.id/en/writing/2026/explaining-bugs-to-non-tech/</guid>
      <description>&amp;ldquo;This is just a small bug, right? Should take 5 minutes.&amp;rdquo;
Ever heard this one? Or maybe its variants: &amp;ldquo;Just change one line of code, right?&amp;rdquo;, &amp;ldquo;How can it take a whole day to fix this?&amp;rdquo;
If you&amp;rsquo;re a developer, you almost certainly have. And that line usually comes from a boss, project manager, or client — someone who doesn&amp;rsquo;t need to know what an N+1 query is, but needs to understand why something that looks simple takes a non-simple amount of time.</description>
    </item>
    
  </channel>
</rss>
