Conventions on Marko Apfelhttp://blog.marko-apfel.de/tags/conventions/Recent content in Conventions on Marko ApfelHugoen-USMon, 09 Sep 2024 19:31:11 +0200How to Organize Code Across Git Repositorieshttp://blog.marko-apfel.de/posts/repository-organization/Fri, 30 Aug 2024 09:40:05 +0200http://blog.marko-apfel.de/posts/repository-organization/A short set of rules for deciding what gets its own repository, how to name it, and how to keep experimental code from cluttering your core product.Production Code vs. Non-Production Code: Why the Distinction Mattershttp://blog.marko-apfel.de/posts/production-vs-non-production-code/Fri, 30 Aug 2024 09:40:05 +0200http://blog.marko-apfel.de/posts/production-vs-non-production-code/Where do integration tests belong relative to your source tree? The answer says more about your repository’s structure than it first appears.How We Organize Files: A DevTree Overviewhttp://blog.marko-apfel.de/posts/file-organization/Wed, 09 Feb 2022 20:01:33 +0100http://blog.marko-apfel.de/posts/file-organization/File organization sounds like a boring topic right up until a new repository doesn’t follow any convention. A short map of the ground covered by the DevTree series.The DevTree: A Practical Folder Layout for .NET Repositorieshttp://blog.marko-apfel.de/posts/dev-tree/Wed, 09 Feb 2022 20:01:33 +0100http://blog.marko-apfel.de/posts/dev-tree/A well-organized repository mirrors production while leaving room for the extras development needs. Here’s a folder layout that scales from a quick PoC to a full production codebase.