<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Programming on Chanzmao ʕ•ᴥ•ʔ Bear Blog</title>
		<link>https://chanzmao.benigumo.com/blog/programming/</link>
		<description>Recent content in Programming on Chanzmao ʕ•ᴥ•ʔ Bear Blog</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
			<copyright>Copyright © 2026, chanzmao</copyright>
		
		
			<lastBuildDate>Sat, 06 Jun 2026 00:41:26 +0900</lastBuildDate>
		
			<atom:link href="https://chanzmao.benigumo.com/blog/programming/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Why Most Tech Blogs Die Fast</title>
				<link>https://chanzmao.benigumo.com/why-most-tech-blogs-die-fast/</link>
				<pubDate>Sat, 06 Jun 2026 00:41:26 +0900</pubDate>
				<guid>https://chanzmao.benigumo.com/why-most-tech-blogs-die-fast/</guid>
				<description>&lt;p&gt;Let’s be honest for a second: the shelf life of a technical blog post is brutally short.&lt;/p&gt;&#xA;&lt;p&gt;It’s an open secret in the dev community, but one we usually choose to ignore. Think about it. You spend an entire weekend fighting a bizarre configuration bug, finally figure it out, set up a flawless GitHub repo, and write up a beautiful step-by-step tutorial. Fast forward a year—sometimes just a few months—and that article is practically a ghost town, buried under a mountain of framework updates and new tools.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
