From e7545f03cc72e63423c84f13ed613a47fe503096 Mon Sep 17 00:00:00 2001
From: subahini <46754761+subahini@users.noreply.github.com>
Date: Fri, 6 Dec 2024 23:26:00 +0100
Subject: [PATCH] Delete 2024/Art Of Knowing when to
 stop-(optimization)/article.md

---
 .../article.md                                      | 13 -------------
 1 file changed, 13 deletions(-)
 delete mode 100644 2024/Art Of Knowing when to stop-(optimization)/article.md

diff --git a/2024/Art Of Knowing when to stop-(optimization)/article.md b/2024/Art Of Knowing when to stop-(optimization)/article.md
deleted file mode 100644
index 5453779a..00000000
--- a/2024/Art Of Knowing when to stop-(optimization)/article.md	
+++ /dev/null
@@ -1,13 +0,0 @@
-# Art of Knowing When to Stop (Optimization)
-Think of optimization like perfecting a recipe: A baker named Sam kept
-adjusting his bread recipe to make it better.At first, small changes improved
-the bread, but when he changed too much, it actually got worse.
-He learned that the best version wasn't necessarily the most complex one.
-
-This same principle applies to programming – there's a "sweet spot" between
-code that's too basic and code that's unnecessarily complex. True optimization
-means making smart improvements that actually add value, while knowing when
-to stop before changes become counterproductive. The key is finding the right
-balance, just like Sam did with his bread.
-## Authors
-- Subahini Nadarajh