# package design Published articles for package design. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Ep. 2: Elevating Software Design in Go: Package Architecture in Modern Development DevFeed: [Ep. 2: Elevating Software Design in Go: Package Architecture in Modern Development]() Original publisher: [Read original article]() Published: 2024-05-21T00:00:00Z Content type: article Language: en Sources: [William Kennedy]() Topics: [Code Modularity](), [system-design-project](), [software-architecture](), [Maintainability](), [Software Engineering]() Tags: [architecture](), [code](), [code-modularity](), [components](), [design](), [designing](), [developers](), [development](), [firewalls](), [functionality](), [go](), [go-development](), [go-projects](), [maintainability](), [modularity](), [package](), [package-architecture](), [package-design](), [packages](), [pitfalls](), [software](), [software-design]() ### AI overview Bill explains that Go packages create boundaries between program components through encapsulation and modularity, supporting organization and reuse. He recommends packages with focused functionality and warns that generic "Utils" or "Common" packages can weaken code integrity, increase dependencies, and hurt maintainability. The excerpt also introduces a "flipping pyramid" as a caution about monolithic codebases and raises robust type systems as relevant to code integrity and efficiency, without detailing either topic. ### Source excerpt Introduction: In this insightful episode, Bill dives deep into the realm of package design, shedding light on its crucial role in software development. Here are three key takeaways for Go developers: Code Modularity: Learn how Go's packaging system creates essential firewalls between program components, enhancing maintainability. Focused Functionality: Discover the importance of designing packages that provide specific functionality, fostering code clarity. Avoiding Pitfalls: Bill warns against common package design mistakes like centralized "common" packages, promoting a layered approach to maintainable code. ## Package Oriented Design DevFeed: [Package Oriented Design]() Original publisher: [Read original article]() Published: 2017-02-24T00:00:00Z Content type: article Language: en Sources: [William Kennedy]() Topics: [software-architecture](), [clean-architecture]() Tags: [2017](), [architecture](), [ardan-labs](), [blog](), [cli](), [communication](), [company](), [dependencies](), [design](), [domain](), [go](), [go-programming](), [golang](), [guidelines](), [latest](), [less](), [library](), [package](), [package-design](), [packages](), [packaging](), [philosophy](), [programming](), [project](), [team]() ### AI overview Package Oriented Design uses project structure to clarify where Go packages belong, what guidelines they follow, and how teams discuss architecture; it does not prescribe one universal layout. The excerpt proposes one kit project as a company-wide standard library, with highly portable foundational packages and no vendor folder; third-party dependencies should build against their latest versions. Keeping kit packages in one repository is presented as a way to reduce management work, with vendoring tools allowing projects to select needed packages. Application projects group programs deployed together, keep their source and third-party dependencies in one repository, and should follow a "less is more" approach. The excerpt ends before describing their three root folders. ### Source excerpt Updated on February 28th, 2017 Prelude This post is part of a series of posts designed to make you think about your own design philosophy on different topics. If you haven't read these posts yet, please do so first: Develop Your Design Philosophy Design Philosophy On Packaging Introduction Package Oriented Design allows a developer to identify where a package belongs inside a Go project and the design guidelines the package must respect. It defines what a Go project is and how a Go project is structured. Finally, it improves communication between team members and promotes clean package design and project architecture that is discussable.