<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Project Structure on PlumePHP</title><link>https://plumephp.com/tags/project-structure/</link><description>Recent content in Project Structure on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Tue, 25 Jul 2023 13:15:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/project-structure/index.xml" rel="self" type="application/rss+xml"/><item><title>Go 项目结构：构建可维护的大型项目</title><link>https://plumephp.com/78-go-project-structure/</link><pubDate>Tue, 25 Jul 2023 13:15:00 +0800</pubDate><guid>https://plumephp.com/78-go-project-structure/</guid><description>&lt;h1 id="go-项目结构构建可维护的大型项目"&gt;Go 项目结构：构建可维护的大型项目&lt;/h1&gt;
&lt;p&gt;你是否遇到过这样的场景：打开一个 Go 项目，看到所有代码都堆在 &lt;code&gt;main.go&lt;/code&gt; 里，或者目录结构混乱得像一盘意大利面？随着项目规模增长，这种混乱的结构会让你每次修改代码都像是在拆炸弹——稍有不慎就会引发连锁反应。&lt;/p&gt;</description></item></channel></rss>