<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Tech-Stack on Birdor Blog</title>
		<link>https://blog.birdor.com/tags/tech-stack/</link>
		<description>Recent content in Tech-Stack on Birdor Blog</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Sat, 06 Jun 2026 10:20:00 +0800</lastBuildDate>
		
			<atom:link href="https://blog.birdor.com/tags/tech-stack/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>A Practical Tech Stack for Indie Game Developers</title>
				<link>https://blog.birdor.com/indie-game-tech-stack/</link>
				<pubDate>Sat, 06 Jun 2026 10:20:00 +0800</pubDate>
				<guid>https://blog.birdor.com/indie-game-tech-stack/</guid>
				<description>&lt;p&gt;An indie game tech stack should help the developer finish the game.&lt;/p&gt;&#xA;&lt;p&gt;That sounds obvious, but many developers choose tools for the wrong reasons:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;the engine looks powerful&lt;/li&gt;&#xA;&lt;li&gt;the language feels elegant&lt;/li&gt;&#xA;&lt;li&gt;the renderer is impressive&lt;/li&gt;&#xA;&lt;li&gt;the tool is popular in technical discussions&lt;/li&gt;&#xA;&lt;li&gt;the developer wants to learn something new&lt;/li&gt;&#xA;&lt;li&gt;the stack feels more serious than the project requires&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Learning is valuable. Technical taste matters. But a commercial or serious indie game needs a stack that supports production, not just exploration.&lt;/p&gt;</description>
			</item>
			<item>
				<title>A Practical Tech Stack for Indie Developers — Simple, Reliable, and Built to Ship</title>
				<link>https://blog.birdor.com/practical-tech-stack-for-indie-developers/</link>
				<pubDate>Sat, 06 Jun 2026 09:10:00 +0800</pubDate>
				<guid>https://blog.birdor.com/practical-tech-stack-for-indie-developers/</guid>
				<description>&lt;p&gt;Indie development is not only about writing code.&lt;/p&gt;&#xA;&lt;p&gt;It is about choosing a technical path that lets one person or a small team build, launch, maintain, and improve a product without being crushed by complexity.&lt;/p&gt;&#xA;&lt;p&gt;For indie developers, the best tech stack is rarely the most advanced one.&lt;/p&gt;&#xA;&lt;p&gt;It is the one that helps you ship.&lt;/p&gt;&#xA;&lt;p&gt;A good indie stack should be:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;simple enough to understand&lt;/li&gt;&#xA;&lt;li&gt;reliable enough for production&lt;/li&gt;&#xA;&lt;li&gt;cheap enough to run&lt;/li&gt;&#xA;&lt;li&gt;flexible enough to evolve&lt;/li&gt;&#xA;&lt;li&gt;boring enough to maintain&lt;/li&gt;&#xA;&lt;li&gt;fast enough for users&lt;/li&gt;&#xA;&lt;li&gt;friendly enough for long-term iteration&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;This article introduces a practical tech stack for indie developers building modern web tools, SaaS products, browser extensions, APIs, content sites, and small commercial products.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
