KISS Principle

[aaronrussellHO]

Our engineering principles are the high-level direction we want to encourage engineers to follow or consider when they are making decisions and implementing things. Look at the 'writing a principle' standard and provide some brief information below

What is the principle you are suggesting?
One thing that keeps coming up across guilds is KISS. So writing this into the principles make sense. Though we need to be aware of overlap with this following principles:
Write maintainable, reusable and evolutionary code

What would be the benefit to the Home Office of adopting this principle?
This principle should help with quality and speed of delivery by creating simple, reusable, self documenting code to help devs across the home office.

How might people follow it
Creating code that is simple to follow, abstracts out complexity and avoid adding technical debt.

Additional information
Add any other information you think would be useful here

Please confirm the below

• I have looked at the writing-a-principle standard and think this would meet the standard
• I have looked through our existing principles and think this is not covered elsewhere
• I have checked through the open issues on the repository and this principle has not already been suggested