title: What Is Your Software Development Directory Structure?
body: <p>I have been experimenting with directory structures and am currently using the one below:</p>
  
  <pre>
   |
   |_projects__
   |           |
   |           |_blog.com_
   |           |          |_mockups
   |           |          |_user stories
   |           |          |_....
   |           |
   |           |_noteapp__
   |                      |_mockups
   |                      |_....
   |
   |_webs______
   |           |
   |           |_dev______
   |           |          |_blog.com_
   |           |                     |_app
   |           |                     |_config
   |           |                     |_....
   |           |
   |           |_prod_____
   |           |          |_blog.com_
   |           |                     |_app
   |           |                     |_....
   |           |_qe_....
   |           |_uat_....
   |
   |
   |_desktops__
               |
               |_dev______
               |          |_noteapp_
               |                    |_app
               |                    |_config
               |                    |_....
               |
               |_prod...
               |_qe....
               |_uat....
  
                                                   KEY
                                                   dev  - development
                                                   prod - production
                                                   qe   - quality engineering
                                                   uat  - user acceptance testing
  </pre>
  
  <p>Webs store web applications, desktops store desktop applications. The dev directory is version controlled, while the other directories (prod, qe, uat) store their respective current releases. The project directory stores non-code related project items.</p>
  
  <p>What is your software development directory structure and is there a reason you recommend that structure?</p>