diff --git a/src/content/blog/why-i-like-small-commits.md b/src/content/blog/why-i-like-small-commits.md
new file mode 100644
index 0000000..9e8d6e1
--- /dev/null
+++ b/src/content/blog/why-i-like-small-commits.md
@@ -0,0 +1,13 @@
+---
+title: "why i like small commits"
+pubDate: 'July 16 2024'
+description: ""
+draft: false
+---
+I like small commits. Why? Well first of all they make it easier to take over code from others, since it shows a coherent thought by simply having code split into smaller fragments.
+
+A benefit of this is that you continuosly scope the task at hand, which in return gives you a better overview of the project. You'll minimize the time the codebase is in a non-functioning state, as well as not getting distracted by *just solving one more thing*.
+
+A bonus for having small commits is that the commit message will be small and easily to describe. Additionally, I like using [**Gitmojis**](https://gitmoji.dev) as a way to identify the purpose of the commit.
+
+This is why I like small commits.
\ No newline at end of file