title: Project code separation and folder naming habits
body: <p>In our project there are C# classes which does something (engine code), and some data transfer (DTO) classes to parameterize the engine fuctions. One of the project member likes to separate the classes into folders:</p>
  
  <pre><code> DTO\class1.cs
   DTO\class2.cs
   engine1.cs
   engine2.cs
  </code></pre>
  
  <p>Other project member is bothered by this folder separation, he likes it in the same folder as these codes are part of the problem:</p>
  
  <pre><code> class1.cs
   class2.cs
   engine1.cs
   engine2.cs
  </code></pre>
  
  <p>First method separates the valuable classes from the 'worthless' ones, and speeds up the searching in the Solution Explorer - but the DTO name is not a nice one. I am interesting in how you guys separate the code into folders (and how to name them) in your (bigger) projects?</p>