You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our engineering patterns are example solutions for addressing problems, meeting standards and living our engineering principles. They should make it easier for engineers to do their jobs. We don't have a standard way of writing patterns as we like to be a bit more flexible with their structure. Please provide us with some information on what you are proposing below
What is the pattern you are suggesting?
A code complexity pattern that sets out why reducing complexity is important, as well as techniques that can be used to reduce it in the future.
What would be the benefit to the Home Office of following this pattern
This will enable code written in the home office to follow best practices as well as reducing tech debt and making code easier to maintain.
How do people implement this pattern
Using tools to help understand complexity of their code, and techniques that can be used to help solve this.
I have looked through our existing patterns and think this is not covered elsewhere
I have checked through the open issues on the repository and this pattern has not already been suggested
The text was updated successfully, but these errors were encountered:
Our engineering patterns are example solutions for addressing problems, meeting standards and living our engineering principles. They should make it easier for engineers to do their jobs. We don't have a standard way of writing patterns as we like to be a bit more flexible with their structure. Please provide us with some information on what you are proposing below
What is the pattern you are suggesting?
A code complexity pattern that sets out why reducing complexity is important, as well as techniques that can be used to reduce it in the future.
What would be the benefit to the Home Office of following this pattern
This will enable code written in the home office to follow best practices as well as reducing tech debt and making code easier to maintain.
How do people implement this pattern
Using tools to help understand complexity of their code, and techniques that can be used to help solve this.
The text was updated successfully, but these errors were encountered: