Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2024-art-of-knowing-when-to-stop-optimization #99

Open
wants to merge 11 commits into
base: master
Choose a base branch
from
8 changes: 8 additions & 0 deletions 2024/Art Of Knowing when to stop-(optimization)/article.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
# 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 added more changes the quality and taste stayed the same but the recipe got more complicated. He realized that the best version wasn’t necessarily the most complex one—it was the one that balanced simplicity and quality.

The same idea applies to optimizing data and models. There’s a “sweet spot” between keeping things too basic and making them overly complex. True optimization means improving pipelines or models in ways that genuinely add value or maintain performance while avoiding unnecessary complications. The goal is to strike the right balance, just like Sam did with his bread

## Authors
- Subahini Nadarajh
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading