Knowing when to use project templates
Full-time employees often work on multiple applications that use the same technology stacks. In these cases, having some consistency between them can be beneficial. Project templates provide a way to save time up front, provide guidance to junior developers, and make maintenance easier down the road. For example, microservices has become a trend and, by definition, this may require setting up the same structure repeatedly. That kind of work not only wastes time but is not much fun either. Instead, you could make a Visual Studio template that sets everything up—such as logging, Entity Framework, Swagger, and so on—and is ready to go in a flash.
Personally, as a consultant/contractor, I code on several projects every year. I find myself doing similar things between different applications and clients. My next project often uses a similar "stack" or group of technologies used on a prior project. Typically, a few months have...
