IP - Do you make your templates accessible to everyone in your organisation?
21/10/2016 11:26 AM by
A common mistake is to use code or emails that you have previously written, and stored somewhere on your computer, and change around key bits to make it relevant for the current situation.
The problem with this is that you make it impossible for anyone else in your organization to do the same task to the same quality level.
Make sure your company has a common code base and email template store and endeavour to improve it regularly. This shares knowledge across your organization and makes sure everyone is working to the level that your company standards require.
Create Nuget Packages for reusable code libraries
The best approach to reuse code across multiple projects is to create Nuget Packages. When you need to update that library, it is then trivial to apply that update to your client projects.
Good Example: when reusing code across multiple projects for a single client, hosting your own Nuget Server provides an excellent way to manage shared private dependencies
For details on creating your own internal Nuget repository, read this rule: https://rules.ssw.com.au/do-you-create-a-private-repository-for-reusable-internal-code
Good Example: If your library has potential outside of your current requirement, consider publishing to the world on Nuget. Often the work involved to make a library more generic and re-usable results in better-quality code.
You can find a selection of Nuget packages published by SSW here:
Do you feel this rule needs an update?