<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Debugging on Blogfolio Najib</title>
		<link>https://najib.id/en/tags/debugging/</link>
		<description>Recent content in Debugging on Blogfolio Najib</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
			<copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright>
		
		
			<lastBuildDate>Thu, 10 Sep 2026 16:50:44 +0700</lastBuildDate>
		
			<atom:link href="https://najib.id/en/tags/debugging/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Hijrah Backend (2): Anatomy of a 15-Second Endpoint</title>
				<link>https://najib.id/en/writing/2026/hijrah-backend-02/</link>
				<pubDate>Thu, 10 Sep 2026 15:30:00 +0700</pubDate>
				<guid>https://najib.id/en/writing/2026/hijrah-backend-02/</guid>
				<description>&lt;p&gt;In &lt;a href=&#34;https://najib.id/en/writing/2026/hijrah-backend-01/&#34;&gt;the previous episode&lt;/a&gt; I mentioned an endpoint that took 15 seconds per call. This is the full story, because hunting its cause turned out to be one of the most educational debugging sessions I&amp;rsquo;ve ever had. Not because it was hard, but because I was wrong repeatedly, and confidently hehe~&lt;/p&gt;&#xA;&lt;h2 id=&#34;one-click-seventeen-seconds&#34;&gt;One Click, Seventeen Seconds &lt;a href=&#34;#one-click-seventeen-seconds&#34; class=&#34;tdln dimmer&#34;&gt;&lt;small&gt;#&lt;/small&gt;&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;The victim: a fuel-estimation-per-vehicle-group endpoint. One click on the dashboard, then you wait. About 17 seconds, every single time. For a dashboard people open daily, that felt like dial-up loading hahaha.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
