When it comes to source control, it is very interesting to see how development teams approach external software dependencies, or software dependencies in general. Many of us use a dedicated folder to store them in source control, often called
Lib, or similar. This is a well-known strategy for keeping solution-level software dependencies close to the source code.
Many developers have been applying this good practice for years, yet there is no single convention on how the folder should be named or structured or where it should be located. This kind of information is typically defined in the corporation's naming conventions and guidelines documentation. It is strange to see a multitude ...