From eb7524ae56bcc10330cb981221bba8d10daf90d3 Mon Sep 17 00:00:00 2001
From: Michele Cereda <cereda.michele@gmail.com>
Date: Sun, 10 Dec 2023 00:30:10 +0100
Subject: [PATCH] chore: added a best practice about changes

---
 knowledge base/operations best practices.placeholder | 1 +
 1 file changed, 1 insertion(+)

diff --git a/knowledge base/operations best practices.placeholder b/knowledge base/operations best practices.placeholder
index 2b743ed..c6faa67 100644
--- a/knowledge base/operations best practices.placeholder	
+++ b/knowledge base/operations best practices.placeholder	
@@ -12,6 +12,7 @@
   Do **not** adapt your work to specific tools.
 - Backup early, backup often.
 - Keep changes shorts and sweet.
+- Make changes easy, avoid making easy changes.
 - [Branch early, branch often].
 - [Trunk-based development][trunk-based development: a comprehensive guide] and other branching strategies all work but [have different pros and cons][git branching strategies vs. trunk-based development].
 - Refactoring _can_ be an option.<br/>