How is your local development environment folders’ structure organized?

Hi Community.

I would like to discuss possible solutions how to effectively organize local development environment structure or/and how you solve one or many challenges from the list below.

Here is set of requirements/constraints good to be satisfied:

• you may collaborate with more than one company as a contractor
• you may work on your personal projects or/and contribute to open source projects
• company, you are working with, may have complex internal structure with a lot of dev teams and departments. you may be involved in multiple projects (like devops for example)
• company may have shared components which should be used by other teams (especially components that requires compilation, like C++ libraries)
• new team member on-boarding: developer should be able to setup dev environment for any project(s) "using-single-click-approach"
• handle micro-services architecture, when every service can be stored using multi-repo approach. it good to have somewhere meta description about all services are included into solution.
• override subset of projects parameters. for example, you may want to store your Dev/QA/UAT environment's configurations in some shared place, but in the same time be able to changes some of them during local development/debug
• manage multiple version of external libraries/frameworks: java, nodejs, maven, boost etc. to be able switch between projects quickly.
• approach should be platform agnostic
• approach should be polyglot programming friendly

A simple example, which highlights some of the topics above.

Thanks in advance!